No-Code
Providers using this tag (216)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 3 Complete, well-documented, and agent-ready
Strong 14 Solid coverage with minor gaps
Developing 51 Usable, with meaningful gaps to close
Thin 45 Limited public surface area
Emerging 81 Early or largely undocumented
Minimal 22 Almost no public developer surface
APIs with this tag (23)
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 →
Strong 1 Solid coverage with minor gaps
Developing 6 Usable, with meaningful gaps to close
Thin 5 Limited public surface area
Emerging 9 Early or largely undocumented
Minimal 2 Almost no public developer surface
Companies reaching this through an API (6)
These companies publish an API, specification or operation carrying “No-Code” 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
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) | 21% |
Cohort brief
Auto-generatedThe 206 providers in the APIs.io catalog tagged No-Code, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Access Clarity | 42.6 | 23.9 | +18.7 | 206 |
| Developer Ergonomics | 32.4 | 23.2 | +9.2 | 206 |
| Contract Quality | 23.4 | 17.2 | +6.2 | 206 |
| Operational Transparency | 19 | 13 | +6 | 206 |
| Discoverability | 62.3 | 57.9 | +4.4 | 206 |
| Contract Governance | 8.7 | 6.5 | +2.2 | 206 |
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% | 13% | +13 |
| MCP server (first-party) | 23% | 12% | +11 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 12% | 11% | +1 |
| Security | 100% | 98% | +2 |
| Arazzo workflows | 3% | 2% | +1 |
| Governance rules | 21% | 16% | +5 |
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 Coda Project 71.6
- 2 Microsoft Power Platform APIs 69.7
- 3 Zapier 67.4
- 4 Knak 63.4
- 5 Creatio 62.1
- 6 Gumloop 62.1
- 7 Navattic 60.8
- 8 Webflow 60.7
- 9 AutoGPT 59.2
- 10 Synthflow 58.1
- 1 Zapier 66.2
- 2 Webflow 62.5
- 3 Knak 58.3
- 4 Process Street 58.3
- 5 AmunCore 56.5
- 6 Coda Project 55.2
- 7 Synthflow 54.9
- 8 Nanonets 53
- 9 Gumloop 49.8
- 10 Tally 49.4
Coverage caveat. 173 of 206 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.