Frequently Asked Questions (FAQ)

What is OnCoord?

OnCoord is a geocoding and place search platform powered by a combination of open data datasets. It enables accurate, fast, and scalable location search through a modern API.

Is the data free to use?

OnCoord offers a free tier for limited usage and paid plans for commercial or high-volume applications. You can view current options on our Pricing page.

What are the data sources?

Our geocoder integrates data from trusted open sources like OpenStreetMap, OpenAddresses, Overture, and Who’s on First, as well as OnCoord-collected.

What countries/datasets are available?

OnCoord provides open-source geocoding for Mexico, Central America, and South America. You can view a list of currently supported countries and data coverage on our Countries page.

What software powers the OnCoord geocoder?

OnCoord is built on Pelias, an open-source geocoding engine.

How do I use the OnCoord Geocoder?

To use the OnCoord geocoder, you’ll first need to obtain an API key. An API key is a unique identifier that tells us which application is making a request to our service. This helps us:

• Authenticate your application so we know the request is valid
• Track usage to make sure you stay within your plan’s limits
• Protect the service from abuse and ensure fair access for everyone

In short: the API key is like a “pass” that lets your app use our geocoding services securely and reliably.

You can log in here to obtain your API key and start using the OnCoord geocoder.

Do you enforce rate limits?

Yes. OnCoord applies rate limits to ensure fair usage, protect system stability, and prevent accidental or abusive overload.

Rate limits are defined by plan and typically include:

• Requests per second (short-term protection)
• Requests per day or month (overall usage limits)

Per-second limits are not intended to imply that responses are instantaneous. Network latency, geographic distance, and request complexity all affect response time. A limit such as “10 requests per second” means your application may send short bursts of requests up to that rate — not that each request must complete within one second.

In practice, these limits exist to prevent runaway loops or misconfigured clients from overwhelming the service. Normal applications — including web, mobile, and batch geocoding workflows — operate comfortably within these limits.

Note: Rate limits apply to request bursts, not response speed. Network latency does not reduce your allowed request rate. Clients may send multiple requests concurrently as long as they remain within these limits.