Deel publishes 91 APIs on the network with a composite of 59.6 — strong — and an agent-readiness score of 42.3 (agent-ready). Its agentic-access contract enumerates 659 operations, 327 acting, and 10 human-in-the-loop.
Ten. On a platform that pays people in 150 countries.
Three hundred and twenty-seven acting operations, ten pauses
Deel is global payroll, HR, and contractor management. The API covers contracts, payroll, time off, expenses, invoices, employer-of-record, IT provisioning, and SCIM. Half its operations mutate state.
Those state changes are not like GitHub’s. A wrongly-created issue is deleted in a second. A wrongly-terminated employment contract, a mis-run payroll cycle, or an incorrectly filed EOR amendment lands in someone’s bank account, someone’s immigration status, or someone’s tax filing. Reversal means a support case, a correction run, and in some jurisdictions a regulator.
10 human-in-the-loop markers across 327 acting operations is the lowest ratio of any provider in this week’s sweep — lower than Telnyx (61 of 553), lower than Kaltura (41 of 1,250), lower than GitHub (31 of 1,203). Deel’s operations are the least reversible of the set and carry the fewest flagged pauses.
I would like to see that inverted. Contract termination, payroll execution, and EOR amendments are the canonical case for an explicit confirmation step in an agent contract, and they are exactly where the markers are thinnest.
The facet spread
| Facet | Score |
|---|---|
| Commercial clarity | 84.2 |
| Contract quality | 69.8 |
| Operational transparency | 60.5 |
| Discoverability | 50.0 |
| Governance | 41.7 |
| Developer ergonomics | 37.0 |
Commercial clarity at 84.2 is the highest of any provider profiled this week. Deel tells you what things cost. That is a direct consequence of the business — per-employee-per-month pricing that a buyer compares line by line against competitors, published because obscuring it loses deals.
Developer ergonomics at 37.0 is the other end. Ninety-one APIs across employment, payroll, and compliance is an intimidating surface, and the catalog finds little in the way of examples or guided paths into it.
The naming leaks the toolchain
The API entries are named Default API, subpackage_accounting API, subpackage_adjustments API, subpackage_assets API, subpackage_ats API, subpackage_candidates API, subpackage_consent API, subpackage_contractorAmendments API, and so on.
subpackage_ is a code generator’s internal grouping, published as-is. It is the same class of problem Grafana has with Add API and All API — the surface was decomposed mechanically and nobody renamed the results for the people reading them.
It is a small thing that costs more than it looks. Every consumer, human or model, picking an API from this list has to mentally strip a prefix that means nothing to them, and Default API — the entry with a single operation — tells a reader nothing at all.
Takeaway
91 APIs, 659 operations, and the highest commercial clarity in the sweep sitting next to the lowest human-in-the-loop ratio. Deel is unusually honest about what it costs and unusually quiet about which of its 327 acting operations you should not let a machine perform unattended. Payroll is not a domain where the default should be “proceed”.
See the full profile at apis.io/providers/deel/.