Geocoding
Geocodinggeocoding
Providers using this tag (136)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 1 Complete, well-documented, and agent-ready
Strong 7 Solid coverage with minor gaps
Developing 20 Usable, with meaningful gaps to close
Thin 24 Limited public surface area
Emerging 6 Early or largely undocumented
Minimal 78 Almost no public developer surface
APIs with this tag (121)
Ranked by the provider's API Evangelist rating — the Kin Score is scored per provider, not per API, so every API of a provider shares its band. How the rating works →
Strong 5 Solid coverage with minor gaps
Developing 13 Usable, with meaningful gaps to close
Thin 18 Limited public surface area
Emerging 8 Early or largely undocumented
Minimal 77 Almost no public developer surface
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 136 providers in the APIs.io catalog tagged Geocoding, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Contract Quality | 22.4 | 17.5 | +4.9 | 136 |
| Discoverability | 63 | 60.4 | +2.6 | 136 |
| Operational Transparency | 12 | 11.3 | +0.7 | 136 |
| Contract Governance | 5.8 | 6.4 | -0.6 | 136 |
| Access Clarity | 18.4 | 22.3 | -3.9 | 136 |
| Developer Ergonomics | 13.9 | 17.9 | -4 | 136 |
A facet is averaged over the members that carry it, not over the whole cohort — the “Scored” column is that count. Averaging an absent facet as zero would score our own coverage gaps as the providers’ posture.
| Artifact | This cohort | Catalog | Difference |
|---|---|---|---|
| MCP server (any) | 8% | 16% | -8 |
| MCP server (first-party) | 3% | 7% | -4 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 7% | 9% | -2 |
| Security | 96% | 88% | +8 |
| Arazzo workflows | 4% | 2% | +2 |
| Governance rules | 21% | 13% | +8 |
mcp_pct counts any mcp/ artifact including ones API Evangelist derived from the provider OpenAPI; mcp_first_party_pct counts only servers the provider publishes. Prefer the latter.
- 1 OpenMercantil 87.9
- 2 Avalara 63.6
- 3 positionstack 63.3
- 4 APIFreaks - API Hub for Developers 62.9
- 5 Ordnance Survey 62.6
- 6 Onfleet 62.3
- 7 OpenWeatherMap 62.3
- 8 REA Group 55.3
- 9 Apple 52.8
- 10 OpenStreetMap 52.4
- 1 Avalara 46.9
- 2 OpenMercantil 42.3
- 3 Domain Group 41.5
- 4 Google 39.2
- 5 Ordnance Survey 34
- 6 Moody's RMS 33.1
- 7 APIFreaks - API Hub for Developers 32.5
- 8 REA Group 30.8
- 9 IPGeolocation.io 30.6
- 10 Google Maps Platform 29.9
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for tags
7 MCP tools reach this
find_tagsBrowse and filter every tag in the catalog.get_cohortThis tag as a scored cohort — every provider carrying it, with scores.cohort_statsPRO — the distribution across this tag: mean, median, band split, adoption rates.cohort_rankingsPRO — the leaderboard, on composite AND agent-readiness axes.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/tags/geocoding"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/geocoding"
curl "https://apis.io/api/v1/cohorts/tag/geocoding/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.