Humaans vs Remote

Humaans

API tokens are limited by eight scopes and the creator's role, can expire and can be rotated with a seven-day overlap, and rate limits are published with Retry-After on 429. No OpenAPI file, API changelog, official SDK or idempotency keys were found, and prices are by quote, so an agent needs a paying customer's token.

Remote

The REST API has 303 operations in a public OpenAPI document, 78 OAuth scopes split into read and write, a sandbox issued by email with no card, and a hosted MCP server using OAuth with PKCE. The REST changelog link redirects to a login page, and writes have no idempotency key.

Humaans

1. Send Authorization: Bearer <token> to https://app.humaans.io/api. Call GET /api/token-info first to read the token's scopes and expiry
2. Expect a role limit as well as scopes. A token made by a user with the User role reads only public company data and that person's own profile
3. Page with $limit (maximum 250) and $skip, and pass -g to curl because parameters use $ and []
4. On 429 wait the seconds in Retry-After. The bucket holds 40 requests and refills at 7 a second per token
5. Check state before retrying a POST. No idempotency key exists, and DELETE /api/people/:id cannot be undone

Remote

1. Match the token prefix to the host. ra_test_ works only on https://gateway.remote-sandbox.com and ra_live_ only on https://gateway.remote.com
2. Stay under 300 requests a minute per company for customer tokens, shared by every token, and read x-ratelimit-remaining and x-ratelimit-reset (milliseconds)
3. Check for an existing record before retrying a create, or set external_id on employments and treat a 422 for a duplicate as success
4. Fetch the country form schema (GET /v1/countries/{country_code}/{form}) before writing employment data. Country codes are three-letter ISO
5. Use the REST API for unattended work. The MCP server needs a browser sign-in and its write tools cover employee self-service only