# Ramp > Ramp is a finance platform with company cards, expense management, bill pay, procurement and travel. Its Developer API reads and writes transactions, receipts, funds, bills and purchase orders. A hosted MCP server and CLI work with the signed-in user's permissions. - Canonical: https://www.anchorterminal.com/tools/ramp - Markdown: https://www.anchorterminal.com/tools/ramp.md (~7,500 tokens) - Slim: https://www.anchorterminal.com/tools/ramp.min.md (~1,880 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/ramp.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 · 57.3/100 · rank #478 of 722 · #7 in Spend management & procurement · not agent-ready · confidence medium** ## Assessment 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. ## Facts | Field | Value | | --- | --- | | Vendor | Ramp Business Corporation (https://ramp.com) | | Kind | HTTP API | | Category | Spend management & procurement (https://www.anchorterminal.com/categories/spend-management) | | Transport | HTTP | | Endpoint | `https://api.ramp.com` | | Auth | OAuth · Access is self-serve for a Ramp customer. An admin creates an app at Company > Developer, accepts the terms, and picks grant types and scopes. Client credentials tokens are requested from `/developer/v1/token` with HTTP Basic auth, last 10 days and act with the app creator's permissions. The authorisation code grant is for apps acting for other businesses, with one-hour access tokens by default, optional refresh tokens, and consent limited to Admin and Business Owner users. Scopes follow `resource:read` and `resource:write`, and `cards:read_vault` needs a production review by Ramp. The MCP server and CLI use OAuth and work with the signed-in user's permissions, and custom MCP clients need their redirect URI allowlisted by Ramp. | | Pricing | Freemium ($15 / seat-mo) · No separate API fee is published. ramp.com/pricing lists Free at $0 per user per month, Plus at $15 per user per month plus a platform fee by team size, and Enterprise on request, with a 30-day Plus trial. The OpenAPI spec marks 51 of 260 operations as needing Plus. Access needs an approved Ramp business account, so an agent can't start without one. A sandbox at demo-api.ramp.com is available on request through a form. The API Agreement reserves the right to charge API fees (checked 2026-10-08). | | x402 | No · Ramp's own API isn't paid for by x402, MPP or L402. Ramp lets a connected agent pay other sellers by x402 from a funded wallet, or by Stripe MPP, per the agentic payments guide (https://docs.ramp.com/llms-guides/agent-payments.txt, checked 2026-10-08). | | Licence | Proprietary service under the Ramp Platform Agreement and the API Agreement. The ramp-cli repository is MIT | | Source | https://github.com/ramp-public/ramp-cli | | Docs | https://docs.ramp.com | | llms.txt | https://docs.ramp.com/llms.txt | | Last release | 2026-10-07 | | GitHub stars | 53 (as of 2026-10-08) | | API | Developer API v1 at https://api.ramp.com (sandbox https://demo-api.ramp.com), one OpenAPI 3.0.2 spec, 260 operations, 89 marked beta and 51 marked as needing the Plus plan | | MCP servers | Ramp MCP at https://mcp.ramp.com/mcp (demo data at https://demo-mcp.ramp.com/mcp), OAuth with PKCE under the signed-in user's permissions, described as subject to change. Developer MCP at https://mcp.ramp.com/developer/mcp, no sign-in, docs only. The tool count isn't published. The CLI's bundled spec marks 120 operations for MCP | | CLI | ramp-cli, MIT, v0.2.54 on 6 October 2026, Python 3.11 or later, installed by script or Homebrew. JSON output in agent mode, a dry-run flag, sandbox by default | | Credentials | OAuth 2.0. Client credentials tokens last 10 days with no refresh. Authorisation code tokens default to 1 hour with optional refresh. Revoke at POST /developer/v1/token/revoke | | Scopes | About 80 in the spec in `resource:read` and `resource:write` form, such as transactions:read, receipts:write, funds:write, bills:write and purchase_orders:write. `cards:read_vault` needs a production review | | Rate limits | 200 requests per rolling 10 seconds per source IP. 60-second request timeout (504). Higher limits by support ticket | | Pagination | Keyset, with the next page as a full URL in `next`. `page_size` default 20, maximum 100 | | Errors | `error_v2` with `error_code`, `message`, `additional_info` and `error_id`, and an `x-trace-id` header on every response | | Idempotency | `X-Idempotency-Key` on 8 of 155 write operations (funds, procurement requests, vault cards, accounting syncs, agreement documents) | | Webhooks | HMAC-SHA256 signature in `X-Ramp-Signature`, up to 10 delivery attempts on 429 and 5xx with a constant event ID, 10-second timeout | | Sandbox | demo.ramp.com and demo-api.ramp.com, on request. No real money moves, and demo actions create transactions and mark bills paid | | Audit | GET /developer/v1/audit-logs/events with filters by user, date, event type and actor type (Plus plan) | | Certifications | SOC 1 Type 2, SOC 2 Type 2, ISO 27001:2022, ISO/IEC 42001:2023 and PCI DSS per trust.ramp.com, with reports behind an access request and NDA | | Agent payments | Agent Cards, Stripe MPP and x402 from a separately funded wallet, for an agent paying other sellers on the connected user's behalf | | Capabilities | spend.transactions, spend.expenses, spend.cards, spend.bills, spend.procurement | | Tags | hosted, freemium, oauth, mcp, cli, openapi, llms-txt, webhooks, sandbox, soc2, pci-dss, security-txt | | JSON | https://www.anchorterminal.com/api/v1/tools/ramp.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 | 30 | 6.0 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 86 | 14.0 | | Agent ergonomics | 13% | 16.2 | 66 | 10.7 | | Security & auth | 14% | 17.5 | 79 | 13.8 | | Payments & pricing | 10% | 12.5 | 25 | 3.1 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 74 | 6.5 | | Transparency & trust (editorial 55, provenance 84) | 7% | 8.8 | 70 | 6.1 | | Negative events | up to −15 | up to −15 | 2026-06-25 and 2026-02-11. The changelog records the webhook event type `transactions.all_requirements_met_and_approved` removed on 25 June 2026, three days after the 22 June entry marked it a deprecated alias, and `functional_currency_amount` dropped from default transaction responses on 11 February 2026. Both are documented on the day they shipped and the first names a replacement. Notice by email couldn't be checked, so the smallest deduction applies (https://docs.ramp.com/developer-api/v1/changelog). | -3 | | **Total** | | | | **57.3 → C** | ### Why each score - Reliability 30: Read with the hosted lines and scored on the Developer API, the surface an outside agent calls with a token. No public status page was found. status.ramp.com doesn't resolve, and no status link appears in the docs export, the help centre article, the trust centre or the home and pricing pages we read (0). With no page there is no incident record to read (0). The limit is published, 200 requests per rolling 10 seconds per source IP, with a 60-second request timeout (15). The docs ask for exponential backoff of 1, 2 and 4 seconds on 429 and on 504. `X-Idempotency-Key` is accepted on 8 of 155 write operations (funds, procurement requests, vault cards, accounting syncs), and a Retry-After header isn't documented (9 of 15). No SLA was found in the Platform Agreement or the API Agreement (0). The API is v1, but 89 of 260 operations carry `x-beta` and the MCP guide says the server is subject to change (6 of 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 86: A public OpenAPI 3.0.2 spec with 260 operations at docs.ramp.com/openapi/developer-api.json (25). llms.txt, a plain-text file per guide, llms-api.txt and llms-full.txt (10). Every operation has a summary or description, and the 133 agent-tool operations in the CLI's bundled spec open with when to use the tool. Developer API descriptions are shorter, and few say when not to call an endpoint (14 of 20). 638 enums, many with `x-enum-descriptions`, UUID and date-time formats, and `x-relationship` links between resources. Error `additional_info` is a free-form object (13 of 15). 264 examples. 400 is documented on 75 operations, 404 on 17, 401 on 3 and 429 on none, and the error guide lists eight status codes without a catalogue of `error_code` values (9 of 15). The path is versioned v1, and the changelog is dated to the day with an RSS feed (15). - Agent ergonomics 66: `page_size` sizes a page (default 20, maximum 100) and `functional_currency_amount` is opt-in on transactions. No field selection or expand parameter was found in the spec (18 of 25). Keyset pagination returns the next page as a full URL in `next`, and 50 list operations take `page_size`, with filters by department, card, merchant, state and date on transactions. The docs say bills and transactions have no updated-at filter (16 of 20). Errors arrive as `error_v2` with `error_code`, `message`, `additional_info` and `error_id`, and every response carries `x-trace-id`. There is no published list of codes, and the docs say unknown fields are ignored on some endpoints and rejected on others (14 of 20). `X-Idempotency-Key` on 8 of 155 write operations, and asynchronous user creation returns a task ID to poll. The spec marks 14 operations with `x-read-only` and 3 with `x-destructive`. The MCP server's own annotations couldn't be read without an account (10 of 20). List calls need no required parameters. No official SDK was found in the docs. The MIT ramp-cli prints JSON in agent mode and has a dry-run flag (8 of 15). - Security & auth 79: OAuth 2.0 with client credentials or the authorisation code grant, about 80 scopes in the spec in `resource:read` and `resource:write` form, tokens bound to scopes at issue and sent in the `Authorization` header, a revoke endpoint, and PKCE (S256) on the MCP server (30). Read scopes are separate from write scopes, card numbers need `cards:read_vault` and a production review by Ramp, and MCP and CLI users act with their own Ramp permissions. Admins on Plus choose who may connect. A client credentials token acts with the app creator's permissions, MCP tools can approve transactions and reimbursements for an approver, and no confirmation step was found for API writes (15 of 20). Memos, comments, merchant names and receipts are untrusted text, and no prompt-injection guidance was found (3 of 15). `GET /developer/v1/audit-logs/events` filters by user, date, event type and actor type (Plus plan), responses carry a trace ID, and MCP calls are attributed to the signed-in user (13 of 15). A valid security.txt expiring 18 March 2027, SOC 1 and SOC 2 Type 2 reports, ISO 27001:2022, ISO 42001, PCI DSS and a responsible disclosure entry on the trust centre. No bounty is stated (18 of 20). - Payments & pricing 25: Read with the hosted rubric. Ramp's API isn't paid for by x402, MPP or L402. Ramp does let an agent pay other sellers by x402 from a funded wallet or by Stripe MPP, which is a product capability and not a way to buy access (0). Plan prices are public, Free at $0 per user per month and Plus at $15 per user per month plus a platform fee by team size that isn't stated, with Enterprise on request. The API has no per-call price (10). The Free plan needs no payment card, but it needs an approved Ramp business account, and sandbox access is by request form, so partial credit (15 of 20). The Developer MCP server answers docs questions with no account. Account data needs an admin to create an app in the dashboard or a person to complete an OAuth 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 74: The changelog's latest entry is 7 October 2026, and ramp-cli v0.2.54 was tagged on 6 October (30). 26 dated changelog entries between 15 July and 7 October 2026, and 48 CLI tags since 10 July (20). Closed service with a daily-dated changelog and RSS feed. Support is a ticket raised from the developer console and answered by email, and the CLI's public repository shows 7 open issues and pull requests. Response times couldn't be observed (10 of 15). No official SDK was found, and Ramp's MCP server isn't in the official MCP registry, where the only Ramp entry is a third party's (com.mcparmory/ramp). The official CLI is current (6 of 15). The CLI repository runs lint, pytest and a smoke test in CI and pins dependencies in uv.lock. It installs from a script or Homebrew, not PyPI (8 of 10). - Transparency & trust 70: Closed service with terms at stable URLs, the Platform Agreement (updated 22 September 2026) and the API Agreement (26 March 2026). The CLI is MIT (16 of 30). The privacy policy (21 August 2026) describes retention by criteria without fixed periods and says Ramp will give notice and obtain permission before training a general-purpose model on company content. The DPA (10 July 2026) deletes personal data on written request after termination, with back-ups kept to Ramp's own schedule (20 of 30). The changelog labels deprecated fields, but the API Agreement says Ramp may change or discontinue the APIs with or without notice, and no notice period is published (6 of 20). The trust centre lists sub-processors and key service providers and posts additions with name, location and purpose, such as Modal in the United States. The full documents sit behind an access request and NDA (13 of 20). Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (21 items): https://www.anchorterminal.com/fixes/ramp.md (JSON https://www.anchorterminal.com/fixes/ramp.json) ### What we couldn't check - unchecked: whether Ramp publishes a status page at an address other than status.ramp.com, which doesn't resolve. None was linked from the pages we read - unchecked: the live Ramp MCP server's tool list, input schemas and readOnlyHint and destructiveHint annotations, which need a signed-in Ramp account. The count of 120 comes from the CLI's bundled spec - unchecked: whether 429 responses carry a Retry-After header - unchecked: whether customers were told by email before the 25 June 2026 webhook event removal and the 11 February 2026 response change - unchecked: the full sub-processor list and the security reports on trust.ramp.com, which need an access request and NDA - unchecked: whether an SLA exists in Enterprise order forms. None was found in the Platform Agreement or the API Agreement - unchecked: whether the Free plan includes Developer API access. The spec marks 209 operations as not needing Plus, and the pricing page doesn't list the API under any plan - The Claude Code and JSON config lines in the MCP guide are stripped from the plain-text export, so `connect` holds only the install script and the documented first request - The x402 guide linked from the cards guide wasn't read. Ramp's x402 support is for paying sellers from a funded wallet, not for paying for Ramp's API - The trust centre's phishing advisory against Ramp customers is undated in the text we read and concerns a third party's campaign, so no deduction was made ### Sources - docs index for agents: (seen 2026-10-08) - OpenAPI spec, 260 operations: (seen 2026-10-08) - authorisation guide, scopes and token lifetimes: (seen 2026-10-08) - rate limits and timeouts: (seen 2026-10-08) - error guide: (seen 2026-10-08) - pagination guide: (seen 2026-10-08) - sandbox guide: (seen 2026-10-08) - changelog: (seen 2026-10-08) - Ramp MCP guide: (seen 2026-10-08) - Developer MCP guide: (seen 2026-10-08) - agentic payments guide: (seen 2026-10-08) - webhooks guide: (seen 2026-10-08) - Ramp MCP help centre article: (seen 2026-10-08) - MCP authorisation server metadata: (seen 2026-10-08) - ramp-cli source, tags, CI and bundled agent-tool spec: (seen 2026-10-08) - pricing: (seen 2026-10-08) - security page: (seen 2026-10-08) - trust centre: (seen 2026-10-08) - security.txt: (seen 2026-10-08) - API Agreement: (seen 2026-10-08) - Platform Agreement: (seen 2026-10-08) - privacy policy: (seen 2026-10-08) - official MCP registry search: (seen 2026-10-08) - RDAP for ramp.com: (seen 2026-10-08) ## Who's behind it (provenance 84/100, checked 2026-10-08) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Ramp Business Corporation | 20/20 | | Domain age | ramp.com, registered 1994-03-14 (32 years) | 15/15 | | Endpoint on the vendor's domain | api.ramp.com | 15/15 | | Terms of service | published, but our reader couldn't read it | 7/10 | | Privacy policy | published, but our reader couldn't read it | 7/10 | | Status page | not found | 0/10 | | Changelog | published | 10/10 | | security.txt | valid | 10/10 | The API Agreement (last updated 26 March 2026) names Ramp Business Corporation, 28 West 23rd Street, Floor 2, New York, NY 10010. The API answers at api.ramp.com and demo-api.ramp.com, and the MCP servers at mcp.ramp.com and demo-mcp.ramp.com. No status page was found. status.ramp.com doesn't resolve, and no status link appears in the docs, help centre, trust centre, home or pricing pages read on 8 October 2026. ramp.com/.well-known/security.txt gives security-external@ramp.com as the contact and expires on 18 March 2027. The Platform Agreement was last updated on 22 September 2026, the privacy policy on 21 August 2026 and the DPA on 10 July 2026. The legal pages render with JavaScript, and we read the published documents from the site's own script files. RDAP for ramp.com gives a registration date of 1994-03-14 and Cloudflare, Inc. as registrar. ### 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://ramp.com/legal/developer-terms/developer-terms/api-agreement), read 2026-10-08. Our reader couldn't read it (the page has 0 words of text without a browser, so the document is drawn by script or sits elsewhere). **Privacy policy** (https://ramp.com/legal/privacy-policy), read 2026-10-08. Our reader couldn't read it (the page has 0 words of text without a browser, so the document is drawn by script or sits elsewhere). ## Live (updated 2026-10-08 19:52 UTC) - Right now: up, HTTP 401, 129 ms, checked 2026-10-08 19:52 UTC (get on `https://api.ramp.com`, asks for auth) - Uptime 24h 100.0% (50 probes) · 30 days 100.0% (50 probes) · p50 139 ms · p95 194 ms - github `ramp-public/ramp-cli` v0.2.54, released 2026-10-06 - security.txt: valid, expires 2027-03-18T19:00:00.000Z - Watching changelog - Watching privacy - Watching terms - Always current: https://www.anchorterminal.com/api/v1/live/ramp.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. ## Prices | Item | Price | Unit | Note | | --- | --- | --- | --- | | Free plan | free | per seat per month | No separate API fee is published | | Plus plan | $15 | per seat per month | Plus a platform fee by team size, not stated. Enterprise is priced on request | Across all listings: https://www.anchorterminal.com/prices/index.md ## Strengths - Public OpenAPI 3.0.2 spec with 260 operations, plus llms.txt and a plain-text export of every guide and the API reference - OAuth 2.0 scopes follow `resource:read` and `resource:write`, tokens are bound to scopes at issue, and `POST /developer/v1/token/revoke` invalidates them - `GET /developer/v1/audit-logs/events` filters events by user, date, event type and actor type, including Ramp's own agents - A sandbox at demo-api.ramp.com and demo.ramp.com moves no real money and has demo actions that create test transactions - The changelog is dated to the day, with 26 dated entries between 15 July and 7 October 2026 and an RSS feed ## Weaknesses - 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 - 89 of 260 operations carry `x-beta`, among them creating a fund and splitting a transaction, and the MCP guide says the server is subject to change - `X-Idempotency-Key` is accepted on 8 of 155 write operations. Creating a bill, a purchase order or a vendor has none - The API Agreement says Ramp may change or discontinue the APIs at any time with or without notice - No official SDK was found in the docs, and 51 operations (custom records, purchase orders, the audit log) need the paid Plus plan ## Before you call it (notes for agents) 1. Send `scope` on the client credentials token request. Without it Ramp issues a token with no scopes and every resource call fails with 403 2. Follow the full URL in `next` to page. `page_size` defaults to 20 and stops at 100, and the cursor is opaque 3. 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 4. Don't use `synced_after` or `from_created_at` to find changed records. Bills and transactions have no updated-at filter, so subscribe to webhooks 5. Send `X-Idempotency-Key` when creating funds or procurement requests. Elsewhere a retried POST can create a duplicate, so read back before retrying ## Connect Install: ```bash curl -fsSL https://agents.ramp.com/install.sh | sh ``` First request: ```bash curl https://api.ramp.com/developer/v1/transactions \ -H "Authorization: Bearer $RAMP_ACCESS_TOKEN" ``` Through letme (picks today, calling later): https://letme.dev/ramp. 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 | | --- | --- | --- | --- | --- | --- | --- | | Airwallex Spend and Issuing | B | 68.3 | 187 | spend.transactions, spend.cards, spend.expenses, spend.bills, spend.procurement | no | https://www.anchorterminal.com/tools/airwallex.md | | Spendesk API + MCP | B | 62.3 | 342 | spend.transactions, spend.expenses, spend.cards, spend.bills, spend.procurement | no | https://www.anchorterminal.com/tools/spendesk.md | | BILL | C | 60.9 | 380 | spend.transactions, spend.expenses, spend.cards, spend.bills | no | https://www.anchorterminal.com/tools/bill.md | | Brex | C | 60.7 | 391 | spend.transactions, spend.expenses, spend.cards, spend.bills | no | https://www.anchorterminal.com/tools/brex.md | | Mercury API | B | 63.8 | 293 | spend.transactions, spend.cards, spend.expenses | no | https://www.anchorterminal.com/tools/mercury.md | | Pleo API + MCP | B | 62.9 | 325 | spend.transactions, spend.expenses, spend.bills | no | https://www.anchorterminal.com/tools/pleo.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 - The Developer API is one OpenAPI 3.0.2 spec with 260 operations across transactions, receipts, memos, funds, cards, bills, vendors, purchase orders, reimbursements, accounting and webhooks (source: ) - Ramp runs three MCP servers. Ramp MCP at https://mcp.ramp.com/mcp works on account data with the signed-in user's permissions, Developer MCP at https://mcp.ramp.com/developer/mcp serves docs with no account, and Ramp Data MCP serves benchmark datasets (source: ) - The MIT ramp-cli bundles a spec of 133 agent-tool operations, 120 of them marked for MCP, and reached v0.2.54 on 6 October 2026 (source: ) - Rate limit of 200 requests per rolling 10 seconds per source IP, and requests over 60 seconds return 504 (source: ) - `X-Idempotency-Key` is accepted on 8 of 155 write operations, among them creating a fund and creating a procurement request (source: ) - Bill approvals and receipt uploads aren't available through Ramp MCP. The Developer API has a receipt upload endpoint (source: ) - An agent connected to Ramp can buy from sellers with Agent Cards, Stripe MPP or x402 from a separately funded wallet (source: ) - The API Agreement, last updated 26 March 2026, says Ramp may change or discontinue the APIs at any time with or without notice (source: ) ## Compare - [Airwallex Spend and Issuing vs Ramp](https://www.anchorterminal.com/compare/airwallex-vs-ramp.md): B 68.3 vs C 57.3 - [BILL vs Ramp](https://www.anchorterminal.com/compare/bill-vs-ramp.md): C 60.9 vs C 57.3 - [Brex vs Ramp](https://www.anchorterminal.com/compare/brex-vs-ramp.md): C 60.7 vs C 57.3 - [Expensify vs Ramp](https://www.anchorterminal.com/compare/expensify-vs-ramp.md): E 41.1 vs C 57.3 - [Mercury API vs Ramp](https://www.anchorterminal.com/compare/mercury-vs-ramp.md): B 63.8 vs C 57.3 - [Pleo API + MCP vs Ramp](https://www.anchorterminal.com/compare/pleo-vs-ramp.md): B 62.9 vs C 57.3 - [Ramp vs Spendesk API + MCP](https://www.anchorterminal.com/compare/ramp-vs-spendesk.md): C 57.3 vs B 62.3 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on ramp.com or one of its subdomains, or the README of github.com/ramp-public/ramp-cli. 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": "ramp", "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 Ramp on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Ramp on Anchor Terminal](https://www.anchorterminal.com/badges/ramp.svg)](https://www.anchorterminal.com/tools/ramp) ``` Plain link: ```html Ramp on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Ramp 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/ramp-dark.png - Light: https://www.anchorterminal.com/assets/share/ramp-light.png