Skip to main content
Three ceilings answer with a 429 and Retry-After, and error.code tells them apart. Spending is bounded by the credits a fix shows before it starts.

​
How many requests can I send?

  • A client is counted by its IP address, and an IPv6 client by its /64 network. A check needs no key, so the limit is per client, not per account.
  • Retry-After on rate_limited is the seconds until the oldest check of the last minute leaves the window.
  • too_many_running_fixes clears as soon as one of the account’s fixes finishes. Wait the seconds in Retry-After, then send the fix again.
  • daily_capacity_reached lifts on its own: Retry-After says when, at the latest the next UTC midnight.
  • Poll a job as its Retry-After says, not faster.

​
How large can an image be?

​
How much can a fix spend?

A fix never spends more than it shows before it starts.
  • The cost is known up front. GET /v1/plans returns it under fix_credits, with its own figure for a large tile. The credits are held when the job starts; a fix that cannot be paid for answers 402 insufficient_credits and starts nothing.
  • A failure gives the credits back when it ends with no_seamless_candidate, service_unavailable or interrupted.
  • A repeat costs nothing. The same file with the same repeat type returns the stored result, and a second send while the first still runs returns the same job.
  • A key cannot buy credits. Plans and top-ups are bought signed in on makeseamless.com, so a leaked key can spend only the credits already on the account. Revoke it on the Account page and it stops at once.
  • One top-up purchase is 10 to 10,000 credits.

​
How long are jobs and images kept?