Llms.txt
Providers using this tag (43)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 4 Complete, well-documented, and agent-ready
Strong 13 Solid coverage with minor gaps
Developing 11 Usable, with meaningful gaps to close
Thin 4 Limited public surface area
Emerging 10 Early or largely undocumented
Minimal 1 Almost no public developer surface
APIs with this tag (81)
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 8 Solid coverage with minor gaps
Developing 19 Usable, with meaningful gaps to close
Thin 40 Limited public surface area
Emerging 13 Early or largely undocumented
Companies reaching this through an API (65)
These companies publish an API, specification or operation carrying “Llms.txt” 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 65 companies ↓
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 43 providers in the APIs.io catalog tagged Llms.txt, 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 | 54.4 | 25 | +29.4 | 43 |
| Developer Ergonomics | 47.4 | 22.1 | +25.3 | 43 |
| Operational Transparency | 31.7 | 12.4 | +19.3 | 43 |
| Contract Quality | 37.3 | 18.2 | +19.1 | 43 |
| Discoverability | 69.6 | 57.9 | +11.7 | 43 |
| Contract Governance | 19.9 | 9.4 | +10.5 | 43 |
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) | 63% | 16% | +47 |
| MCP server (first-party) | 67% | 14% | +53 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 28% | 13% | +15 |
| Security | 100% | 98% | +2 |
| Arazzo workflows | 0% | 2% | -2 |
| Governance rules | 67% | 35% | +32 |
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 Cracked API 73.1
- 2 TranscriptFetch 70.9
- 3 Statable Stats API 69.6
- 4 RoxyAPI 67.6
- 5 Autoderm – AI Dermatology API 65.1
- 6 AI for Database 64.9
- 7 Adanos Market Sentiment API 63.9
- 8 Odds API 63.5
- 9 Pagesnap 61.8
- 10 ReefAPI 61
- 1 Agent Ready 74.4
- 2 Cracked API 69.2
- 3 BudgetPixel 60
- 4 Loa Healthcare Pricing API 60
- 5 Statable Stats API 58.5
- 6 TranscriptFetch 56.9
- 7 The Ainglish Project 54.7
- 8 anew 53.6
- 9 APIVerve 51
- 10 Agent Disco 50.2
Coverage caveat. 24 of 43 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 7 November 2026, across 38912 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.