What "unlimited requests" should mean, precisely
Unlimited should be a testable claim, not a mood. If a plan has a real ceiling anywhere, that number belongs on the pricing page, not the word unlimited.
Tag
#billing
Why per-country pricing tiers are a bad idea
Charging more to look up an address in one country than another treats geography itself as a pricing lever instead of plain, ordinary data to serve.
New ways to pay: PayPal, cryptocurrency and bank transfer
Accounts can now fund prepaid credit or pay for an Unlimited package using PayPal, cryptocurrency, or a bank transfer, whichever option fits best.
Prepaid credit and Unlimited packages, explained
Once free allowances run out, usage draws on prepaid credit at a fixed rate or an Unlimited package, with the same pricing on every endpoint.
Why flat pricing beats hidden overage fees
An overage fee only shows up on the invoice you did not expect. Flat, published pricing lets you calculate the cost before you ever place the call.
What per-product billing gets wrong about how APIs are used
Real applications mix geocoding, IP lookups, and time zone calls in a single request path. Billing them as separate products ignores how they are used together.
The trouble with "unlimited" plans that quietly aren't
Unlimited is supposed to mean no cap. Read the fine print on many unlimited API plans and you will often find a fair use policy that quietly says otherwise.
Why we priced this per request, not per seat
A per-request price matches what an API actually costs to run. Seat pricing measures headcount, not usage, and geocoding traffic rarely follows either.