Providers using this tag (134)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 1 Complete, well-documented, and agent-ready
Strong 12 Solid coverage with minor gaps
Developing 41 Usable, with meaningful gaps to close
Thin 44 Limited public surface area
Emerging 29 Early or largely undocumented
Minimal 7 Almost no public developer surface
APIs with this tag (97)
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 14 Solid coverage with minor gaps
Developing 26 Usable, with meaningful gaps to close
Thin 33 Limited public surface area
Emerging 22 Early or largely undocumented
Minimal 1 Almost no public developer surface
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 134 providers in the APIs.io catalog tagged SQL, 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 | 38.7 | 17.9 | +20.8 | 134 |
| Contract Quality | 35.8 | 17.5 | +18.3 | 134 |
| Operational Transparency | 24 | 11.3 | +12.7 | 134 |
| Access Clarity | 34.6 | 22.3 | +12.3 | 134 |
| Discoverability | 68.3 | 60.4 | +7.9 | 134 |
| Contract Governance | 12.4 | 6.4 | +6 | 134 |
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) | 27% | 16% | +11 |
| MCP server (first-party) | 15% | 7% | +8 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 17% | 9% | +8 |
| Security | 98% | 88% | +10 |
| Arazzo workflows | 6% | 2% | +4 |
| Governance rules | 40% | 13% | +27 |
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 Plinth US Grants Data 70.5
- 2 Aidbox 63.2
- 3 Cloudflare 62
- 4 Halo Connect 59.7
- 5 Databricks 59.1
- 6 Feldera 58.3
- 7 VividCortex 57.7
- 8 AmunCore 56.5
- 9 Azure Databricks 56.5
- 10 Census 56.1
- 1 Equals 54.4
- 2 Plinth US Grants Data 51.8
- 3 Cloudflare 44.5
- 4 Aidbox 43.7
- 5 Oracle 41.9
- 6 AmunCore 41.5
- 7 Ocient 41.4
- 8 Databricks 40.1
- 9 Kinetica 39.4
- 10 Skyvia 36.4
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for tags
7 MCP tools reach this
find_tagsBrowse and filter every tag in the catalog.get_cohortThis tag as a scored cohort — every provider carrying it, with scores.cohort_statsPRO — the distribution across this tag: mean, median, band split, adoption rates.cohort_rankingsPRO — the leaderboard, on composite AND agent-readiness axes.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/tags/sql"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/sql"
curl "https://apis.io/api/v1/cohorts/tag/sql/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.