Best of · Domain data
Best spend management and procurement platforms for AI agents
All 9 ranked spend management and procurement platforms on the Anchor benchmark, with a pick for each need and where each one falls short. Scores come from public evidence, re-checked as vendors change.
- 9 ranked
- 0 agent-ready
- 9 hosted endpoints
- Updated 8 October 2026
Top three
Picks by need
Worked out from the scores, prices and facts, so they change when the research does.
Schema & documentation
87/100 on schema & documentation, against 69 for the overall leader.
Maintenance & community
Ramp C
74/100 on maintenance & community, against 66 for the overall leader.
Transparency & trust
80/100 on transparency & trust, against 78 for the overall leader.
The shortlist
| # | Tool | Grade | Best for | Price | Where |
|---|---|---|---|---|---|
| 1 | Airwallex Spend and Issuing Airwallex |
B 68.3 | A company already banking with Airwallex in several currencies that wants an agent to issue cards with limits, read card transactions and expenses, load vendors, purchase orders and bills, and sync status to an ERP. | $12 / seat-mo | hosted |
| 2 | Mercury API Mercury Technologies, Inc. |
B 63.8 | A company that banks with Mercury and wants an agent to read balances and transactions, set notes and categories, upload receipts, issue virtual cards with spend limits and queue payments for human approval. | $35 / mo | hosted |
| 3 | Pleo API + MCP Pleo Technologies A/S |
B 62.9 | An agent that completes, codes, reviews and queues expenses for a Pleo customer on the Optimise plan, or for a bookkeeping integration that exports accounting entries and syncs tags, tax codes, accounts and vendors. | Paid | hosted |
| 4 | Spendesk API + MCP Spendesk SAS |
B 62.3 | A finance team already on Spendesk that wants an assistant to analyse spend, follow invoices and prepare the accounting close, or an ERP sync reading payables and settlements. | Paid | hosted |
| 5 | BILL BILL Holdings, Inc. |
C 60.9 | 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. | $49 / seat-mo | hosted |
| 6 | Brex Brex LLC |
C 60.7 | A finance team already on Brex that wants an agent to read expenses and transactions, issue and lock cards, set spend limits, upload receipts and pay vendors. | $12 / seat-mo | hosted |
| 7 | Ramp Ramp Business Corporation |
C 57.3 | 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. | $15 / seat-mo | hosted |
| 8 | Payhawk API + MCP Payhawk Limited |
C 57.1 | A finance team already on Payhawk that wants an ERP or accounting sync, master data kept in step, purchase orders raised from another system, or an assistant that answers spend questions and prepares approvals. | Paid | hosted |
| 9 | Expensify Expensify, Inc. |
E 41.1 | A finance team already on Expensify that wants an agent to export approved reports to an accounting system, create expenses and reports, keep categories, tags and employees in step with an HR system, or mark reports reimbursed. | $5 / seat-mo | hosted |
How to choose
- Scopes for card and expense accessCheck which scopes separate reading transactions from creating spending limits and issuing cards, since an agent should hold only the access its task needs.
- Approval points before money movesCheck where a person must approve a spend, a limit change or a purchase request, and whether an agent can route a request into that approval without bypassing it.
- Audit record for agent actionsCheck that each expense code, receipt and limit change lands in the audit record with the agent's identity, so finance can trace what it changed.
- Receipt attachment and duplicatesCheck whether a receipt can be attached to an existing transaction through the API and whether re-sending the same upload creates a duplicate.
How the benchmark tests this category. One test company with a fixed set of card transactions in each listing's sandbox. The same tasks run through its API (list transactions, attach a receipt, code an expense, create a spending limit, read a bill). We check scopes, approval points and the audit record. In this run listings are graded from public evidence against the published checklist.
Each one in detail
Airwallex Spend and Issuing
B 68.3/100Airwallex is a multi-currency business account with company cards, expense management and bill pay. Its REST API issues and controls cards, reads card transactions and expenses, and creates vendors, purchase orders and bills. A CLI and MCP server use OAuth.
Verdict Scoped API keys split read from write per resource, tokens last 30 minutes, and the sandbox opens at once with no contract. No OpenAPI spec was found, every Spend endpoint read is marked beta, the pricing page lists direct Spend API integration under the custom-priced Accelerate plan, and no SLA was found.
Choose it for A company already banking with Airwallex in several currencies that wants an agent to issue cards with limits, read card transactions and expenses, load vendors, purchase orders and bills, and sync status to an ERP.
Strengths
- Scoped API keys grant Read or Write per resource, can be limited to listed IP ranges, and exchange for bearer tokens that last 30 minutes
- A sandbox account opens at once from a signup form, with the full API except Connected Accounts and simulation endpoints for card transactions
- Rate limits are published with numbers, 100 requests a second per account and 20 per endpoint in production, with backoff guidance for 429
Weaknesses
- No OpenAPI spec was found. The reference is a Markdown page per endpoint, and the CLI prints one endpoint's schema at a time
- Each Spend endpoint we read (expenses, vendors, bills, purchase orders) is marked beta, and the pricing page lists direct Spend API integration under the custom-priced Accelerate plan
- The Spend API reads expenses and sets sync status. No endpoint was found to attach a receipt, code a card expense or approve one
Price $12 / seat-moAuth OAuth or keyx402 nohosted
Mercury API
B 63.8/100Mercury is a US business banking service with accounts, debit and credit cards, payments and invoicing. Its REST API reads transactions, issues virtual cards with spend limits and sends payments, and a hosted MCP server is in beta.
Verdict Custom tokens take per-endpoint scopes, write tokens need an IP allowlist, and payments can be queued for approval in the dashboard through POST /account/{accountId}/request-send-money. No rate limits, error catalogue or SLA were found in the reviewed documentation, the changelog carries no dates, and the MCP server is beta.
Choose it for A company that banks with Mercury and wants an agent to read balances and transactions, set notes and categories, upload receipts, issue virtual cards with spend limits and queue payments for human approval.
Strengths
- Three token tiers (read-only, read and write, custom scopes), with an IP allowlist required for write scopes and unused permissions removed after 45 days
POST /account/{accountId}/request-send-moneyalways queues a payment for approval in the dashboard, and MCP payment tools can only create such requestsidempotencyKeyis required on send-money calls, and a repeat returns 409 with the original transaction
Weaknesses
- No rate limits with numbers and no 429 handling were found in the reviewed documentation
- Reference pages document only 400 and 404 errors with one-line descriptions, and no error body schema or code list was found
- The changelog lists ten entries with no dates, and no deprecation policy was found
Price $35 / moAuth OAuth or keyx402 nohosted
Pleo API + MCP
B 62.9/100Spend management platform from Pleo Technologies A/S in Copenhagen, covering company cards, expenses, reimbursements, invoices and accounting exports. Outside agents reach it through a hosted MCP server for expense work and a REST API built for accounting integrations.
Verdict The hosted MCP server acts with the connecting user's own Pleo permissions, is off until an admin enables it per entity, and can't move money, change cards or alter limits. It is listed only on the Optimise plan, its tool definitions aren't published, API keys need enabling by Pleo support, and no official SDK or SLA was found.
Choose it for An agent that completes, codes, reviews and queues expenses for a Pleo customer on the Optimise plan, or for a bookkeeping integration that exports accounting entries and syncs tags, tax codes, accounts and vendors.
Strengths
- MCP server at mcp.pleo.io/mcp uses OAuth with PKCE and dynamic client registration, and acts with the connecting user's Pleo permissions
- Payments, card changes and spending-limit changes are blocked through the MCP by design, per the AI Access Terms
- Eleven current OpenAPI 3.0.1 specs with 162 operations, plus llms.txt, llms-full.txt and a Markdown copy of every docs page
Weaknesses
- The pricing page lists MCP on the Optimise plan only (£18 per user per month, three users minimum, sold through a demo)
- MCP tool names, schemas and count aren't published, so they can't be read without a customer sign-in
- Standalone API keys aren't self-service. Pleo support or a Customer Success Manager enables them, and partner OAuth clients go through a reviewed programme
Price PaidAuth OAuth or keyx402 nohosted
Spendesk API + MCP
B 62.3/100Spend management platform from Spendesk SAS in Paris, covering company cards, expense claims, supplier invoices, purchase orders and accounting exports. Outside agents reach it through a REST API with scoped keys or OAuth, and a hosted MCP server.
Verdict Scoped credentials, MCP write permissions that are off by default, an action log and published guidance on prompt injection suit delegated finance work. Access needs a paying customer and a request to Spendesk, most write endpoints are experimental, no official SDK was found, and the status page lists three critical incidents between 2 and 29 September 2026.
Choose it for A finance team already on Spendesk that wants an assistant to analyse spend, follow invoices and prepare the accounting close, or an ERP sync reading payables and settlements.
Strengths
- OpenAPI 3.1 definition with 106 operations, llms.txt and a Markdown copy of every docs page, all public without sign-in
- 37 documented scopes split by resource and by read or write. A token can carry fewer scopes than its key, and keys expire within one year
- MCP write permissions are off by default, enabled per connection by an admin with a second factor, then ticked by each user
Weaknesses
- No public price, free tier or self-serve signup. API access and demo credentials are requested from a Spendesk representative
- Cards, transactions, invoices, purchase orders, webhooks and most writes sit behind experimental scopes granted on request, and may change
- No official SDK found on npm or PyPI, and the MCP server isn't in the official MCP registry
Price PaidAuth OAuth or keyx402 nohosted
BILL
C 60.9/100BILL is a US financial operations platform for accounts payable, accounts receivable and company card spend. Its v3 REST API reads and writes bills, payments, invoices, budgets, cards, transactions and reimbursements, and an MCP server in beta gives read-only access.
Verdict 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.
Choose it 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.
Strengths
- Two public OpenAPI 3.0.1 files cover 326 operations, with llms.txt, a Markdown copy of every docs page and a docs MCP server at
https://developer.bill.com/mcp - Creating a payment, adding a funding bank account and enabling vendor auto-pay need an API session trusted by multi-factor authentication
- The sandbox is self-serve through a sign-up form, charges no subscription fee and moves no real money
Weaknesses
POST /v3/logintakes a user's username and password with a developer key, and the session carries that user's role with no scopes- No idempotency key is accepted on the 203 write operations of the v3 API, payments included.
X-Idempotent-Keyexists only on two webhook subscription calls - The MCP server is beta, read-only and limited to US organisations, and MCP clients other than Claude and ChatGPT need BILL's approval by email
Price $49 / seat-moAuth OAuth or keyx402 nohosted
Brex
C 60.7/100Brex is a spend platform with corporate cards, expense management, bill pay, travel and business accounts. Its REST Developer API reads and writes cards, expenses, spend limits, vendors and transfers, and a hosted MCP server is in beta.
Verdict User tokens carry per-resource scopes with read-only variants, every POST and PUT accepts an Idempotency-Key, and ten OpenAPI specs are public. The Expenses API changes only an expense's memo, there is no customer sandbox or official SDK, and the status page logs API errors lasting over four hours on 4 August 2026.
Choose it for A finance team already on Brex that wants an agent to read expenses and transactions, issue and lock cards, set spend limits, upload receipts and pay vendors.
Strengths
- Ten public OpenAPI 3 specs covering 115 operations, plus llms.txt and a Markdown twin of every docs page
- User tokens take scopes chosen at creation, most with a read-only variant, and card numbers need the separate
cards.panscope - Every POST and PUT accepts an
Idempotency-Key, and Create transfer and Create card require one
Weaknesses
- The Expenses API update endpoint accepts only
memo, so an outside agent can't set a category or custom field on an expense through it - No customer sandbox. The docs say staging isn't a sandbox and won't accept customer tokens
- No official SDK. The docs list three community libraries that Brex doesn't support
Price $12 / seat-moAuth OAuth or keyx402 nohosted
Ramp
C 57.3/100Ramp 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.
Verdict 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.
Choose it 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.
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:readandresource:write, tokens are bound to scopes at issue, andPOST /developer/v1/token/revokeinvalidates them GET /developer/v1/audit-logs/eventsfilters events by user, date, event type and actor type, including Ramp's own agents
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-Keyis accepted on 8 of 155 write operations. Creating a bill, a purchase order or a vendor has none
Price $15 / seat-moAuth OAuthx402 nohosted
Payhawk API + MCP
C 57.1/100Spend management platform from Payhawk Limited in London, covering company cards, expenses, bills, purchase orders and travel. Outside agents reach it through a REST Developer API with read-only or full-access keys, and a hosted MCP server.
Verdict The Developer API has a public OpenAPI 3.1 definition with 179 operations, read-only or full-access keys and a published limit of 15 requests a second. It needs a Payhawk customer account, no official SDK or API changelog was found, and the 82-tool MCP server is added by hand because it is not yet in the assistant directories.
Choose it for A finance team already on Payhawk that wants an ERP or accounting sync, master data kept in step, purchase orders raised from another system, or an assistant that answers spend questions and prepares approvals.
Strengths
- Public OpenAPI 3.1 definition with 105 paths and 179 operations, covering expenses, cards, fund accounts, suppliers, purchase orders and 24 webhook event types
- API keys are created as read-only or full access, sent in a header, and managed by administrators or a custom role
- The limit of 15 requests a second is stated on every operation, and responses carry RateLimit headers with Retry-After on a 429
Weaknesses
- No self-serve route. The API needs a Payhawk customer account, and a development sandbox is requested through a form
- No official SDK on npm or PyPI, no API changelog and no deprecation policy were found. Release notes cover the product only
- The API page's FAQ contradicts the definition on the host name, the page size and whether expenses can be created or reviewed
Price PaidAuth OAuth or keyx402 nohosted
Expensify
E 41.1/100Expensify is an expense management service with receipt scanning, expense reports, approvals, reimbursement and company cards. Its Integration Server API exports report and card data and creates expenses, reports and workspace settings. A hosted MCP server gives read-only search.
Verdict One endpoint exports reports through caller-written templates and creates expenses, reports, rules and workspace settings, with limits of 5 requests per 10 seconds published and a status page that tracks the API separately. There is no OpenAPI spec, changelog, SDK, pagination or idempotency key, and one credential pair carries the whole account's rights.
Choose it for A finance team already on Expensify that wants an agent to export approved reports to an accounting system, create expenses and reports, keep categories, tags and employees in step with an HR system, or mark reports reimbursed.
Strengths
- Export templates written in Freemarker let the caller choose every output field, in CSV, XLS, XLSX, TXT, PDF, JSON or XML, filtered by date, state, workspace and report ID
- Rate limits are published as 5 requests per 10 seconds and 20 per 60 seconds, with status 429 when exceeded
- The status page lists Integration APIs as its own component, and no incident in the 90 days to 8 October 2026 names it
Weaknesses
- No OpenAPI spec, llms.txt, version number or changelog was found for the Integration Server API
- The partnerUserID and partnerUserSecret pair acts with all of the account's rights. No scopes or read-only credential were found for the API
- No idempotency key or pagination is documented, and no official SDK was found
Price $5 / seat-moAuth OAuth or keyx402 nohosted
Head to head
- Airwallex Spend and Issuing vs Mercury API B 68.3 vs B 63.8
- Airwallex Spend and Issuing vs Pleo API + MCP B 68.3 vs B 62.9
- Airwallex Spend and Issuing vs Spendesk API + MCP B 68.3 vs B 62.3
- Airwallex Spend and Issuing vs BILL B 68.3 vs C 60.9
- Mercury API vs Pleo API + MCP B 63.8 vs B 62.9
- Mercury API vs Spendesk API + MCP B 63.8 vs B 62.3
- BILL vs Mercury API C 60.9 vs B 63.8
- Pleo API + MCP vs Spendesk API + MCP B 62.9 vs B 62.3
- BILL vs Pleo API + MCP C 60.9 vs B 62.9
- BILL vs Spendesk API + MCP C 60.9 vs B 62.3
Questions
What are the highest-rated spend management and procurement platforms for AI agents?
Airwallex Spend and Issuing has the highest benchmark score of the 9 ranked spend management and procurement platforms, 68.3 (B). Mercury API is second with 63.8 (B).
How many spend management and procurement platforms are agent-ready?
0 of the 9 ranked here grade BB or better, the bar for agent-ready on the Anchor benchmark.
Which spend management and procurement platforms accept x402 payments?
None of the ranked listings here accepts x402 for its main call yet.
How is this list ranked?
By the Anchor benchmark score out of 100, a weighted mean of the scored categories minus deductions for negative events, from public evidence re-checked as vendors change. Listings cannot pay for a place. The latest assessment behind this page is from 8 October 2026.
How this list is made
The order is the Anchor benchmark score, the same number as on each listing and in the top list. Each listing is graded from public evidence against the benchmark checklist, and the picks above are worked out from those grades, prices and facts. No listing pays for its place, and paid audits or listing help never change a score.
Full ranked table · 36 head-to-head comparisons · Best tools in every category