Head to head · Hr employees · October 2026 research run
Remote vs Rippling
Remote scores 70.7 (BB) on agent readiness against Rippling's 60.8 (C), and leads in 4 of 7 scored categories. Rippling leads on agent ergonomics and security & auth. Both do hr employees.
Which one, for what
Remote BB
Good for A company that employs people through Remote (EOR, payroll, contractors or its HRIS) and wants an agent to read employments, file and review time off, track onboarding, and read payslips and documents.
Ahead on
- Reliability, 96 against 62
- Schema & documentation, 78 against 73
- Payments & pricing, 35 against 5
- Transparency & trust, 68 against 51
Also in its favour
- Agent-ready, a grade of BB or better
- No incidents deducted, where Rippling loses 3 points for them
Watch for
The REST API changelog link in the docs redirects to a ReadMe dashboard login, so no public dated record of API changes was read
Rippling C
Good 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
- Agent ergonomics, 75 against 57
- Security & auth, 90 against 74
Watch for
No public price, free tier or trial. rippling.com/pricing is a quote form, and endpoints name a paid package such as API Tier 1
Score by category
| Category | Weight this run | Remote | Rippling | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 96 | 62 | Remote +34 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 78 | 73 | Remote +5 |
| Agent ergonomics | 13%16.2 | 57 | 75 | Rippling +18 |
| Security & auth | 14%17.5 | 74 | 90 | Rippling +16 |
| Payments & pricing | 10%12.5 | 35 | 5 | Remote +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 72 | 74 | Rippling +2 |
| Transparency & trust | 7%8.8 | 68 | 51 | Remote +17 |
| Negative events | ≤15 | 0 | -3 | |
| Total | 70.7 · BB | 60.8 · C |
Facts side by side
| Fact | Remote | Rippling |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Remote Technology, Inc. | People Center, Inc. dba Rippling |
| Hosted endpoint | https://gateway.remote.com | https://rest.ripplingapis.com |
| Transports | HTTP, Streamable HTTP | HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Paid | Paid |
| x402 | no | no |
| Licence | Proprietary service under Remote's terms of use. The remote-for-ai plugin and the Remote CLI repository on GitHub are MIT | Proprietary service under Rippling's customer terms and Developer Terms of Use. The JavaScript SDK on npm is Apache-2.0 |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| Last release | 2026-10-08 | 2026-10-07 |
| Terms last updated | 2026-08-03 | couldn't be read |
| Privacy policy last updated | 2026-08-03 | couldn't be read |
| Customer content may train models | not found in the text | couldn't be read |
| Terms restrict automated access | yes | couldn't be read |
| Terms restrict benchmarking | yes | couldn't be read |
| Terms or service can change without notice | not found in the text | couldn't be read |
| Arbitration or class-action waiver | yes | couldn't be read |
| Popularity | 1.8k npm/wk | 3.6k npm/wk |
Verdicts
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.
Rippling
API tokens carry any of 162 scopes and can never see more than their owner, and hires and worker changes land as drafts for a person to review. There is no public price, trial or self-serve signup, and status.rippling.com shows five incidents marked critical between 16 July and 29 September 2026.
Before you call either
Remote
- Match the token prefix to the host.
ra_test_works only on https://gateway.remote-sandbox.com andra_live_only on https://gateway.remote.com - Stay under 300 requests a minute per company for customer tokens, shared by every token, and read
x-ratelimit-remainingandx-ratelimit-reset(milliseconds) - Check for an existing record before retrying a create, or set
external_idon employments and treat a 422 for a duplicate as success - Fetch the country form schema (
GET /v1/countries/{country_code}/{form}) before writing employment data. Country codes are three-letter ISO - Use the REST API for unattended work. The MCP server needs a browser sign-in and its write tools cover employee self-service only
Rippling
- 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 - Treat a null field as possibly hidden. Check
__meta.redacted_fields, the token's scopes and whetherexpandwas sent - Follow
next_linkuntil it is null. The default page is 50 records and alimitabove 100 returns 400 - Stay under 300 requests per IP in any 10 seconds. Going over rejects every request for the next 10 seconds
- Send an
Idempotency-Keyon POST /hires/ and POST /draft-transitions/, then poll the request until it reaches a final status
Questions
Which is better for AI agents, Remote or Rippling?
Remote scores 70.7 (BB) on agent readiness against Rippling's 60.8 (C), and leads in 4 of 7 scored categories. Rippling leads on agent ergonomics and security & auth.
Do Remote and Rippling need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Remote and Rippling without installing anything?
Yes. Remote has a hosted endpoint at https://gateway.remote.com and Rippling at https://rest.ripplingapis.com.
Other comparisons with Remote or Rippling
Machine-readable
- This page as Markdown
/compare/remote-vs-rippling.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/remote.json·/api/v1/tools/rippling.json - From a terminal
anchor compare remote rippling(the CLI) - Over MCP
compare_tools {"a": "remote", "b": "rippling"}at/mcp, no key