Kafka
Kafkakafka
Providers using this tag (40)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 1 Complete, well-documented, and agent-ready
Strong 3 Solid coverage with minor gaps
Developing 13 Usable, with meaningful gaps to close
Thin 14 Limited public surface area
Emerging 8 Early or largely undocumented
Minimal 1 Almost no public developer surface
APIs with this tag (34)
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 9 Usable, with meaningful gaps to close
Thin 13 Limited public surface area
Emerging 8 Early or largely undocumented
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 40 providers in the APIs.io catalog tagged Kafka, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Contract Quality | 44.9 | 17.5 | +27.4 | 40 |
| Developer Ergonomics | 33.9 | 17.9 | +16 | 40 |
| Operational Transparency | 25.8 | 11.3 | +14.5 | 40 |
| Access Clarity | 33.1 | 22.3 | +10.8 | 40 |
| Contract Governance | 15.3 | 6.4 | +8.9 | 40 |
| Discoverability | 66.9 | 60.4 | +6.5 | 40 |
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) | 30% | 16% | +14 |
| MCP server (first-party) | 8% | 7% | +1 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 13% | 9% | +4 |
| Security | 98% | 88% | +10 |
| Arazzo workflows | 10% | 2% | +8 |
| Governance rules | 68% | 13% | +55 |
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 Oracle Siebel 67.1
- 2 Red Hat 59.1
- 3 Azure Event Hubs 57.1
- 4 Datadog 57.1
- 5 Oracle 53
- 6 Netcracker 52.8
- 7 U.S. Department of Transportation 52.2
- 8 Kong 51.2
- 9 WarpStream 49.3
- 10 Oracle Database 47.8
- 1 Red Hat 52.3
- 2 Oracle 41.9
- 3 Datadog 38.3
- 4 Netcracker 36.8
- 5 Kong 35.8
- 6 Sensors Data 32.8
- 7 Oracle Siebel 31.3
- 8 Gravitee 30.4
- 9 Soveren 29.4
- 10 Azure Event Hubs 29.1
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/kafka"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/kafka"
curl "https://apis.io/api/v1/cohorts/tag/kafka/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.