Networks
NetworkNetworks
Providers using this tag (44)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 5 Complete, well-documented, and agent-ready
Strong 1 Solid coverage with minor gaps
Developing 5 Usable, with meaningful gaps to close
Thin 14 Limited public surface area
Emerging 9 Early or largely undocumented
Minimal 10 Almost no public developer surface
APIs with this tag (163)
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 24 Complete, well-documented, and agent-ready
Strong 32 Solid coverage with minor gaps
Developing 48 Usable, with meaningful gaps to close
Thin 41 Limited public surface area
Emerging 18 Early or largely undocumented
Companies reaching this through an API (148)
These companies publish an API, specification or operation carrying “Networks” 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 37 providers in the APIs.io catalog tagged Networks, 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 | 34.8 | 24.5 | +10.3 | 37 |
| Contract Quality | 28.4 | 18.6 | +9.8 | 37 |
| Operational Transparency | 21.1 | 13.2 | +7.9 | 37 |
| Contract Governance | 15.2 | 9.7 | +5.5 | 37 |
| Access Clarity | 35 | 30 | +5 | 37 |
| Discoverability | 63.9 | 59.1 | +4.8 | 37 |
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) | 19% | 18% | +1 |
| MCP server (first-party) | 14% | 16% | -2 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 24% | 13% | +11 |
| Security | 100% | 99% | +1 |
| Arazzo workflows | 3% | 1% | +2 |
| Governance rules | 62% | 36% | +26 |
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 CloudFront 79.6
- 2 Telstra 72.3
- 3 Hubble Network 71.7
- 4 Azure Load Balancer 70.2
- 5 Amazon Web Services 68.5
- 6 Shodan 60.9
- 7 Akamai 53.8
- 8 Broadcom 53.8
- 9 Forward Networks 44.1
- 10 AT&T 43.8
- 1 Telstra 42.3
- 2 Akamai 40.8
- 3 Amazon Web Services 38.8
- 4 CloudFront 37.9
- 5 Broadcom 37.5
- 6 Agentel 36.1
- 7 Hubble Network 34.9
- 8 Vectranetworks 33.6
- 9 Physical Capability Cloud 33.4
- 10 AT&T 32.8
Coverage caveat. 26 of 37 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 14 November 2026, across 41591 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.