Pipelines
PipelinePipelines
Providers using this tag (58)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 2 Complete, well-documented, and agent-ready
Strong 9 Solid coverage with minor gaps
Developing 8 Usable, with meaningful gaps to close
Thin 10 Limited public surface area
Emerging 11 Early or largely undocumented
Minimal 17 Almost no public developer surface
Unrated 1 Not yet scored
APIs with this tag (170)
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 38 Complete, well-documented, and agent-ready
Strong 27 Solid coverage with minor gaps
Developing 44 Usable, with meaningful gaps to close
Thin 33 Limited public surface area
Emerging 23 Early or largely undocumented
Minimal 5 Almost no public developer surface
Companies reaching this through an API (117)
These companies publish an API, specification or operation carrying “Pipelines” 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 117 companies ↓
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 54 providers in the APIs.io catalog tagged Pipelines, 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 | 31.3 | 17.2 | +14.1 | 54 |
| Operational Transparency | 23 | 13 | +10 | 54 |
| Developer Ergonomics | 33 | 23.2 | +9.8 | 54 |
| Contract Governance | 10.6 | 6.5 | +4.1 | 54 |
| Discoverability | 61.8 | 57.9 | +3.9 | 54 |
| Access Clarity | 23.6 | 23.9 | -0.3 | 54 |
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% | 13% | +11 |
| MCP server (first-party) | 25% | 12% | +13 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 22% | 11% | +11 |
| Security | 96% | 98% | -2 |
| Arazzo workflows | 5% | 2% | +3 |
| Governance rules | 24% | 16% | +8 |
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 GitHub Actions 81.3
- 2 Buildkite 66.5
- 3 CircleCI 66.1
- 4 Databricks Asset Bundles 65
- 5 Salesloft 62.5
- 6 Zendesk Sell 60.6
- 7 Pipeliner CRM 57.9
- 8 Talend 57.2
- 9 ZenML 56.2
- 10 Dagger 55.7
- 1 Monaco 61.4
- 2 CircleCI 56.1
- 3 Folk 53.2
- 4 GitLab CI/CD 53.1
- 5 Talend 51.1
- 6 Buildkite 50.6
- 7 GitHub Actions 48.3
- 8 Salesloft 45.4
- 9 Attio 45.3
- 10 Pipeliner CRM 38.5
Coverage caveat. 41 of 54 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 24 October 2026, across 31984 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.