| 401 | invalid_api_key | No usable agent API key. | Mint or check the key on the agent’s page. |
| 400 | invalid_request | The request body couldn’t be read, is over its route’s limit (32 MiB for a chat completion or message, 10 MiB for a generation request; images sent inline count toward it), holds so many characters such as <, >, and & that it grows past what a paid request can carry, or its Idempotency-Key is over 255 characters. The message says which. Nothing charged. | Fix the request. For images, see Send images. |
| 400 | streaming_not_enabled | The request set "stream": true on an endpoint that doesn’t stream. Nothing charged. | Send the request with "stream": false, or omit the field. |
| 413 | request_too_large | The request is under its route’s limit but larger than the model provider accepts, currently about 25 MB for a chat completion or message. Images sent inline count toward it. Nothing is charged unless the message names a transaction. | Resize or compress the images, or send fewer, then retry. See Send images. |
| 400 | provider_rejected_request | The model provider rejected the request, for example an unknown model name. When a payment was submitted, the message and X-Transaction-ID name it. | Fix the request. GET /v1/models lists the model names. If a payment was submitted, check that transaction before retrying. |
| 403 | budget_not_configured | No spend limit configured. | Configure a budget, then retry. A retry with the Idempotency-Key of a request you already paid for goes through to that payment. |
| 403 | daily_limit_reached | The agent reached its daily spending cap. Nothing charged. | Retry after the cap resets. |
| 403 | budget_inactive | The agent’s budget isn’t active. Nothing is charged unless the message names a transaction. | Activate the budget, then retry. When the message says Anchorage recorded the decline, it names the declined transaction in the message and the X-Transaction-ID header, and the identical request is declined again: check the transaction before you send it again. |
| 403 | insufficient_funds | The account doesn’t have enough funds for this request. Nothing is charged unless the message names a transaction. | Add funds, then retry. When the message says Anchorage recorded the decline, it names the declined transaction in the message and the X-Transaction-ID header, and the identical request is declined again: check the transaction before you send it again. |
| 403 | payment_declined | The payment was declined: a compliance, spending (the budget cap, with a message that the payment would take the budget past its cap), or account-status check, a per-payment or program limit, or a payment the model provider asked for that Anchorage can’t make for this request. The message gives the reason when it’s known. When it gives a reason and names no transaction, nothing was charged. When it says Anchorage can’t confirm whether the payment went through, the payment may have been made. When it says the request matches an earlier payment that used a different payment protocol, it names that payment’s transaction ID in the message and the X-Transaction-ID header, and nothing new was paid. | Act on the reason, then retry. For a budget limit, an org admin raises the cap, and you then retry with a new Idempotency-Key. When the message says Anchorage recorded the decline, it names the declined transaction in the message and the X-Transaction-ID header, and the identical request is declined again: check the transaction before you send it again. When the message can’t confirm the payment, send the identical request again with the same Idempotency-Key if you sent one, and with none added if you didn’t: it returns any payment already made instead of paying again. See Payment failures. |
| 503 | platform_unavailable | A temporary problem on Anchorage’s side stopped the payment. Your budget didn’t cause it. When a payment was submitted, the message and X-Transaction-ID name it. Otherwise the message says Anchorage can’t confirm whether the payment went through. | When the response carries x-should-retry: true, retry in a few minutes with the identical request and the same Idempotency-Key if you sent one, and with none added if you didn’t: it returns any payment already made instead of paying again. When the message names a transaction, the response carries false: check that transaction instead. Resending a non-streamed request usually returns the same recorded answer, and resending a streamed one doesn’t replay anything. |
| 409 | payment_request_expired | The model provider’s payment request expired before Anchorage could pay it. Nothing charged. | Retry the request. |
| 502 | provider_unavailable | The model provider is unavailable or unreachable. Nothing charged. | Retry in a few minutes. |
| 429 | rate_limit_exceeded | The model provider is rate limiting requests, or Anchorage is limiting how often new payment destinations can be set up. When a payment was submitted, the message and X-Transaction-ID name it. | When the response carries x-should-retry: true, wait for the Retry-After delay if it has one, otherwise back off, then retry. When a payment was submitted, the response carries false and no Retry-After: check that transaction instead, since resending can return the same recorded answer. |
| 502 | paid_no_response | A payment was submitted but no usable completion came back: the provider refused the payment, returned a server error, or returned an answer too large to record, or Anchorage didn’t send the request because its new quote’s price differs from the earlier payment’s. The message and X-Transaction-ID name the transaction. | Check that transaction before you send the request again, and resend the way the message says to avoid paying twice. For a streamed request, or one over 10 MiB, Anchorage sent the request at most once and a same-key resend sends nothing and returns payment_in_progress or already_paid, so the message asks you to use a new Idempotency-Key to ask again. When the message says the request was not sent, this request’s quote differs from the one the earlier payment was made for, and that payment can no longer be sent: a same-key resend sends nothing, so send it with a new Idempotency-Key to ask again, which makes a new payment. If it stays pending, contact Anchorage support. |
| 409 | payment_in_progress | A streamed request, or one over 10 MiB, with this Idempotency-Key was already paid and is still being answered on another connection. Nothing new was charged or sent. The message and X-Transaction-ID name the transaction. | Wait for the Retry-After delay, then send the identical request again, with the same Idempotency-Key if you sent one and with none added if you didn’t. |
| 409 | already_paid | A streamed request, or one over 10 MiB, with this Idempotency-Key was already paid, and Anchorage sends a paid request to the model provider at most once. Nothing new was charged or sent. The message and X-Transaction-ID name the transaction. | Check that transaction, then send the request with a new Idempotency-Key to ask again. |
| 403 | origin_not_permitted | Refused before this endpoint’s own request handling ran (for example, a compliance check on the connection). Nothing charged. | See Payment failures. |
| 500 | internal_error | Something went wrong on Anchorage’s side. When the message says a payment was submitted, the response carries x-should-retry: false. | Retry in a few minutes when the response carries x-should-retry: true. When the message says a payment was submitted, check your transactions in Anchorage Agentic Banking before you send the request again, and resend the way the message says to avoid paying twice (when it says the request was not sent, a new Idempotency-Key makes a new payment); if the resend fails the same way, contact Anchorage support. Otherwise, false means the same request fails the same way, so contact Anchorage support. |
| 404 | generation_job_not_found | A generation status poll named no job of this kind that belongs to this agent. | Check the id and the route. |