Frequently asked questions

No. Usage is counted per IP address, so you can call any endpoint with no key and no account, 2,500 times a day. Build the whole integration that way. A key or a whitelisted IP is only needed to go past 2,500 a day.

An email address. Nothing else: no name, no company, no card. You can create keys and whitelist addresses straight away, and add credits or subscribe whenever you decide to.

You top up a balance in advance, any amount from $5, by card or in crypto. One credit costs $0.001 and pays for one request above the free 2,500 a day. Credits are only used after the free allowance, even when you use an API key, and they never expire. When the balance is empty, requests above the free allowance are refused until you top up; nothing is charged automatically.

Yes. Bitcoin (on-chain and Lightning), Ethereum, USDC, USDT and Litecoin, for credits and for the Unlimited plan. The amount is fixed at checkout and applied once the payment confirms.

Every endpoint and every drop-in host, with no per-request charges, for €50 a month, from up to two IP addresses in any 24 hour period per account. Burst limits still apply and are raised on request. See pricing.

Per IPv4 address, or per /40 block for IPv6, across all endpoints and drop-in hosts. The counter resets at midnight UTC. Accounts get the same 2,500 a day free before any credits are used.

A single IPv6 customer usually holds a /64 or larger, which is more addresses than anyone could use. Counting per address would let one machine rotate through them and never hit the limit. Counting per /40 keeps the free tier fair. If you share a /40 with other users, attach a key so your usage is counted on your own account.

An API key can be used from at most two distinct IP addresses in any rolling 24 hour period. A request from a third address is refused with HTTP 403 and the code key_ip_limit until one of the earlier addresses has not been seen for 24 hours. On the Unlimited plan the same two-address limit applies to the whole account. On credits, whitelisting server addresses has no such limit.

Yes. CORS is enabled on every endpoint. Do not embed an API key in client code, because every visitor would count as a new IP against the key and the third visitor would be refused. Let visitors use the free tier from their own address, or proxy the call through your server where a key or whitelist applies.

Yes, a burst limit of 10 requests a second for anonymous use and 50 a second for accounts. It can be raised for accounts on request. Over the limit you get 429 with the code rate_limited; those requests are not counted.

Revoke it in the dashboard and create a new one. Because of the two IP rule, a leaked key cannot be used from more than two machines in a day anyway, and since credits are prepaid, nobody can run up a bill beyond the balance you chose to load.

It tells you what the returned point represents: house for the building or parcel, street for a position interpolated along the street, postcode for the centre of a postal code area, and admin for the centre of a city, district, region or country. If you asked for a house and got postcode, we could not find the house.

The coverage page lists the best level available for each of 249 countries and territories, with filters by region and level. It is updated with every data release.

A mix of national address and cadastral registers where they are open, OpenStreetMap, GeoNames, postal authorities, regional internet registries and routing tables for IP data, the IANA time zone database and public elevation models, plus our own corrections. Each source is checked against the others before it goes in.

Yes. Results are yours to keep in your database, cache and display on any map, including maps from other providers. The only restriction in the terms is reselling the raw data as a geocoding service of your own.

Address data is refreshed monthly, IP data weekly, time zone rules whenever IANA publishes a release, and elevation data when a better public model appears. The changelog notes each release.

Pass lang with an ISO 639-1 code and place names come back in that language where we have them, falling back to the local name. Address formatting follows the conventions of the country the address is in.

The paths, parameters and response shapes match each provider's public documentation so that existing client code parses the responses without changes. The data is ours, so values differ, and a few provider-specific features are not included. Each compatibility page lists the differences.

No. The loader at gapi.mygeocode.com provides the google.maps namespace with our own map tiles, geocoder, autocomplete and elevation service behind it. Street View, Directions and Places Details are not included. Map loads do not count toward your quota. See JavaScript drop-ins.

No. Those names belong to their owners and are used here only to say which formats we can answer in.

Self-serve plans do not come with a contractual SLA. We run the API in more than one region and show live status at status.mygeocode.com. If you need a written SLA, talk to us.

Email [email protected]. Accounts get a reply within one business day. Free tier questions are answered too, as time allows.