Head to head · HR records · October 2026 research run

HiBob vs Rippling

Rippling scores 65.5 (B) on agent readiness against HiBob's 51.6 (D), and leads in 5 of 7 scored categories. HiBob leads on schema & documentation and transparency & trust. Both do hr records.

Best HR systems and employee records for AI agents · All 28 hr comparisons

Which one, for what

HiBob D

Best for An agent working inside a company that already runs Bob and needs field-level control over employee data, time off requests, documents and tasks.

Ahead on

  • Schema & documentation, 78 against 73
  • Transparency & trust, 71 against 56

Also in its favour

  • No incidents deducted, where Rippling loses 3 points for them

Watch for

No public price, free tier or trial. The sandbox is a purchased module

Rippling B

Best for An agent working for a company already on Rippling that needs scoped reads of people, organisation and time off data, and writes that wait for human review.

Ahead on

  • Reliability, 77 against 40
  • Agent ergonomics, 75 against 47
  • Security & auth, 90 against 68
  • Payments & pricing, 15 against 0
  • Maintenance & community, 74 against 59

Watch for

No price list, free tier or trial. The pricing page gives only a starting figure of $8 per employee per month plus a base fee, and endpoints name a paid package such as API Tier 1

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Reliability Rippling +37

HiBob 40

Graded on the public REST API. HiBob's End Users Terms of Use (October 2024) bar anyone from systematically collecting data from the Site "by scraping or otherwise", where the Site is any website HiBob owns or operates, and the API Terms of Use (22 January 2026) bar scraping or crawling the HiBob Documents. HiBob hosts, status.hibob.io included, were therefore not read on 4 November 2026, and the 7 October readings are kept as not re-read. The provenance names a Statuspage site at status.hibob.io. The 7 October reading of its components and incidents came only from the page's /api/v2 path, which this benchmark doesn't use, so it is struck, and nothing is readable today (0 for the status page, 5 for the incident record, the no-readable-history score). Per-endpoint limits are published, such as 50 a minute on people search and 10 on employee updates, per the 7 October check (15). 429 carries Retry-After and X-RateLimit headers and the docs ask for backoff on 429 and 500, but no idempotency keys or safe-retry guidance for writes were found (10). No SLA found, and the subscription terms disclaim uninterrupted service (0). The API is generally available, while the OAuth MCP server is in gradual rollout (10). 0+5+15+10+0+10 = 40.

Rippling 77

Read with the hosted lines and scored on the REST Platform API v2, the surface an outside agent calls with a token. status.rippling.com on Atlassian Statuspage lists components among them Rippling App and Platform API, with incident history (20). Read on 3 November from history.atom and the incident pages (the 7 October reading came from the Statuspage /api/ feed, which robots.txt disallows, and is struck). 14 incidents from 5 August to 29 October, none tagging the Platform API component. One names the REST API, increased latency on 10 September from 11:21 to 14:20 EST, with timeouts in Functions and App Studio, read as partial since the API was slow, not down. 15 October's higher error rates across products (about two hours, component Rippling App) is titled partially degraded. The app outages on 29 September (about 32 minutes) and 18 September (intermittent) and the MCP outage on 17 September (34 minutes) tag other components. Minor incidents only (20). Limits with numbers, 600 requests per 10 seconds per token per endpoint path, 300 per path and IP with no token, page size 100, 64 filter nodes (15). The docs say to retry a rate-limited call with exponential backoff or Retry-After and give a retry column per status. Idempotency-Key appears on hires, draft transitions and time entries only (12 of 15). No SLA found, and the customer terms were unreadable (0). The v2 API carries no beta label (10). 20 + 20 + 15 + 12 + 0 + 10 = 77.

Agent ergonomics Rippling +28

HiBob 47

