Platform status#
The console itself is the health signal: if it loads and your calls return JSON answers, the platform is up.
When calls start failing, read the error code first: a refusal like insufficient_budget or
product_not_assigned is your setup, not the platform — see Errors.
A stream that ends without data: [DONE] was cut off mid-answer; the invocation id still
tells you what it cost.
Checking a charge#
The console is the record of what you were charged, and it answers most "was I charged correctly?" questions on its own:
- Usage lists every call — time, project, product, status, tokens, and the reserved and charged micro-USD amounts.
- Request detail opens one call: the reservation, the settlement (reserved, charged, released), the provider outcome and a safe explanation. Prompt and response content are deliberately absent.
- Project wallet shows funded, charged, reserved and available balances; Financial audit combines funding entries with the charges against them.
A call that never reached a provider was never charged, and a charged call has a ledger entry to point at. Between those two facts, most disputes dissolve.
If a charge still looks wrong#
Take it to your organization Owner, who can see the organization's usage rows. Cases that survive that go to the platform operator: held reservations that never settled land in an operator reconciliation queue, and any correction there requires upstream evidence and a recorded reason — the ledger, not anyone's say-so, decides.
You will need the invocation id of the call in question. It is returned as the
X-AIGrid-Invocation response header on every admitted call and shown in the usage views,
and it threads through the reservation, the charge and any reconciliation.
What has a channel, and what does not#
| Question | Where it goes |
|---|---|
| "What was I charged for this call?" | Usage → request detail, in the console |
| "Is the platform down?" | The error code says whether it's you or the platform |
| "Why did this call fail?" | Errors — the code names the recovery |
| "Why can't I call this model?" | Almost always a missing assignment — see Catalog and assignments |
| "This charge is wrong" | your organization Owner, then platform-operator reconciliation |
| General product support | your normal commercial or operator contact |
Before you escalate#
Most failures name their own fix. Have these ready and the conversation is short:
- the invocation id — the
X-AIGrid-Invocationheader, or the call in your usage view - the error code — the
codefield, not the message — and the recovery you already tried - the organization and project involved
- your key prefix only, never the secret
- whether the call appears in usage, and what its reserved / charged / released amounts show
Next#
- Errors — every code and what clears it
- Usage and metering — finding a call by invocation id