Location
LocationsLocation
Providers using this tag (81)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Strong 7 Solid coverage with minor gaps
Developing 19 Usable, with meaningful gaps to close
Thin 20 Limited public surface area
Emerging 16 Early or largely undocumented
Minimal 16 Almost no public developer surface
APIs with this tag (331)
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 21 Complete, well-documented, and agent-ready
Strong 50 Solid coverage with minor gaps
Developing 130 Usable, with meaningful gaps to close
Thin 91 Limited public surface area
Emerging 31 Early or largely undocumented
Minimal 8 Almost no public developer surface
Companies reaching this through an API (299)
These companies publish an API, specification or operation carrying “Location” 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.
Show all 299 companies ↓
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 76 providers in the APIs.io catalog tagged Location, 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 | 32.7 | 17.6 | +15.1 | 76 |
| Developer Ergonomics | 35.8 | 23.2 | +12.6 | 76 |
| Operational Transparency | 21.3 | 13.7 | +7.6 | 76 |
| Access Clarity | 33.8 | 26.5 | +7.3 | 76 |
| Discoverability | 64.2 | 58.1 | +6.1 | 76 |
| Contract Governance | 8.1 | 6.3 | +1.8 | 76 |
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) | 24% | 14% | +10 |
| MCP server (first-party) | 20% | 12% | +8 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 22% | 11% | +11 |
| Security | 100% | 98% | +2 |
| Arazzo workflows | 3% | 2% | +1 |
| Governance rules | 24% | 14% | +10 |
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 Square 75.4
- 2 HERE 71.2
- 3 Esri 70.4
- 4 RoxyAPI 63.5
- 5 positionstack 62.4
- 6 Kontakt.io 61.4
- 7 Listings API 60.8
- 8 HyperTrack 59.3
- 9 Amazon Location Service 59
- 10 Serper 56.3
- 1 Listings API 66.1
- 2 Square 60.6
- 3 HERE 55.9
- 4 Mireye 51.4
- 5 Esri 50.8
- 6 Kontakt.io 50.5
- 7 Mapbox 44.6
- 8 SK Telecom 43.7
- 9 HyperTrack 42.6
- 10 Paedae 42.3
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.