API archive entry · source-reported
OpenStreetMap
Navigation, geolocation and geographical data
Decision snapshot
OpenStreetMap is catalogued as a Geocoding API from OpenStreetMap. The directory reports oauth authentication, HTTPS as unconfirmed, and CORS as unknown.
- Category
- Geocoding
- Authentication
- OAuth
- HTTPS
- Unconfirmed
- CORS
- Unknown
Evaluation pathway
- Define endpoints, fields, freshness, and expected request volume.
- Read the live source and confirm access, terms, limits, and version.
- Test representative inputs, errors, latency, pagination, and data quality.
- Plan monitoring, retries, caching, version pinning, and a fallback.
What still needs verification
Pricing and quotas
Confirm current plans, free-tier limits, overages, and request ceilings.
Endpoint coverage
Check that the operations and response fields match the intended workload.
Reliability
Look for uptime history, a status page, support routes, and service commitments.
Data and privacy
Review retention, licensing, regional processing, and compliance requirements.
Versioning
Confirm the active version, change policy, deprecation window, and migration guidance.
Developer experience
Validate SDKs, examples, error formats, pagination, and test environments.
Nearby Geocoding options
Battuta
A (country/region/city) in-cascade location API
API key · HTTPS unconfirmed · CORS Unknown
Cep.la
Brazil RESTful API to find information about streets, zip codes, neighborhoods, cities and states
No auth · HTTPS unconfirmed · CORS Unknown
GeoNames
Place names and other geographical data
No auth · HTTPS unconfirmed · CORS Unknown
Source reference
This page separates source-reported facts from questions that need live provider verification.