Scheduling
Providers using this tag (330)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 12 Complete, well-documented, and agent-ready
Strong 31 Solid coverage with minor gaps
Developing 67 Usable, with meaningful gaps to close
Thin 73 Limited public surface area
Emerging 89 Early or largely undocumented
Minimal 55 Almost no public developer surface
Unrated 3 Not yet scored
APIs with this tag (147)
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 17 Complete, well-documented, and agent-ready
Strong 19 Solid coverage with minor gaps
Developing 41 Usable, with meaningful gaps to close
Thin 26 Limited public surface area
Emerging 26 Early or largely undocumented
Minimal 18 Almost no public developer surface
Companies reaching this through an API (85)
These companies publish an API, specification or operation carrying “Scheduling” 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 85 companies ↓
Score breakdown
Where this tag sits
330 providers carry this tag directly, and 379 counting the 18 narrower tags below — 49 more to reach.
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 |
|---|---|
| Field Service, Home Services and Trades | 44% |
Cohort brief
Auto-generatedThe 302 providers in the APIs.io catalog tagged Scheduling, 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 | 39.9 | 30 | +9.9 | 302 |
| Contract Quality | 28.4 | 18.6 | +9.8 | 302 |
| Operational Transparency | 19 | 13.2 | +5.8 | 302 |
| Developer Ergonomics | 30.3 | 24.5 | +5.8 | 302 |
| Discoverability | 63.2 | 59.1 | +4.1 | 302 |
| Contract Governance | 12.8 | 9.7 | +3.1 | 302 |
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) | 19% | 18% | +1 |
| MCP server (first-party) | 19% | 16% | +3 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 20% | 13% | +7 |
| Security | 98% | 99% | -1 |
| Arazzo workflows | 2% | 1% | +1 |
| Governance rules | 50% | 36% | +14 |
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 Nylas 93.9
- 2 Elation Health 79.7
- 3 Amazon EventBridge Scheduler 73.3
- 4 Hootsuite 72.8
- 5 ZnanyLekarz 72.7
- 6 Healthie 68.6
- 7 Microsoft Azure Batch 68.6
- 8 Connecteam 68.4
- 9 Chili Piper 68.1
- 10 Chronary 67.8
- 1 Publora 70.2
- 2 FieldRobin 61.7
- 3 Nylas 59.6
- 4 deploy.social 57.2
- 5 Chili Piper 56.3
- 6 Chirpie 53.7
- 7 GreatWait 53.7
- 8 LeanData 52.3
- 9 HoneyBook 52
- 10 Postiz 51.9
Coverage caveat. 214 of 302 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.