Geocode Earth
Geocode Earth is a hosted geocoding and address autocomplete API built by the team that maintains Pelias, the open-source geocoder. It provides forward (search), autocomplete, reverse, and structured geocoding plus place lookup over fully open data (OpenStreetMap, OpenAddresses, Who's on First, and Geonames), with results that can be stored without restrictive licensing.
Geocode Earth publishes 3 APIs on the APIs.io network: Forward API, Place API, and Reverse API. Tagged areas include Geocoding, Address Autocomplete, Reverse Geocoding, Mapping, and Pelias.
Geocode Earth’s developer surface includes authentication, documentation, engineering blog, and 8 more developer resources.
Kin Score
APIs 3
Individual APIs this provider publishes, each with its own machine-readable definition.
Geocode Earth Forward API
The Forward API from Geocode Earth — 3 operation(s) for forward.
Geocode Earth Place API
The Place API from Geocode Earth — 1 operation(s) for place.
Geocode Earth Reverse API
The Reverse API from Geocode Earth — 1 operation(s) for reverse.
Open Collections 1
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Geocode Earth API
OPEN COLLECTIONPricing Plans 1
Published pricing tiers and plan structures.
Rate Limits 1
Documented rate limits and quota policies.
Geocode Earth Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals for API financial operations.
Geocode Earth Finops
FINOPSSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
Recommended x-agentic-access execution contracts for AI agents.
Resources
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API