Testing
Providers using this tag (136)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 5 Complete, well-documented, and agent-ready
Strong 9 Solid coverage with minor gaps
Developing 34 Usable, with meaningful gaps to close
Thin 37 Limited public surface area
Emerging 35 Early or largely undocumented
Minimal 16 Almost no public developer surface
APIs with this tag (108)
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 7 Solid coverage with minor gaps
Developing 21 Usable, with meaningful gaps to close
Thin 28 Limited public surface area
Emerging 30 Early or largely undocumented
Minimal 1 Almost no public developer surface
Companies reaching this through an API (46)
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
136 providers carry this tag directly, and 190 counting the 6 narrower tags below — 54 more to reach.
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 129 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.8 | 23.2 | +14.6 | 129 |
| Operational Transparency | 26.8 | 13.7 | +13.1 | 129 |
| Contract Quality | 27.9 | 17.6 | +10.3 | 129 |
| Access Clarity | 35.9 | 26.5 | +9.4 | 129 |
| Discoverability | 62.2 | 58.1 | +4.1 | 129 |
| Contract Governance | 9.5 | 6.3 | +3.2 | 129 |
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) | 26% | 14% | +12 |
| MCP server (first-party) | 22% | 12% | +10 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 6% | 11% | -5 |
| Security | 95% | 98% | -3 |
| Arazzo workflows | 4% | 2% | +2 |
| Governance rules | 26% | 14% | +12 |
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 79.6
- 2 Checkly 74
- 3 Tricentis 68
- 4 BrowserStack 67.8
- 5 Speakeasy 67.6
- 6 UiPath 66.3
- 7 Stack Moxie 64.5
- 8 Treblle 63.2
- 9 TempMailGrab API 62.4
- 10 Artillery 57.4
- 1 APIContext 60.1
- 2 Checkly 60
- 3 Coval 59.8
- 4 Postman 54.9
- 5 Scorecard 48.7
- 6 Kubeshop 47.7
- 7 Speakeasy 44.7
- 8 Tricentis 44.6
- 9 Openlayer 44.6
- 10 BrowserStack 44.1
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.