Testing
Providers using this tag (146)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Strong 14 Solid coverage with minor gaps
Developing 30 Usable, with meaningful gaps to close
Thin 33 Limited public surface area
Emerging 46 Early or largely undocumented
APIs with this tag (111)
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 15 Complete, well-documented, and agent-ready
Strong 18 Solid coverage with minor gaps
Developing 15 Usable, with meaningful gaps to close
Thin 28 Limited public surface area
Emerging 34 Early or largely undocumented
Minimal 1 Almost no public developer surface
Companies reaching this through an API (47)
These companies publish an API, specification or operation carrying “Testing” 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
Where this tag sits
146 providers carry this tag directly, and 202 counting the 6 narrower tags below — 56 more to reach.
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 139 providers in the APIs.io catalog tagged Testing, 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 | 37.6 | 23.2 | +14.4 | 139 |
| Operational Transparency | 23.4 | 13 | +10.4 | 139 |
| Contract Quality | 27 | 17.2 | +9.8 | 139 |
| Access Clarity | 32.2 | 23.9 | +8.3 | 139 |
| Discoverability | 62 | 57.9 | +4.1 | 139 |
| Contract Governance | 10.2 | 6.5 | +3.7 | 139 |
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) | 25% | 13% | +12 |
| MCP server (first-party) | 21% | 12% | +9 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 6% | 11% | -5 |
| Security | 95% | 98% | -3 |
| Arazzo workflows | 4% | 2% | +2 |
| Governance rules | 29% | 16% | +13 |
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 Checkly 72.5
- 3 Tricentis 68.6
- 4 UiPath 66.6
- 5 BrowserStack 66.3
- 6 Speakeasy 66.3
- 7 Stack Moxie 64.5
- 8 TempMailGrab API 63.2
- 9 Treblle 62.6
- 10 Scorecard 59.4
- 1 Coval 60.7
- 2 Checkly 59.5
- 3 APIContext 59.5
- 4 Postman 55.6
- 5 Speakeasy 52.5
- 6 Scorecard 49.8
- 7 accessiBe 45.2
- 8 Kubeshop 45.1
- 9 Limrun 44.4
- 10 BrowserStack 43.7
Coverage caveat. 111 of 139 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.