Credits and caps
Every request spends credits. Free credits are spent first, then credits you loaded.
The free quota
10,000 credits a day, reset at midnight UTC. That is about 500 map views or 1,000 geocodes. GitHub accounts younger than 30 days get 2,000 a day. Unused free credits don’t carry over.
Packs
Load credits in packs of $5 (100,000 credits), $20 (440,000) or $50 (1,200,000). Purchased credits expire 12 months after purchase. There is no subscription.
At zero
When the free quota and your loaded credits are both used up, requests return
402 insufficient_credits with a message saying nothing more will be charged. Maps stop
loading new tiles. Add credits and requests work again within seconds. We can never bill you
more than you loaded.
Reading your balance
Every metered response has two headers:
X-MR-Credits-Used: what this request costX-MR-Balance: credits left after it, free and paid together
GET /v1/account/usage with a secret key returns the balance in full. The balance in headers
can lag a few hundred credits behind, because each server holds a small block of credits at a
time.
Failed requests are free
If geocoding is down or a batch item fails on our side, its credits are given back and the response says so. Requests refused for a bad parameter, a bad key or a rate limit are never charged.
Refunds and disputes
A refund removes the same share of that pack’s credits, never more than you have left. Credits from a disputed payment are frozen until the dispute is resolved.