Environment
EnvironmentsEnvironment
Providers using this tag (46)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 1 Complete, well-documented, and agent-ready
Strong 1 Solid coverage with minor gaps
Developing 4 Usable, with meaningful gaps to close
Thin 7 Limited public surface area
Emerging 8 Early or largely undocumented
Minimal 25 Almost no public developer surface
APIs with this tag (192)
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 37 Complete, well-documented, and agent-ready
Strong 40 Solid coverage with minor gaps
Developing 65 Usable, with meaningful gaps to close
Thin 18 Limited public surface area
Emerging 9 Early or largely undocumented
Minimal 23 Almost no public developer surface
Companies reaching this through an API (148)
These companies publish an API, specification or operation carrying “Environment” 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 148 companies ↓
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 43 providers in the APIs.io catalog tagged Environment, 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 | 18.8 | 17.2 | +1.6 | 43 |
| Contract Governance | 6.9 | 6.5 | +0.4 | 43 |
| Discoverability | 57.9 | 57.9 | 0 | 43 |
| Operational Transparency | 10.7 | 13 | -2.3 | 43 |
| Developer Ergonomics | 18.9 | 23.2 | -4.3 | 43 |
| Access Clarity | 14.7 | 23.9 | -9.2 | 43 |
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) | 7% | 13% | -6 |
| MCP server (first-party) | 7% | 12% | -5 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 2% | 11% | -9 |
| Security | 100% | 98% | +2 |
| Arazzo workflows | 5% | 2% | +3 |
| Governance rules | 26% | 16% | +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 Postman 78
- 2 First Street 55
- 3 Prime Intellect 53.9
- 4 Google Maps Platform 51.3
- 5 Climatiq 44.2
- 6 Bureau of Land Management 40.3
- 7 Forest Service 34.5
- 8 Air Quality Programmatic APIs 31.5
- 9 World Air Quality Index (WAQI) 31.5
- 10 Carbon Intensity API 30.7
- 1 Postman 55.6
- 2 Bureau of Land Management 41.3
- 3 Prime Intellect 35.6
- 4 First Street 35.1
- 5 World Air Quality Index (WAQI) 33.5
- 6 Pantheon 28.3
- 7 Air Quality Programmatic APIs 27.2
- 8 SouthendOnSea.city 26
- 9 Google Maps Platform 24.5
- 10 Carbon Intensity API 23.8
Coverage caveat. 38 of 43 scored members had under half their catalog-attributable points satisfied at all (catalog_earned / catalog_max < 0.5). They are INCLUDED in the mean above. A large share here means the cohort mean is partly a measurement of how far our enrichment reached, not only of how these providers publish.Generated from the catalog build of 24 October 2026, across 31984 providers, using the same computation served by the APIs.io cohort API. Briefs are published for rosters of 5 or more scored providers; below that a distribution is not meaningful.
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.