Work Orders
Work OrdersWork ordersWorkOrdersWorkorderswork-ordersworkorders
Providers using this tag (43)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 1 Complete, well-documented, and agent-ready
Developing 13 Usable, with meaningful gaps to close
Thin 17 Limited public surface area
Emerging 8 Early or largely undocumented
Minimal 2 Almost no public developer surface
APIs with this tag (40)
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 1 Complete, well-documented, and agent-ready
Strong 2 Solid coverage with minor gaps
Developing 11 Usable, with meaningful gaps to close
Thin 18 Limited public surface area
Emerging 7 Early or largely undocumented
Minimal 1 Almost no public developer surface
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 43 providers in the APIs.io catalog tagged Work Orders, 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 | 42 | 17.5 | +24.5 | 43 |
| Access Clarity | 36.5 | 22.3 | +14.2 | 43 |
| Discoverability | 73.4 | 60.4 | +13 | 43 |
| Developer Ergonomics | 29.8 | 17.9 | +11.9 | 43 |
| Operational Transparency | 21.3 | 11.3 | +10 | 43 |
| Contract Governance | 11 | 6.4 | +4.6 | 43 |
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) | 35% | 16% | +19 |
| MCP server (first-party) | 7% | 7% | 0 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 21% | 9% | +12 |
| Security | 100% | 88% | +12 |
| Arazzo workflows | 7% | 2% | +5 |
| Governance rules | 33% | 13% | +20 |
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 Salesforce 83.3
- 2 Epsilon3 58.5
- 3 MaintainX 56.5
- 4 Arthur Online 51.8
- 5 Facilio 49.3
- 6 ServiceChannel 45.5
- 7 Oracle Fusion Cloud Applications 45.3
- 8 RentCheck 44.3
- 9 Zuper 43.8
- 10 SMS Assist 43.7
- 1 Salesforce 52.2
- 2 Facilio 50.2
- 3 Arthur Online 37.9
- 4 Epsilon3 33.8
- 5 SAP Fieldglass 33.5
- 6 MaintainX 32.9
- 7 Roadsync 31.4
- 8 1Factory 30.6
- 9 IFS 28.7
- 10 Zuper 28.1
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for tags
7 MCP tools reach this
find_tagsBrowse and filter every tag in the catalog.get_cohortThis tag as a scored cohort — every provider carrying it, with scores.cohort_statsPRO — the distribution across this tag: mean, median, band split, adoption rates.cohort_rankingsPRO — the leaderboard, on composite AND agent-readiness axes.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/tags/work-orders"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/work-orders"
curl "https://apis.io/api/v1/cohorts/tag/work-orders/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.