Docs

Errors and rate limits

Errors use the OpenAI shape:

{ "error": { "message": "…", "type": "invalid_request_error", "param": null, "code": "input_url_rejected" } }
HTTPtypecode
400invalid_request_errorinvalid_request, unsupported_parameter, unsupported_media, input_url_rejected, content_blocked, duration_exceeded, data_class_not_allowed
401authentication_errorinvalid_api_key
402insufficient_quotainsufficient_balance: top up in the console
403permission_erroraccount_not_active, scope_missing, kyb_required
404not_found_errormodel_not_found, job_not_found
409invalid_request_erroridempotency_key_reused
413invalid_request_errorfile_too_large: use the batch endpoint
429rate_limit_errorrate_limited, queue_full, with Retry-After
503service_unavailablemetering_unavailable, no_capacity

503 metering_unavailable means our metering service is unreachable and we refuse work rather than run it uncounted. Retry with backoff.

Rate limits

Responses carry x-ratelimit-* headers. On 429 or 503, wait for Retry-After seconds. The OpenAI SDKs do this automatically. Use an Idempotency-Key so retries never create duplicate jobs.

Errors and rate limits · Vouch Compute