Edge Computing
Providers using this tag (107)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 5 Complete, well-documented, and agent-ready
Strong 5 Solid coverage with minor gaps
Developing 20 Usable, with meaningful gaps to close
Thin 16 Limited public surface area
Emerging 19 Early or largely undocumented
Minimal 38 Almost no public developer surface
Unrated 4 Not yet scored
APIs with this tag (32)
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 1 Solid coverage with minor gaps
Developing 18 Usable, with meaningful gaps to close
Thin 6 Limited public surface area
Emerging 6 Early or largely undocumented
Minimal 1 Almost no public developer surface
Companies reaching this through an API (9)
These companies publish an API, specification or operation carrying “Edge Computing” 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 100 providers in the APIs.io catalog tagged Edge Computing, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Developer Ergonomics | 32.1 | 23.2 | +8.9 | 100 |
| Operational Transparency | 18.4 | 13 | +5.4 | 100 |
| Contract Quality | 20.1 | 17.2 | +2.9 | 100 |
| Discoverability | 60.5 | 57.9 | +2.6 | 100 |
| Contract Governance | 8.7 | 6.5 | +2.2 | 100 |
| Access Clarity | 25.9 | 23.9 | +2 | 100 |
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) | 13% | 13% | 0 |
| MCP server (first-party) | 12% | 12% | 0 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 10% | 11% | -1 |
| Security | 96% | 98% | -2 |
| Arazzo workflows | 2% | 2% | 0 |
| Governance rules | 21% | 16% | +5 |
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 Cloudflare 80.6
- 2 Netlify 70.6
- 3 Azion 67.7
- 4 Synadia Communications 67.6
- 5 CloudFront 67.3
- 6 Spectro Cloud 65.9
- 7 Webscale Networks 62.4
- 8 Edgee 58.4
- 9 Amazon IoT Greengrass 57.7
- 10 Amazon Outposts 54.8
- 1 Cloudflare 69.6
- 2 Netlify 58.8
- 3 Turso 47.2
- 4 ETSI 45.1
- 5 Upstash 41.8
- 6 Akamai 40.8
- 7 Weidmüller 36.2
- 8 Amazon IoT Greengrass 35.8
- 9 Scale Computing 35.5
- 10 Edgee 33.4
Coverage caveat. 86 of 100 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.