Head to head · Spend transactions · October 2026 research run
BILL vs Ramp
BILL scores 60.9 (C) on agent readiness against Ramp's 57.3 (C), and leads in 1 of 7 scored categories. Ramp leads on agent ergonomics, security & auth and maintenance & community. Both do spend transactions.
Which one, for what
BILL C
Good for A US company already on BILL that wants an agent to create and read bills, run approvals, schedule vendor payments, raise invoices and manage budgets, vendor cards, card transactions and reimbursements.
Ahead on
- Reliability, 81 against 30
Also in its favour
- No incidents deducted, where Ramp loses 3 points for them
Watch for
POST /v3/login takes a user's username and password with a developer key, and the session carries that user's role with no scopes
Ramp C
Good for A finance team already on Ramp that wants an agent to read transactions, upload receipts, code and split expenses, issue funds with limits, create bills and work with purchase orders and procurement requests.
Ahead on
- Agent ergonomics, 66 against 60
- Security & auth, 79 against 56
- Maintenance & community, 74 against 32
Watch for
No public status page was found. status.ramp.com doesn't resolve, and no status link appears in the docs, help centre or trust centre pages read
Score by category
| Category | Weight this run | BILL | Ramp | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 81 | 30 | BILL +51 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 83 | 86 | Ramp +3 |
| Agent ergonomics | 13%16.2 | 60 | 66 | Ramp +6 |
| Security & auth | 14%17.5 | 56 | 79 | Ramp +23 |
| Payments & pricing | 10%12.5 | 25 | 25 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 32 | 74 | Ramp +42 |
| Transparency & trust | 7%8.8 | 66 | 70 | Ramp +4 |
| Negative events | ≤15 | 0 | -3 | |
| Total | 60.9 · C | 57.3 · C |
Facts side by side
| Fact | BILL | Ramp |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | BILL Holdings, Inc. | Ramp Business Corporation |
| Hosted endpoint | https://gateway.prod.bill.com/connect | https://api.ramp.com |
| Transports | HTTP | HTTP |
| Auth | OAuth or key | OAuth |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Proprietary service under the BILL Developer Terms and the BILL General Terms of Service | Proprietary service under the Ramp Platform Agreement and the API Agreement. The ramp-cli repository is MIT |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-05-21 | 2026-10-07 |
| Terms last updated | 2026-03-03 | couldn't be read |
| Privacy policy last updated | 2026-01-30 | couldn't be read |
| Customer content may train models | not found in the text | couldn't be read |
| Terms restrict automated access | not found in the text | couldn't be read |
| Terms restrict benchmarking | not found in the text | 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 | not found in the text | couldn't be read |
| Popularity | none | 53 stars |
Verdicts
BILL
A public OpenAPI 3.0.1 spec covers 326 operations, a self-serve sandbox moves no money, and payments need a session trusted by multi-factor authentication. The AP and AR API signs in with a user's password and has no scopes, no idempotency key protects payment calls, and no official SDK was found.
Ramp
OAuth 2.0 scopes split read from write across about 40 resources, a 260-operation OpenAPI spec is public, and an audit log endpoint records actions by user and agent. No public status page was found, 89 operations are marked beta, the API Agreement allows changes without notice, and idempotency keys cover only eight write operations.
Before you call either
BILL
- Sign in with
POST /v3/loginand sendsessionIdanddevKeyas headers on every AP and AR call. The session expires after 35 minutes idle - Send the
apiTokenheader alone on/v3/spend/paths. Spend & Expense calls need no login and are limited to 60 a minute per token - Complete the MFA challenge before
POST /v3/payments. An untrusted session fails withBDC_1361 - Read back payments before retrying a failed
POST /v3/payments. No idempotency key is accepted, so a blind retry can pay twice - Keep to three concurrent requests per developer key per organisation and 20,000 an hour. After
BDC_1144, wait for the next hour
Ramp
- Send
scopeon the client credentials token request. Without it Ramp issues a token with no scopes and every resource call fails with 403 - Follow the full URL in
nextto page.page_sizedefaults to 20 and stops at 100, and the cursor is opaque - Stay under 200 requests in any 10 seconds per source IP and back off 1, 2 then 4 seconds on 429. No Retry-After header is documented
- Don't use
synced_afterorfrom_created_atto find changed records. Bills and transactions have no updated-at filter, so subscribe to webhooks - Send
X-Idempotency-Keywhen creating funds or procurement requests. Elsewhere a retried POST can create a duplicate, so read back before retrying
Questions
Which is better for AI agents, BILL or Ramp?
BILL scores 60.9 (C) on agent readiness against Ramp's 57.3 (C), and leads in 1 of 7 scored categories. Ramp leads on agent ergonomics, security & auth and maintenance & community.
Do BILL and Ramp need an API key?
BILL takes an API key or an OAuth sign-in. Ramp uses an OAuth sign-in.
Can an agent call BILL and Ramp without installing anything?
Yes. BILL has a hosted endpoint at https://gateway.prod.bill.com/connect and Ramp at https://api.ramp.com.
Other comparisons with BILL or Ramp
Machine-readable
- This page as Markdown
/compare/bill-vs-ramp.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/bill.json·/api/v1/tools/ramp.json - From a terminal
anchor compare bill ramp(the CLI) - Over MCP
compare_tools {"a": "bill", "b": "ramp"}at/mcp, no key