Errors and billing

When you are charged

You pay only for images that are delivered.
Refused or failed jobs are not charged.
The price is fixed by model and size tier. See Models and pricing.
Your balance is prepaid. When it runs out, requests fail with 403 until your manager tops it up.

Check what a request cost

Every response, success or error, carries a request ID header:

X-Oneapi-Request-Id: 2026102015161442847504045555018

Look up the charge for that ID. This endpoint needs no key:

curl https://orvado.dev/api/cost/request/2026102015161442847504045555018

{
  "request_id": "2026102015161442847504045555018",
  "cost_usd": 0.05,
  "created_at": 1792509374000
}

The response has a few more fields. Use cost_usd. An unknown ID, or a request that was not charged, returns:

{ "message": "failed to get cost by request id: record not found", "success": false }

Log the X-Oneapi-Request-Id of every request next to your own order or job ID. It is the fastest way to reconcile invoices and to ask support about a charge.

Read the header with the OpenAI Python SDK:

raw = client.images.with_raw_response.generate(
    model="nano-banana-pro",
    prompt="amethyst perfume bottle on plum velvet",
    size="1024x1024",
)
request_id = raw.headers.get("x-oneapi-request-id")
result = raw.parse()

Error format

Errors use the OpenAI shape. The message ends with the request ID:

{
  "error": {
    "message": "No token provided (request id: 2026102015161442847504045555018)",
    "type": "one_api_error"
  }
}

Error codes

Status	Meaning	Charged	What to do
`400`	Unsupported size, model or field	No	Fix the request. Check sizes and model IDs
`401`	Missing or invalid key	No	Check the `Authorization` header or create a new key
`403` `insufficient_user_quota`	Not enough balance on the account or the key	No	Ask your manager to top up, or raise the key limit in Tokens
`502` `async_image_failed`	The model refused or failed the job	No	Change the prompt and retry
`503`	No capacity for this model right now	No	Retry after a minute

Retry rules

Retry 502 and 503 with a backoff, for example 30 s, then 60 s, then 120 s.
Do not retry 400, 401 or 403 without fixing the cause.
Do not retry after a client timeout. See Response time and timeouts.

Get started

Guides

API reference

Errors and billing

When you are charged

Check what a request cost

Error format

Error codes

Retry rules

​When you are charged

​Check what a request cost

​Error format

​Error codes

​Retry rules

When you are charged

Check what a request cost

Error format

Error codes

Retry rules