Credits and limits
Understand prepaid usage, per-operation costs, spending caps, and technical rate limits.
Credits follow the work
Each operation documents its cost in the generated API reference. Matrix costs depend on source–target pairs; directions and elevation use started input blocks. Read the operation's cost before increasing request size.
Read accounting fields
Successful responses include credits_charged, request_id, and data_version. Use these fields to reconcile application activity with console usage.
Balance and account limits
A depleted balance returns 402 Payment Required. Account spending limits and technical request limits are independent controls. Manage available limits and prepaid credits through your console.
No silent overage
Default prepaid operation stops at the configured balance and limits. UAT balances and purchases are isolated test data.
Rate limits and retries
Technical request limits can return 429. Respect Retry-After when present and use bounded retries with backoff. Avoid retry storms, especially for large matrix requests. See error handling.