iPaaS
Providers using this tag (76)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 8 Complete, well-documented, and agent-ready
Strong 11 Solid coverage with minor gaps
Developing 13 Usable, with meaningful gaps to close
Thin 14 Limited public surface area
Emerging 24 Early or largely undocumented
Minimal 6 Almost no public developer surface
APIs with this tag (13)
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 5 Complete, well-documented, and agent-ready
Strong 3 Solid coverage with minor gaps
Developing 1 Usable, with meaningful gaps to close
Thin 1 Limited public surface area
Emerging 2 Early or largely undocumented
Minimal 1 Almost no public developer surface
Companies reaching this through an API (4)
These companies publish an API, specification or operation carrying “iPaaS” 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
Related tags
Where this tag comes from
Markets provisional
Kin Score markets whose measured providers carry this tag. Share is the fraction of the market's measured providers that carry it — it describes the market, not this tag.
| Market | Share of the market's providers |
|---|---|
| Workflow Automation (iPaaS bridges) | 48% |
Cohort brief
Auto-generatedThe 65 providers in the APIs.io catalog tagged iPaaS, 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 | 43.2 | 24.5 | +18.7 | 65 |
| Access Clarity | 45.9 | 30 | +15.9 | 65 |
| Contract Quality | 34 | 18.6 | +15.4 | 65 |
| Operational Transparency | 24.3 | 13.2 | +11.1 | 65 |
| Contract Governance | 18.3 | 9.7 | +8.6 | 65 |
| Discoverability | 63.7 | 59.1 | +4.6 | 65 |
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) | 26% | 18% | +8 |
| MCP server (first-party) | 32% | 16% | +16 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 15% | 13% | +2 |
| Security | 100% | 99% | +1 |
| Arazzo workflows | 8% | 1% | +7 |
| Governance rules | 66% | 36% | +30 |
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 Tray.ai 89.5
- 2 AWS Step Functions 74.5
- 3 Jitterbit 73.1
- 4 Zapier 72.9
- 5 Workato 70.5
- 6 Emporix 69.1
- 7 Boomi 68.5
- 8 IntegrationOS 68
- 9 Pandium 63.8
- 10 SnapLogic 63.7
- 1 Zapier 66.2
- 2 Tray.ai 61.6
- 3 IntegrationOS 58.5
- 4 Frends 54.2
- 5 Flume Health 53.2
- 6 Workato 52.2
- 7 Syncari 50
- 8 Celigo 49.1
- 9 Emporix 48.5
- 10 AWS Step Functions 45.8
Coverage caveat. 42 of 65 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 14 November 2026, across 41591 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.