Regulatory
Providers using this tag (48)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 1 Complete, well-documented, and agent-ready
Developing 10 Usable, with meaningful gaps to close
Thin 11 Limited public surface area
Emerging 7 Early or largely undocumented
APIs with this tag (22)
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 1 Complete, well-documented, and agent-ready
Strong 3 Solid coverage with minor gaps
Developing 3 Usable, with meaningful gaps to close
Thin 8 Limited public surface area
Emerging 4 Early or largely undocumented
Minimal 3 Almost no public developer surface
Companies reaching this through an API (14)
These companies publish an API, specification or operation carrying “Regulatory” 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 47 providers in the APIs.io catalog tagged Regulatory, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Access Clarity | 30.4 | 26.5 | +3.9 | 47 |
| Contract Governance | 9.7 | 6.3 | +3.4 | 47 |
| Discoverability | 60.5 | 58.1 | +2.4 | 47 |
| Contract Quality | 19 | 17.6 | +1.4 | 47 |
| Developer Ergonomics | 22.9 | 23.2 | -0.3 | 47 |
| Operational Transparency | 11.6 | 13.7 | -2.1 | 47 |
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) | 4% | 14% | -10 |
| MCP server (first-party) | 4% | 12% | -8 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 11% | 11% | 0 |
| Security | 100% | 98% | +2 |
| Arazzo workflows | 0% | 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 Veeva 72.8
- 2 SingleFile 52.5
- 3 EU Open Data Portal 51.4
- 4 Qualio 50
- 5 Google Cloud Assured Workloads 45.6
- 6 AgeChecker.Net 44.2
- 7 openFDA 43.4
- 8 Harbor Compliance 42.8
- 9 SEC EDGAR 41.9
- 10 HMRC UK Tax Authority 40.9
- 1 Veeva 41.5
- 2 Rhizome Ai 39.4
- 3 Regulations.gov 32.5
- 4 SingleFile 30.8
- 5 AgeChecker.Net 30.6
- 6 SEC EDGAR 30.6
- 7 Meddra 27.8
- 8 Qualio 26.4
- 9 FDIC 25.8
- 10 Google Cloud Assured Workloads 24.8
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.