Event-Driven
Providers using this tag (42)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 4 Complete, well-documented, and agent-ready
Strong 8 Solid coverage with minor gaps
Developing 9 Usable, with meaningful gaps to close
Thin 15 Limited public surface area
Emerging 4 Early or largely undocumented
Minimal 2 Almost no public developer surface
APIs with this tag (55)
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 4 Complete, well-documented, and agent-ready
Strong 6 Solid coverage with minor gaps
Developing 17 Usable, with meaningful gaps to close
Thin 21 Limited public surface area
Emerging 6 Early or largely undocumented
Companies reaching this through an API (37)
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
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 40 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 |
|---|---|---|---|---|
| Contract Quality | 50.3 | 20.1 | +30.2 | 40 |
| Developer Ergonomics | 48.7 | 23.4 | +25.3 | 40 |
| Operational Transparency | 29.5 | 14 | +15.5 | 40 |
| Contract Governance | 19.4 | 6.5 | +12.9 | 40 |
| Access Clarity | 38.3 | 26.5 | +11.8 | 40 |
| Discoverability | 68.2 | 61 | +7.2 | 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) | 13% | 10% | +3 |
| MCP server (first-party) | 10% | 13% | -3 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 18% | 11% | +7 |
| Security | 100% | 96% | +4 |
| Arazzo workflows | 20% | 2% | +18 |
| Governance rules | 70% | 13% | +57 |
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 Svix 80.4
- 2 Virto Commerce 76
- 3 Oracle Cloud Infrastructure 74.7
- 4 Microsoft Azure Functions 68.8
- 5 Amazon Lambda 61.8
- 6 Amazon EventBridge Pipes 60.9
- 7 Amazon EventBridge Scheduler 60.9
- 8 Inngest 60.4
- 9 Amazon EventBridge 59.9
- 10 Gravitee 56.8
- 1 Svix 49.4
- 2 Oracle Cloud Infrastructure 49.3
- 3 Virto Commerce 37.7
- 4 Amazon EventBridge Scheduler 37.1
- 5 Wazo 35
- 6 Hookdeck 30.9
- 7 Amazon EventBridge Pipes 30.6
- 8 Gravitee 30.4
- 9 Microsoft Azure Functions 30
- 10 KEDA 30
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.