# Manifest

Manifest is a smart LLM router for OpenClaw. It scores each request across multiple dimensions, picks a complexity tier (simple, standard, complex, reasoning), and routes to the cheapest qualifying model from your connected suppliers. The Grid plugs in as a backend supplier: you connect it through Manifest's dashboard, and Manifest routes qualifying requests to Grid instruments at market prices.

This works in both local mode (self-hosted plugin, no account needed) and cloud mode (`app.manifest.build`).

## Prerequisites

* Manifest installed and running. Either local (`openclaw plugins install manifest` followed by `openclaw gateway restart`) or cloud (`app.manifest.build` account).
* A Grid account at [app.thegrid.ai](https://app.thegrid.ai).
* Credits in your account. The Grid is prepaid.
* A Grid consumption API key from **Settings → API Keys → Create Consumption Key**.

## Setup

### 1. Open the Manifest dashboard

Local mode: <http://127.0.0.1:2099> after the plugin install. Cloud mode: [app.manifest.build](https://app.manifest.build).

### 2. Add The Grid as a custom provider

In the **Routing** or **Providers** section, add a new custom provider:

* Provider name: `thegrid`
* Base URL: `https://api.thegrid.ai/v1`
* API key: your Grid consumption key
* API type: OpenAI-compatible

### 3. Add Grid instruments as models

In the provider configuration, add the Grid instruments you want Manifest to route to. Pull the live IDs from the [current instruments list](/docs/instrument-specifications/current-instruments.md).

### 4. Map instruments to Manifest tiers

Manifest's tier system aligns naturally with Grid tiers. A practical setup for a coding agent:

| Manifest tier | Primary                 | Fallback                |
| ------------- | ----------------------- | ----------------------- |
| Simple        | `thegrid/code-standard` | `thegrid/text-standard` |
| Standard      | `thegrid/code-prime`    | `thegrid/text-prime`    |
| Complex       | `thegrid/code-max`      | `thegrid/agent-max`     |
| Reasoning     | `thegrid/code-max`      | `thegrid/text-max`      |

For agentic workloads (multi-step tool use), swap `agent-prime` and `agent-max` into the Standard and Complex tiers.

### 5. Activate `manifest/auto` in OpenClaw

```bash
openclaw models set manifest/auto
```

## Verification

Run a task in OpenClaw and check the Manifest dashboard. It shows which model handled each request, the tier classification, and the cost. If Grid instruments appear in the routing log, the integration is live.

## Troubleshooting

{% hint style="warning" %}
**401 from The Grid through Manifest.** The key in Manifest's provider config is a Grid trading key, not a consumption key. Generate a new consumption key and update the provider.
{% endhint %}

{% hint style="warning" %}
**402 Payment Required.** Your credits are at zero. Top up at [app.thegrid.ai](https://app.thegrid.ai).
{% endhint %}

{% hint style="info" %}
**Manifest routes to other suppliers instead of The Grid.** Manifest picks the cheapest qualifying model per tier. If a non-Grid supplier is cheaper for the tier you assigned, Manifest will prefer it. Adjust the tier assignment if you want to force Grid instruments.
{% endhint %}

{% hint style="info" %}
**Cost numbers don't match the Grid dashboard.** Cost tracking in Manifest depends on the per-model pricing you set. The Grid uses market-based pricing per fill, so Manifest's tracked costs will not match exactly. The Grid dashboard is the source of truth.
{% endhint %}

{% hint style="info" %}
**Using The Grid as the only Manifest backend.** Connect just The Grid, assign instruments to all four tiers, and Manifest will route every request through it.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://thegrid.ai/docs/integrations-and-best-practices/integrations/manifest.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.