# Humaans

> Humaans is an HR system of record for employee profiles, job roles, compensation, time away, timesheets, documents and equipment. Agents reach it through a REST API with scoped access tokens, signed webhooks and a hosted MCP server that uses OAuth.

- Canonical: https://www.anchorterminal.com/tools/humaans
- Markdown: https://www.anchorterminal.com/tools/humaans.md (~7,350 tokens)
- Slim: https://www.anchorterminal.com/tools/humaans.min.md (~2,230 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/tools/humaans.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-08

## Overview

**Grade C · 54.4/100 · rank #529 of 722 · #7 in HR & employee operations · not agent-ready · confidence medium**


## Assessment

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.

## Facts

| Field | Value |
| --- | --- |
| Vendor | Humaans Software UK Ltd (https://humaans.io) |
| Kind | HTTP API |
| Category | HR & employee operations (https://www.anchorterminal.com/categories/hr) |
| Transport | HTTP |
| Endpoint | `https://app.humaans.io/api` |
| Auth | OAuth or key · Access is granted by a customer, with no self-serve route for outsiders. A signed-in user creates an API access token in the Humaans app and sends it as a Bearer header. The token is limited by any of eight scopes and by its creator's role (Owner, Admin, Finance, Tech, Manager or User), can be set to expire after 1 to 365 days, and can be rotated with the old secret valid for up to seven days. The hosted MCP server at https://mcp.humaans.ai/mcp uses OAuth 2.0 with dynamic client registration and PKCE, signs the user in through a browser and follows that person's permissions, with 32 scopes chosen at connection. |
| Pricing | Paid (Paid) · No public prices. The Growth and Enterprise plans and the Athena agent platform all say Talk to sales, and the terms describe per-seat fees set in a sales agreement. No free tier or trial was found. Growth lists Integrations and API access. Enterprise adds Webhooks and a dedicated sandbox account, and integration builders can ask for a sandbox through a request form. The MCP server is included for all customers at no extra cost per the MCP page (https://humaans.io/pricing, checked 2026-10-08). |
| x402 | No · No x402, MPP or L402 in the API reference, the terms or the pricing page (checked 2026-10-08). |
| Licence | Proprietary service under Humaans' Terms of Service |
| Docs | https://docs.humaans.io/api/ |
| llms.txt | not found |
| Last release | 2026-09-10 |
| Surface graded | The public REST API at https://app.humaans.io/api with scoped access tokens. The hosted MCP server is recorded but its tool list could not be read without signing in |
| API coverage | 174 method and path pairs across 50 resources (86 GET, 30 POST, 29 PATCH, 29 DELETE). People, job roles, compensations, bank accounts, emergency contacts, working patterns, time away with policies, allocations and adjustments, timesheets, documents and identity documents, equipment, org units, job library, custom fields, data exports and webhooks |
| Credentials | Bearer API access token created in the app. Scopes `public:read`, `private:read`, `private:write`, `compensations:read`, `compensations:write`, `documents:read`, `documents:write` and `webhooks:manage`. Optional expiry of 1 to 365 days with email warnings, and rotation with up to seven days of overlap. `GET /api/token-info` returns scopes and expiry |
| Permissions | A token can do only what its creator can. Owner has full access, Admin edits all profiles, Finance reads all profiles, Tech sees limited data, Manager sees reports' data and User sees their own. Compensation defaults to Owner and Finance, personal documents to Owner |
| MCP server | Hosted at https://mcp.humaans.ai/mcp. OAuth 2.0 with dynamic client registration and PKCE S256 against app.humaans.io, 32 scopes including `timeAway:write`, `workflows:write` and `auditLog:read`. Launched April 2026 and opened to all Growth and Enterprise customers on 8 June 2026. The vendor's page names the tools `find_people`, `find_compensations`, `create_compensations` and `send_esign_document` |
| Rate limits | Per token. A bucket of 40 requests refilling at 7 a second, about 400 a minute. `X-RateLimit-Limit`, `X-RateLimit-Remaining` and `X-RateLimit-Policy` headers, and `Retry-After` on 429 |
| Errors | JSON error object with id, code, name, message and per-field `issues`. 400, 401, 403, 404, 405, 409, 413, 422 (ValidationError, Unprocessable, EmailTaken), 429, 500, 502 and 503 documented |
| Pagination | `$limit` (default 100, maximum 250) and `$skip`, with `total` in each response. Filters `$in`, `$nin`, `$gt`, `$gte`, `$lt`, `$lte` and `$or` on listed fields. Incremental sync by `updatedAt` with `$includeDeleted=true`, and deleted records kept as tombstones for 30 days |
| Webhooks | 28 event types across time away, people, bank accounts, job roles, compensation, emergency contacts and equipment. Signed with HMAC SHA-256 in `webhook-signature`, sent from three published IPv4 addresses and one IPv6 range, retried with exponential backoff, and disabled after 5 days of failures. Listed under the Enterprise plan |
| Time away | Create, update and delete entries, and approve or decline by setting `requestStatus` to approved or declined with a `reviewNote` on `PATCH /api/time-away/:id`. Types, policies, periods, allocations and adjustments have their own endpoints |
| Onboarding | `POST /api/people` with status `newHire` creates a pending hire that only Owner and Admin can see until it is made active. No workflow or task endpoints are in the REST reference. The MCP page says workflows such as onboarding can be started through the MCP server |
| Versioning | None. The docs commit to no backward-incompatible changes, say unused APIs may be removed, and say any future versioning will not break the existing API. Four performance resources are marked Preview |
| Sandbox | A dedicated sandbox account is listed under the Enterprise plan. Integration builders can ask for one through a form titled Request a Sandbox Account for Integration |
| Audit | The audit log records who acted, what changed, when and from where, with filters by actor, action, field and space. Unlimited audit logs and export are listed under Enterprise |
| Certifications | SOC 2 Type II and ISO 27001:2022 per humaans.io/security, with reports in the trust centre. Hosted on Google Cloud in the EU, AES-256 at rest with application-level encryption, regular penetration tests |
| Status | humaansstatus.io on Instatus with Website, Platform and API components, 90-day uptime bars and RSS and Atom feeds |
| Sub-processors | DPA Annex C, effective 6 October 2026. Google Cloud EMEA (infrastructure, Ireland), AWS (backups), Stripe, Postmark and Svix among the core set. Google, Anthropic and OpenAI for AI models, defaulting to the EEA or Switzerland. 14 days' notice of additions |
| Capabilities | hr.employees, hr.time-off, hr.org, hr.documents, hr.onboarding |
| Tags | hosted, sales-led, api-key, oauth, mcp, webhooks, sandbox, status-page, soc2, iso27001, eu-hosted |
| JSON | https://www.anchorterminal.com/api/v1/tools/humaans.json |

## Score breakdown (methodology v0.4, October 2026 research run)

Assessed 2026-10-08 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points.

| Category | Weight | This run | Score (0–100) | Points |
| --- | --- | --- | --- | --- |
| Reliability | 16% | 20 | 70 | 14.0 |
| Performance | 10% | pending | pending | n/a |
| Schema & documentation | 13% | 16.2 | 44 | 7.2 |
| Agent ergonomics | 13% | 16.2 | 60 | 9.8 |
| Security & auth | 14% | 17.5 | 70 | 12.2 |
| Payments & pricing | 10% | 12.5 | 0 | 0.0 |
| Task success | 10% | pending | pending | n/a |
| Maintenance & community | 7% | 8.8 | 56 | 4.9 |
| Transparency & trust (editorial 65, provenance 81) | 7% | 8.8 | 73 | 6.4 |
| Negative events | up to −15 | up to −15 | none recorded | 0 |
| **Total** | | | | **54.4 → C** |

### Why each score

- Reliability 70: Graded on the public REST API, as a hosted service. Instatus page at humaansstatus.io with Website, Platform and API components and 90-day uptime bars (20). One incident in the last 90 days, a major outage of 1 hour 19 minutes on 7 September 2026 affecting Platform and API, with API uptime shown as 99.94% (10). The rate limit is published as a bucket of 40 requests refilling at 7 a second per token, about 400 a minute (15). 429 carries `Retry-After` and the docs ask clients to back off, but no idempotency keys were found for writes (10). The Enterprise plan lists 99.9% uptime on the pricing page, with no SLA document or remedy found in the terms (5). The API is generally available, with four performance resources marked Preview (10).
- Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes.
- Schema & documentation 44: No OpenAPI or other machine-readable contract was found (0). humaans.io/llms.txt is a marketing summary with no API content, and the reference is one static HTML page of about 2 MB with no Markdown version (3). Each resource states its purpose, endpoints and required scopes, and notes behaviours such as new-hire creation and permanent deletion, without guidance on when to choose another endpoint (13). Parameters are typed with required flags, nullability, enumerated values in prose and rules such as at most one of `startTime` or `startPeriod` (11). Every endpoint has a curl example and a sample response, and the error object and 14 status and name pairs are documented (13). The API is unversioned by design with a written promise against incompatible changes, and no API changelog was found (4).
- Agent ergonomics 60: `$limit` sizes pages, `$select` appears on three list endpoints only, and the `public:read` scope returns trimmed profiles (13). Offset pagination with `$limit` up to 250 and `$skip`, filters with `$in`, `$nin`, `$gt`, `$gte`, `$lt`, `$lte` and `$or`, sorting by `updatedAt` and tombstones for deletions, with no cursor (18). Errors carry an id, code, name, message and per-field `issues` with reasons (17). No idempotency keys. 429 carries `Retry-After`, and the MCP tool annotations could not be read (5). Reads need few parameters and list defaults are stated. No official SDK was found (7).
- Security & auth 70: API tokens are revocable, limited by eight scopes and by the creator's role, can expire after 1 to 365 days and can be rotated with the old secret valid for up to seven days. They travel only in the `Authorization` header. The MCP server uses OAuth 2.0 with dynamic client registration, PKCE S256 and 32 scopes (30). Read and write scopes are separate and `public:read` limits a token to company-public data. No confirmation step was found for deletes, which the docs call permanent (13). The API returns text written by employees and no guidance for API consumers was found. The security page describes permission-based context filtering for Humaans' own AI functions (3). The audit log records actor, change, time and origin and there is an `auditLog:read` OAuth scope. Whether token calls are attributed was not stated (11). SOC 2 Type II, ISO 27001:2022, regular penetration tests and a security@humaans.io contact. No security.txt and no bug bounty found (13).
- Payments & pricing 0: No x402, MPP or L402 (0). Growth, Enterprise and Athena all say Talk to sales, with no price on the page (0). No free tier or trial was found. A sandbox account is listed under Enterprise and through a request form for integration builders (0). Tokens are created by a signed-in user in the Humaans app and the MCP server needs a browser sign-in (0).
- Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored.
- Maintenance & community 56: The newest dated product update is 10 September 2026, 28 days before the check (30). Four dated product posts in the last 90 days, on 11 and 25 August and 1 and 10 September 2026. These are product announcements, not an API changelog (20). Support is by email and a help centre, and no API changelog, public issue tracker or developer forum was found (6). No official SDK was found, and the MCP registry lists only a third-party stdio server from Mindstone (0). No public packages or CI to assess (0).
- Transparency & trust 73: Closed service with public Terms of Service effective 6 October 2026 and a link to the previous version (15). The terms and the DPA agree on a 30-day window to request return of data, deletion from production afterwards and purging of remaining copies within 90 days. The DPA sets 72 hours for incident notice. The privacy policy covers only data Humaans controls and points to the DPA for customer data (26). The versioning section promises no incompatible changes but says unused APIs may be removed, with no notice period or dated notices found (4). Annex C of the DPA names each sub-processor, its purpose and location, with 14 days' notice of additions, EU hosting on Google Cloud, and AI processing by Google, Anthropic and OpenAI defaulting to the EEA or Switzerland (20).

Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (18 items): https://www.anchorterminal.com/fixes/humaans.md (JSON https://www.anchorterminal.com/fixes/humaans.json)

### What we couldn't check

- unchecked: the MCP server's tool list, input schemas and annotations. https://mcp.humaans.ai/mcp answers 401 without an OAuth token, so only the four tool names on the MCP page were seen
- unchecked: the trust centre at trust.humaans.io, which is drawn by script and returned no text to our reader
- unchecked: the body text of the product update posts, which loaded with titles and dates only
- Whether the 99.9% uptime line on the Enterprise plan is backed by an SLA document with remedies. None was found in the Terms of Service
- Whether calls made with an API token appear in the customer's audit log with the token named
- Whether webhooks are available on the Growth plan. The pricing page lists Integrations and API access under Growth and Webhooks under Enterprise
- The sandbox is listed as an Enterprise plan item and through a request form for integration builders. Its terms and cost were not established
- The site footer reads Humaans Inc. while the terms, privacy policy and DPA name Humaans Software UK Ltd

### Sources

- API reference (guide, scopes, roles, pagination, rate limiting, errors, versioning, webhooks, every resource): <https://docs.humaans.io/api/> (seen 2026-10-08)
- MCP server page: <https://humaans.io/mcp> (seen 2026-10-08)
- OAuth authorisation server metadata: <https://app.humaans.io/.well-known/oauth-authorization-server> (seen 2026-10-08)
- MCP protected resource metadata: <https://mcp.humaans.ai/.well-known/oauth-protected-resource> (seen 2026-10-08)
- pricing: <https://humaans.io/pricing> (seen 2026-10-08)
- status page: <https://humaansstatus.io> (seen 2026-10-08)
- status history: <https://humaansstatus.io/history> (seen 2026-10-08)
- status history feed: <https://humaansstatus.io/history.rss> (seen 2026-10-08)
- Terms of Service, effective 6 October 2026: <https://humaans.io/terms> (seen 2026-10-08)
- Privacy Policy, effective 6 October 2026: <https://humaans.io/privacy> (seen 2026-10-08)
- Data Processing Addendum and sub-processors, effective 6 October 2026: <https://humaans.io/data-processing> (seen 2026-10-08)
- security page: <https://humaans.io/security> (seen 2026-10-08)
- audit log page: <https://humaans.io/features/audit-log> (seen 2026-10-08)
- product updates: <https://humaans.io/blog/tag/product-updates> (seen 2026-10-08)
- newest product update, 10 September 2026: <https://humaans.io/blog/meet-your-new-ai-companion-now-20x-more-powerful> (seen 2026-10-08)
- MCP general availability post, 8 June 2026: <https://humaans.io/blog/mcp-now-available-to-all> (seen 2026-10-08)
- llms.txt on the marketing site: <https://humaans.io/llms.txt> (seen 2026-10-08)
- security.txt (404): <https://humaans.io/.well-known/security.txt> (seen 2026-10-08)
- npm search for humaans: <https://registry.npmjs.org/-/v1/search?text=humaans&size=10> (seen 2026-10-08)
- MCP registry search: <https://registry.modelcontextprotocol.io/v0/servers?search=humaans> (seen 2026-10-08)
- domain registration (RDAP): <https://rdap.identitydigital.services/rdap/domain/humaans.io> (seen 2026-10-08)

## Who's behind it (provenance 81/100, checked 2026-10-08)

| Check | Finding | Points |
| --- | --- | --- |
| Legal entity named | Humaans Software UK Ltd | 20/20 |
| Domain age | humaans.io, registered 2019-03-29 (7 years) | 11/15 |
| Endpoint on the vendor's domain | app.humaans.io | 15/15 |
| Terms of service | read, states 6 of the 7 things a reader expects, and has 2 clauses that cost points | 5.1/10 |
| Privacy policy | read, states 8 of the 8 things a reader expects | 10/10 |
| Status page | humaansstatus.io | 10/10 |
| Changelog | published | 10/10 |
| security.txt | not found | 0/10 |

The Terms of Service (effective 6 October 2026) define Humaans as Humaans Software UK Ltd and govern the subscription and the platform, including access through the published APIs. They are governed by the laws of England and Wales.

The privacy policy (effective 6 October 2026) names Humaans Software UK LTD, company number 11496946, Office 7, 35-37 Ludgate Hill, London EC4M 7JN. It covers data Humaans controls and says customer employee data is governed by the Data Processing Addendum at https://humaans.io/data-processing.

The site footer reads Humaans Inc. with offices in London, New York and San Francisco. The legal documents name only the UK company.

The API answers at https://app.humaans.io/api. The MCP server is on a second domain, mcp.humaans.ai, and names app.humaans.io as its authorisation server. The status page is on humaansstatus.io.

humaans.io/.well-known/security.txt returns 404. The API reference gives security@humaans.io for reporting security issues.

The changelog link is the product updates section of the blog. No API changelog was found.

RDAP for humaans.io gives a registration date of 2019-03-29.

### Terms and privacy, as read

A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice.

**Terms of service** (https://humaans.io/terms), read 2026-10-08, dated 2026-10-06, states 6 of the 7 things a reader expects.

- To know. Restricts automated access (costs points). "use any automated means (including bots, scrapers, or similar technology) to access the Platform, except through our published APIs;"
- To know. Restricts benchmarking or competitive use (costs points). "use the Platform to develop, directly or indirectly, a product or service that competes with the Platform or the Subscribed Services."
- Gives the date it was last updated. Last updated 2026-10-06.
- Names the governing law or courts. The law of England and Wales.
- States a limit on its liability. Capped at the fees paid in the 12 months before the claim.
- Says how changes to the terms are announced. Gives 90 days of notice before a change.
- Not found in the text. Refers to a service level or uptime commitment.
- Also in the text (2026-10-08). Humaans AI is switched on by default when a customer account is created, where the subscription includes it. "Where Humaans AI is included in the subscription, it is enabled by default when a customer account is created."
- Also in the text (2026-10-08). Humaans may use customer logos for marketing. "We may from time to time use customer logos for marketing purposes."
- Also in the text (2026-10-08). Humaans reserves the right to raise subscription fees when a subscription period renews. "On renewal of a Subscription Period, we reserve the right to increase the Subscription Fees for the subsequent Subscription Period."

**Privacy policy** (https://humaans.io/privacy), read 2026-10-08, dated 2026-10-06, states 8 of the 8 things a reader expects.

- Gives the date it was last updated. Last updated 2026-10-06.
- Says how long data is kept. Names a period of 90 days.
- Says whether personal data is sold or shared for advertising. Says it does not sell personal data.
- Gives a privacy contact. privacy@humaans.io.
- Says where data is transferred or stored. Relies on standard contractual clauses.
- Also in the text (2026-10-08). Humaans says it does not use customer personal data to train, improve or develop general-purpose AI or machine learning models. "We do not use Customer Personal Data to train, improve or develop general-purpose AI or machine learning models."

## Live (updated 2026-10-08 22:39 UTC)

- Right now: up, HTTP 404, 55 ms, checked 2026-10-08 22:39 UTC (get on `https://app.humaans.io/api`)
- Uptime 24h 100.0% (36 probes) · 30 days 100.0% (36 probes) · p50 46 ms · p95 92 ms
- Vendor status page: unknown, no machine-readable status found
- Always current: https://www.anchorterminal.com/api/v1/live/humaans.json

## Probe metrics

Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score.

## Strengths

- API tokens carry any of eight scopes, are capped by the creator's role, can expire after 1 to 365 days and rotate with a seven-day overlap
- Rate limit published as a token bucket of 40 refilling at 7 a second, with `X-RateLimit-*` headers and `Retry-After` on 429
- Time away requests can be approved or declined by setting `requestStatus` on `PATCH /api/time-away/:id`
- Incremental sync is documented, with `updatedAt` filters and tombstones for records deleted in the last 30 days
- DPA, sub-processor list with locations and 14 days' notice of changes are public, with SOC 2 Type II and ISO 27001:2022 stated

## Weaknesses

- No OpenAPI file or Markdown docs. The reference is one HTML page of about 2 MB
- No public price, free tier or trial. Growth and Enterprise both say Talk to sales
- No idempotency keys, and deletes are permanent with no confirmation step
- The API is unversioned with no API changelog, and the docs say unused APIs may be removed
- No official SDK found. The only npm package and MCP registry entry come from a third party

## Before you call it (notes for agents)

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

## Connect

First request:

```bash
curl https://app.humaans.io/api/me \
  -H 'Authorization: Bearer <your_api_access_token>'
```

Through letme (picks today, calling later): https://letme.dev/humaans. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md

## Similar tools

Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last.

| Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown |
| --- | --- | --- | --- | --- | --- | --- |
| Deel | B | 69.1 | 168 | hr.employees, hr.time-off, hr.org, hr.onboarding, hr.documents | no | https://www.anchorterminal.com/tools/deel.md |
| BambooHR | C | 61.7 | 357 | hr.employees, hr.time-off, hr.org, hr.onboarding, hr.documents | no | https://www.anchorterminal.com/tools/bamboohr.md |
| Rippling | C | 60.8 | 386 | hr.employees, hr.time-off, hr.org, hr.onboarding, hr.documents | no | https://www.anchorterminal.com/tools/rippling.md |
| HiBob | C | 57 | 484 | hr.employees, hr.time-off, hr.org, hr.onboarding, hr.documents | no | https://www.anchorterminal.com/tools/hibob.md |
| Zoho People | C | 55 | 523 | hr.employees, hr.time-off, hr.org, hr.onboarding, hr.documents | no | https://www.anchorterminal.com/tools/zoho-people.md |
| Factorial | B | 66.3 | 239 | hr.employees, hr.time-off, hr.org, hr.documents | no | https://www.anchorterminal.com/tools/factorial.md |

## Panel reviews (0)

Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): .

Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md

## Notable

- API tokens are limited by eight scopes and by the creator's role, with optional expiry of 1 to 365 days and rotation that keeps the old secret valid for up to seven days (source: <https://docs.humaans.io/api/>)
- The hosted MCP server at https://mcp.humaans.ai/mcp uses OAuth 2.0 with dynamic client registration and has been open to all Growth and Enterprise customers since 8 June 2026 (source: <https://humaans.io/mcp, https://humaans.io/blog/mcp-now-available-to-all>)
- Each token has a bucket of 40 requests refilling at 7 a second, and 429 responses carry `Retry-After` (source: <https://docs.humaans.io/api/>)
- The API is unversioned. The docs commit to no incompatible changes but say unused APIs may be removed (source: <https://docs.humaans.io/api/>)
- humaansstatus.io lists one incident in the last 90 days, a major outage of 1 hour 19 minutes on 7 September 2026 on Platform and API (source: <https://humaansstatus.io/history>)
- The Terms of Service, Privacy Policy and DPA were all reissued with an effective date of 6 October 2026 and name Humaans Software UK Ltd (source: <https://humaans.io/terms>)
- humaans.io/llms.txt exists but is a marketing summary with no API content, so the listing records no llms.txt for the docs (source: <https://humaans.io/llms.txt>)

## Compare

- [BambooHR vs Humaans](https://www.anchorterminal.com/compare/bamboohr-vs-humaans.md): C 61.7 vs C 54.4
- [Deel vs Humaans](https://www.anchorterminal.com/compare/deel-vs-humaans.md): B 69.1 vs C 54.4
- [Factorial vs Humaans](https://www.anchorterminal.com/compare/factorial-vs-humaans.md): B 66.3 vs C 54.4
- [HiBob vs Humaans](https://www.anchorterminal.com/compare/hibob-vs-humaans.md): C 57 vs C 54.4
- [Humaans vs Rippling](https://www.anchorterminal.com/compare/humaans-vs-rippling.md): C 54.4 vs C 60.8
- [Humaans vs Zoho People](https://www.anchorterminal.com/compare/humaans-vs-zoho-people.md): C 54.4 vs C 55

## Verify this listing

For the vendor. The badge or a plain link to this page verifies the listing, from a page on humaans.io or one of its subdomains. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "humaans", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify

HTML badge:

```html
<a href="https://www.anchorterminal.com/tools/humaans"><img src="https://www.anchorterminal.com/badges/humaans.svg" alt="Humaans on Anchor Terminal" height="20"></a>
```

Markdown badge, for a README:

```markdown
[![Humaans on Anchor Terminal](https://www.anchorterminal.com/badges/humaans.svg)](https://www.anchorterminal.com/tools/humaans)
```

Plain link:

```html
<a href="https://www.anchorterminal.com/tools/humaans">Humaans on Anchor Terminal</a>
```

## Share this listing

For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Humaans is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score.

- Dark: https://www.anchorterminal.com/assets/share/humaans-dark.png
- Light: https://www.anchorterminal.com/assets/share/humaans-light.png