Per the 7 October check, not re-read on 4 November 2026 (HiBob's terms bar scraping its sites). The fields array sizes people responses, but people search returns every matching employee in one response (13). Cursor pagination with a limit up to 200 covers bulk tables, workforce planning and the job catalogue only, and people search filters accept only root.id and root.email with equals (10). Status codes and recovery advice are documented (no retry on 400, stop on 401 and 403), but fields without permission vanish from a 200 response with no warning (12). No idempotency keys. 304 signals an unchanged record, and the MCP tool annotations could not be read (6). Few required parameters on reads. No official SDK found in the reviewed documentation (6).

Rippling 75

Related objects come back null until asked for with expand, and limit sizes a page. No field selection (20 of 25). Cursor pagination through next_link, filter with nine operators, order_by (20). A status table with retry advice, __meta.redacted_fields naming hidden fields and x-rippling-request-id on responses, though the example error bodies are generic (14 of 20). Idempotency-Key on hires, draft transitions and time entries, and the SDK retries twice by default. No general idempotency rule for writes, and MCP annotations weren't visible (12 of 20). List calls need no parameters. One official SDK, JavaScript, still alpha (9 of 15).

Security & auth Rippling +22

HiBob 68

Per the 7 October check, not re-read on 4 November 2026 (HiBob's terms bar scraping its sites). Service users are separate, revocable credentials with no permissions by default and rights granted per feature, per field and per employee population. They travel as HTTP Basic. OAuth with 28 scopes, 5-minute access tokens and a customer-chosen audience exists for approved partners, and the MCP server uses OAuth as the signed-in employee (25). Field-level View and Edit make read-only service users possible. No confirmation step for terminate or delete calls was found (14). The API returns text written by employees, and no injection guidance was found. The MCP documentation was unreadable (2). Bob has an API audit log linked from the docs, whose article we could not open (10). SOC 2 Type II, ISO 27001:2022, ISO 27018:2019, third-party penetration tests and a Bugcrowd bounty. security.txt could not be checked (17).

Rippling 90

API tokens with 162 listed scopes, most split into read and read-write, limited to the owner's permission profile, shown once, revocable, and revoked after 30 days unused or when the owner leaves. OAuth 2.0 with scopes for partners. All in the Authorization header (30). Read-only scopes, admin-only token oversight, hires and worker changes created as drafts for review, leave requests through the normal approval flow, and MCP deletes that need confirmation (19 of 20). The MCP runs model-written code in a sandbox with no network egress and credentials kept outside it, and withholds SSNs, home addresses and tax IDs. No guidance on untrusted text in records (9 of 15). An activity log endpoint with 90 days of events, an email on token creation and MCP Gateway audit logs. A per-token call log wasn't found (14 of 15). SOC 1 and SOC 2 Type II, SOC 3, ISO 27001, 27018 and 42001, CSA STAR Level 2, and a vulnerability reporting programme with bounties. No security.txt (18 of 20).

Payments & pricing Rippling +15

HiBob 0

Per the 7 October check, not re-read on 4 November 2026 (HiBob's terms bar scraping its sites). No x402, MPP or L402 (0). Prices are by quote only (0). No free tier or trial found, and the sandbox is a purchased module (0). Credentials come from a customer's admin in the Bob interface, with no programmatic route (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 0 is 0.

Rippling 15

Read with the hosted rubric. No x402, MPP or L402 (0). The pricing page FAQ, read on 3 November, says plans start at $8 per employee per month with a monthly base fee and quotes everything else, which is read between contact sales and public plan pricing, as factorial (5). No free tier or trial found for customers. Approved App Shop partners use the API and a test company at no cost, which needs an application, so partial credit (5 of 20). A person creates each token in the Developer app or completes an OAuth install (0). 0 + 5 + 5 + 0 = 10. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 10 is 15.

Maintenance & community Rippling +15

HiBob 59

Per the 7 October check, not re-read on 4 November 2026 (HiBob's terms bar scraping its sites). The newest developer changelog entry on record is dated 7 October 2026, 28 days before this check (30). Ten entries between 21 July and 7 October were recorded, among them new Employee Tables endpoints on 17 August and the 7 October entry inside the 90 days from 6 August. The other dates weren't recorded and the changelog can't be read today, so the line is held on the October count (20). A dated changelog with RSS and a support desk. No public issue tracker or developer forum was found (9). No official SDKs found, and none on GitHub in a search on 4 November (0). No public packages or CI to assess (0). 30+20+9+0+0 = 59.

Rippling 74

The changelog's latest entry is 25 October 2026 (name and owner search on custom object records) (30). 36 changelog entries on 12 dates from 5 August to 25 October (20). Closed service with a dated changelog, a partner support address and a service desk for applications. No public issue tracker (10 of 15). One official SDK, alpha, current per the 7 October check (npm not re-read on 3 November), and no entry for Rippling's own MCP server in the official registry (9 of 15). The SDK has no runtime dependencies. Its repository is private, so CI isn't visible (5 of 10). 30 + 20 + 10 + 9 + 5 = 74.

Transparency & trust HiBob +15

HiBob 71

Per the 7 October check, not re-read on 4 November 2026 (HiBob's terms bar scraping its sites). Closed service with public API Terms of Use and customer subscription terms revised January 2026 (15). The subscription terms promise deletion of personal data within 30 days of termination and let HiBob use anonymised, aggregated customer data freely. The privacy policy excludes data processed for customers, and the DPA sits behind a DocuSign link we could not read (15). Past deprecations carried dates and four to seven months' notice (2023 and 2024), but the deprecations page was last updated in May 2025 and the API terms promise notice only where commercially reasonable (10). The sub-processor list (November 2025) names providers, purposes and locations, including OpenAI and Azure OpenAI for optional functions, and hosting is stated as AWS Ireland with Frankfurt for recovery (18).

Rippling 56

Closed service. Customer terms, user terms, AI Services Terms and Developer Terms of Use are published at stable URLs on app.rippling.com, which returned only a JavaScript application to our reader on 7 October (not re-read on 3 November). The SDK is Apache-2.0 (13 of 30). The privacy and compliance page says Rippling processes customer data only as instructed and links a privacy notice and a DPA, both unread for the same reason. The docs state 90 days of activity log retention and the fields the MCP withholds (12 of 30). Versions are dated and V1 is labelled an archive, but breaking changes are logged on the day with no notice period shown and no removal dates (8 of 20). The trust security page says all data is housed in US-based AWS data centres across several availability zones, and no sub-processor list was found, as medplum (5 of 20, was 0). 13 + 12 + 8 + 5 = 38.

Score by category

CategoryWeightHiBobRipplingEdge
Reliability16%4077Rippling +37
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7873HiBob +5
Agent ergonomics13%4775Rippling +28
Security & auth14%6890Rippling +22
Payments & pricing10%015Rippling +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%5974Rippling +15
Transparency & trust7%7156HiBob +15
Negative events≤150-3
TotalD 51.6/100B 65.5/100

Facts side by side

FactHiBobRippling
KindHTTP APIHTTP API
VendorHi Bob Ltd.People Center, Inc. dba Rippling
Hosted endpointhttps://api.hibob.com/v1https://rest.ripplingapis.com
TransportsHTTPHTTP
AuthOAuth or keyOAuth or key
PricingPaidPaid
x402nono
LicenceProprietary service under HiBob's customer subscription terms and API Terms of UseProprietary service under Rippling's customer terms and Developer Terms of Use. The JavaScript SDK on npm is Apache-2.0
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-072026-10-25
Terms last updatedno date givencouldn't be read
Privacy policy last updatedno date givencouldn't be read
Customer content may train modelsnot found in the textcouldn't be read
Terms restrict automated accessyescouldn't be read
Terms restrict benchmarkingnot found in the textcouldn't be read
Terms or service can change without noticeyescouldn't be read
Arbitration or class-action waivernot found in the textcouldn't be read
Popularitynone3.6k npm/wk
Agent reviewsnone2.8/5 (4)

How the scores have moved

Verdicts

HiBob

Service users start with no permissions and gain view or edit rights per field, and the docs are served as Markdown with an OpenAPI definition on each endpoint page. There is no public price, trial or free sandbox, so an agent needs a paying customer's admin to issue credentials. No idempotency keys or official SDKs were found.

Rippling

Scoped, revocable API tokens, read-only scopes, drafts for worker changes and a broad certification list suit an agent working on HR data. Pricing is quoted beyond a starting figure, there's no trial, the only SDK is alpha, and breaking changes land in the changelog the day they take effect.

Before you call either

HiBob

  1. Send Authorization: Basic base64(SERVICE-USER-ID:TOKEN) to https://api.hibob.com/v1. Ask the Bob admin to put the service user in a permission group first, because it starts with none
  2. Request only the fields needed in fields on POST /people/search (maximum 400). The call returns all matching employees at once, so batch by root.id in large companies
  3. Compare returned fields with requested ones. Missing permission or a wrong field ID yields 200 with the field omitted
  4. Stop on 401 or 403. More than 50 in 10 seconds blocks the IP for 5 minutes
  5. Back off on 429 using Retry-After. Writes such as update, create and terminate employee allow 10 calls a minute, and no idempotency key exists, so check state before retrying a write

Rippling

  1. Call https://rest.ripplingapis.com with a Bearer token and pin Rippling-Api-Version. Use V1 at api.rippling.com only for resources that exist nowhere else
  2. Treat a null field as possibly hidden. Check __meta.redacted_fields, the token's scopes and whether expand was sent
  3. Follow next_link until it is null. The default page is 50 records and a limit above 100 returns 400
  4. Stay under 600 requests per 10 seconds per endpoint path for each token, and on a 429 back off or wait for Retry-After while other paths keep working
  5. Send an Idempotency-Key on POST /hires/ and POST /draft-transitions/, then poll the request until it reaches a final status

Questions

Which is better for AI agents, HiBob or Rippling?

Rippling scores 65.5 (B) on agent readiness against HiBob's 51.6 (D), and leads in 5 of 7 scored categories. HiBob leads on schema & documentation and transparency & trust.

Do HiBob and Rippling need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call HiBob and Rippling without installing anything?

Yes. HiBob has a hosted endpoint at https://api.hibob.com/v1 and Rippling at https://rest.ripplingapis.com.

Other comparisons with HiBob or Rippling

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.