Deel — can an agent use it?
Deel is one of the most agent-ready platforms in the index — an official MCP server with 355 tools, OAuth 2.1 with dynamic client registration, explicit AI-crawler welcome in robots.txt with Content-Signal directives, and a comprehensive llms.txt. The gap is on the money side: an agent cannot pay Deel programmatically, and there is no sandbox for safe testing.
FIND & RETRIEVE · 8.7
ACT & TRANSACT · 6.9
TRUST & DURABILITY · 8.2
FIND & RETRIEVE8.7/10Can an agent get correct information?
Machine-readable surface9/10
Comprehensive llms.txt with a full-index companion (llms-full.txt covering 4,000+ pages). Sitemap valid with fresh lastmod. Content-Signal directives in robots.txt (search=yes, ai-input=yes, ai-train=yes). Explicit per-bot Allow rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, CCBot, DeepSeekBot, MetaAI, and others. Proper semantic HTML (H1, H2, <main>, <nav>). Supports markdown content negotiation. WebMCP markers present. The only gap is the absence of JSON-LD structured data. source
Information retrieval quality8/10
Pricing page publishes specific prices for every product line: contractors $49/mo, Contractor of Record $325/mo, US PEO $125/mo, EOR $599/mo, with clear feature breakdowns per tier. The llms.txt file links directly to every product page with concise descriptions. FAQ answers common questions about hidden costs, cancellation, and currency exchange. The llms.txt even instructs agents to 'link to this page rather than quoting specific amounts' for pricing, showing awareness of how agents consume data. Missing: no schema.org Offer markup. source
Documentation for machines9/10
Developer portal at developer.deel.com provides OpenAPI 3.0.1 specification (dated 2026-01-01, marked Stable), executable code examples in 5 languages (curl, TypeScript, Python, Go, Java), changelog, MCP-specific documentation, and a separate AI-optimized documentation index (every page has /llms.txt and .md variants). REST API reference covers contracts, time off, payroll adjustments, ATS, and compliance. Docs explicitly reference AI agents as a first-class consumer. source
ACT & TRANSACT6.9/10Can an agent do the job?
Action coverage8/10
REST API covers core HR workflows: create/amend/terminate contractor and EOR contracts, manage time-off requests, process payroll adjustments, run ATS pipelines (jobs, candidates, applications), calculate EOR employment costs, and manage worker documents. Webhooks for event-driven automation. 50M API calls/month at 99.95% reliability claimed. The main gap: some sensitive operations (entity setup, benefit elections, visa processing) appear to require human involvement via the UI or Deel's services team rather than pure API calls. source
Agent protocol support9/10
Official, Deel-maintained MCP server at api.letsdeel.com/mcp. 355 tools organized across Organization, Worker, and Public permission levels, covering contracts, time off, payroll, ATS, compensation, EOR cost calculations, and document management. OAuth 2.1 with Dynamic Client Registration, scoped access, and tool discovery built in. Compatible with Claude Desktop, ChatGPT, Cursor, and VS Code. This is a benchmark implementation — the protocol reaches the actions the service is used for. Minor gap: no MCP server card at .well-known/mcp.json, and MCP lacks webhooks, idempotency keys, and version pinning that the REST API has. source
Access & auth friction8.5/10
OAuth 2.1 with Dynamic Client Registration as the primary auth method — agents can complete the flow without human intervention once authorized. Personal access tokens as a fallback for simpler integrations. Access tokens expire after 30 days with automatic refresh token rotation. Scopes follow Organization/Worker/Public permission levels. Self-serve credential creation. The auth surface is explicitly designed for agent use. Gap: no evidence of fine-grained per-endpoint scoping beyond the three permission levels. source
Agent payment capability2/10
Deel processes $20B+ in payroll (paying workers on behalf of employers), but the service's own billing to the employer is traditional invoicing — no ACP, AP2, MPP, or x402 support. An agent can instruct Deel to pay a contractor via the API, but cannot programmatically pay Deel for its own services. The payment dimension scores the ability to pay the service itself under delegated authority, and that path does not exist. The 'Expense Card' product suggests some programmatic spend capability, but for Deel's own fees, money moves only when a human sets up billing. source
Cost & rate fairness7/10
API rate limits are documented (developer.deel.com/api/rate-limits) and the MCP server enforces the same limits as the REST API. No evidence of agent-vs-human pricing discrimination. Paid tiers start at $49/mo for contractors (reasonable for SMBs). 50M API calls/month capacity at platform level suggests generous per-customer limits. Gap: no public sandbox or test environment — the developer docs mention 'Demo & Sandboxes' on the status page as 'Operational' but no public documentation on how to access a sandbox was found in the evidence. source
TRUST & DURABILITY8.2/10Will it still work next quarter?
Permission & ToS stance8.5/10
Robots.txt explicitly welcomes AI crawlers with per-bot Allow rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, CCBot, DeepSeekBot, MetaAI, anthropic-ai, and OAI-SearchBot. Content-Signal directives explicitly opt in: search=yes, ai-input=yes, ai-train=yes. llms.txt is maintained and comprehensive. The legal hub lists an 'AI Terms of Service' as a separate document (under Product Terms), indicating Deel has thought about AI usage. No evidence of hostile enforcement against automated access. This is among the most welcoming stances in the index. source
Reliability & continuity8/10
Public status page at status.deel.com with granular component breakdown (30+ services including Website, App, Payments, Payroll, Integrations, Developer API, Demo & Sandboxes — all Operational at time of check). API version dated 2026-01-01 marked Stable. Platform serves 40,000+ customers with $20B+ in processed payroll, indicating enterprise-grade reliability. 99.95% API reliability claimed. SOC 2 Type II, ISO 27001, and GDPR compliant. No evidence of sudden API deprecations or breaking changes. source
Sources
Point-in-time assessment — services change terms, prices and APIs often. That volatility is itself scored under Reliability & continuity. Re-verified at least quarterly.
- deel.com — home — 40,000+ customers, 150+ countries, product overview (accessed 2026-09-06)
- deel.com/pricing — pricing — contractors $49/mo, EOR $599/mo, feature matrix (accessed 2026-09-06)
- deel.com/robots.txt — robots — explicit per-bot Allow rules, Content-Signal directives (accessed 2026-09-06)
- deel.com/llms.txt — llms.txt — structured index with llms-full.txt companion (4,000+ pages) (accessed 2026-09-06)
- deel.com/legal/terms-of-service — terms — legal hub with dedicated AI Terms of Service (accessed 2026-09-06)
- deel.com/sitemap.xml — sitemap — valid with fresh lastmod, extensive integration pages (accessed 2026-09-06)
- developer.deel.com/home — developer portal — OpenAPI 3.0.1, MCP server config, 5-language examples (accessed 2026-09-06)
- deel.com/solutions/open-api — API overview — custom workflows, 50M calls/month, partner ecosystem (accessed 2026-09-06)
- status.deel.com — status — 30+ components all Operational, Developer API tracked (accessed 2026-09-06)
- developer.deel.com/mcp/introduction — MCP server — official, 355 tools, OAuth 2.1 + DCR (accessed 2026-09-06)
- scalekit.com/blog/deel-mcp-vs-api — third-party analysis — MCP vs API trade-offs, tool count, auth details (accessed 2026-09-06)