Event-Driven
Providers using this tag (37)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 11 Complete, well-documented, and agent-ready
Strong 5 Solid coverage with minor gaps
Developing 7 Usable, with meaningful gaps to close
Thin 10 Limited public surface area
Emerging 4 Early or largely undocumented
APIs with this tag (41)
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 6 Complete, well-documented, and agent-ready
Strong 5 Solid coverage with minor gaps
Developing 15 Usable, with meaningful gaps to close
Thin 10 Limited public surface area
Emerging 5 Early or largely undocumented
Companies reaching this through an API (31)
These companies publish an API, specification or operation carrying “Event-Driven” 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
37 providers carry this tag directly, and 64 counting the 3 narrower tags below — 27 more to reach.
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 37 providers in the APIs.io catalog tagged Event-Driven, 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 | 53.5 | 24.5 | +29 | 37 |
| Contract Quality | 46.4 | 18.6 | +27.8 | 37 |
| Operational Transparency | 39.2 | 13.2 | +26 | 37 |
| Access Clarity | 45 | 30 | +15 | 37 |
| Contract Governance | 23 | 9.7 | +13.3 | 37 |
| Discoverability | 69.5 | 59.1 | +10.4 | 37 |
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) | 24% | 18% | +6 |
| MCP server (first-party) | 22% | 16% | +6 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 19% | 13% | +6 |
| Security | 100% | 99% | +1 |
| Arazzo workflows | 19% | 1% | +18 |
| Governance rules | 95% | 36% | +59 |
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 Microsoft Azure Functions 76.2
- 2 Oracle Cloud Infrastructure 75.6
- 3 Amazon EventBridge 75.4
- 4 Svix 74.7
- 5 Amazon EventBridge Scheduler 73.3
- 6 Amazon EventBridge Pipes 70.3
- 7 Virto Commerce 69.3
- 8 Google Cloud Eventarc 68.2
- 9 Inngest 68.1
- 10 Google Cloud Functions 67.5
- 1 Svix 53.1
- 2 Oracle Cloud Infrastructure 50
- 3 Google Cloud Eventarc 39.7
- 4 Google Cloud Pub/Sub 38.4
- 5 Inngest 37.9
- 6 Amazon EventBridge 36.7
- 7 Google Cloud Functions 36.1
- 8 Wazo 35.8
- 9 Virto Commerce 34.7
- 10 Amazon EventBridge Scheduler 33.5
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.