Geolocation
Providers using this tag (41)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Strong 5 Solid coverage with minor gaps
Developing 15 Usable, with meaningful gaps to close
Thin 7 Limited public surface area
Emerging 7 Early or largely undocumented
Minimal 6 Almost no public developer surface
Unrated 1 Not yet scored
APIs with this tag (79)
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 →
Exemplar 2 Complete, well-documented, and agent-ready
Strong 6 Solid coverage with minor gaps
Developing 14 Usable, with meaningful gaps to close
Thin 49 Limited public surface area
Emerging 7 Early or largely undocumented
Minimal 1 Almost no public developer surface
Companies reaching this through an API (22)
These companies publish an API, specification or operation carrying “Geolocation” but do not classify their business under it. Listed unranked and kept out of the count above, because one tagged operation is not a statement about what a company does.
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 38 providers in the APIs.io catalog tagged Geolocation, 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 | 39.4 | 19.8 | +19.6 | 38 |
| Access Clarity | 39.5 | 26.3 | +13.2 | 38 |
| Developer Ergonomics | 32.2 | 23.3 | +8.9 | 38 |
| Operational Transparency | 22.4 | 13.9 | +8.5 | 38 |
| Discoverability | 68 | 61 | +7 | 38 |
| Contract Governance | 11.2 | 6.3 | +4.9 | 38 |
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) | 15% | 10% | +5 |
| MCP server (first-party) | 15% | 9% | +6 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 8% | 11% | -3 |
| Security | 95% | 97% | -2 |
| Arazzo workflows | 8% | 2% | +6 |
| Governance rules | 33% | 14% | +19 |
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 CycleCalcs 63.5
- 2 HyperTrack 59.4
- 3 APIFreaks - API Hub for Developers 58.2
- 4 Neutrino API 57.6
- 5 Zenserp 57.4
- 6 Google Maps Platform 51.1
- 7 MCP360 49.7
- 8 Flock Safety 49.2
- 9 WeatherAPI 48.6
- 10 OpenUV 48.1
- 1 CycleCalcs 49.4
- 2 HyperTrack 42.6
- 3 Flock Safety 36.5
- 4 APIFreaks - API Hub for Developers 35.9
- 5 Zenserp 33.3
- 6 Google Places 32.7
- 7 Neutrino API 31.8
- 8 Airport Gap 30.6
- 9 Lookip 30.5
- 10 Google Maps Platform 29.4
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.