Can AI agents automate Deel?

Deel is automatable today through its REST API. This record is the Deel global workforce platform (contracts, payroll, HR, and Deel IT). Production calls use https://api.letsdeel.com/rest over HTTPS. The sandbox base is https://api-staging.letsdeel.com/rest. Tokens are sent as Authorization Bearer. Organization tokens cover organization resources such as contracts, timesheets, invoices, and SCIM. Personal tokens are limited to the user. Worker API tokens represent one EOR worker. OAuth2 is the other documented method. The quickstart lists webhooks, rate limits, and idempotency, and names Employer of Record, contractors, global payroll, HRIS, Deel IT, and platform APIs. Deel hosts an MCP server at https://api.letsdeel.com/mcp over HTTP with JSON-RPC 2.0 and SSE. Tools map to API operations. Organization, worker, and public tools use different permission levels. Examples include getListOfPeople, listOfContracts, and createTimeOffRequest. MCP auth is OAuth2 with dynamic client registration and PKCE, or a personal access token bearer fallback. OAuth access tokens last 1 hour. Refresh tokens last 30 days and are single use. Public initialize and tools/list calls do not require a token. Protected tools return 401 without one. https://developer.deel.com/llms.txt is a first-party developer index for the REST API, webhooks, and MCP. A published language SDK and connector catalogs were not established. Computer-use viability is unassessed. API scores 8. MCP scores 7. API is the best path because it is the HTTP contract for sandbox and production, including organization tokens for server-to-server work. MCP is the same operations behind an assistant connector.

Best path today: api · Overall automatability: 8/10