Rank among the 246 products we drove
- Core work done
- tied #60
- 88%
- 7 of 8 core tasks
- Steps on its own
- tied #35
- 3/ 5
- Find to Leave, no person
- Time to get in
- tied #83
- 8minutes
- Getting in on its own
Yes. Our agent signed up for Mercury on its own in a browser with an email and password, got an API key and used its API and MCP server. No CLI found.
The record
Level confirmed
Not yet
Level from one drive; a second must agree.
- Got in by
- Sign-up in a browser8 minutes
- Got as far as
- Pay: ready to payPayment not yet proven; stopped at the pay button of the $35 a month charge
Connects by
API
Agent payments
None found
On its own · 148 doc pages read
Docs it can act on: llms.txt.
On its own · 8 minutes
No key needed, MCP sign-in, sign-up in a browser.
On its own · 7 of 8 core tasks
Did: send payments and read them back; add, edit and delete payment recipients.
Partly
Ready to pay. Payment not yet proven; stopped at the pay button of the $35 a month charge.
Partly
Nothing to cancel. Its account stays.
- On its own
- Partly
To reach L4: Delete its account, so its keys and login stop working.
See how it ranks in the banking APIs category.
Own Mercury? 9 things to fix. Get your findings, free
Checked 18 Nov 2026: MCP server asks for a sign-in, sign-up page unchanged since the check before.
Find
How an agent connects
API and llms.txt found.
MCP server
10 of 42 testedA server for searching the docs only.
42 tools mapped in our drive
API
75 of 82 testedREST, OpenAPI embedded per reference page.
82 operations mapped in our drive
OpenAPI
UnknownCLI
None foundSDK
None foundllms.txt
YesAgent payments
None foundWalked to the last click ("Start free trial") and stopped: Mercury Books, $35 a month. It checks out through its own checkout. No CAPTCHA at checkout.
Docs
In partCovers getting started, auth, error codes and code examples.
Describes each operation only in part: completeness 50 of 100.
9 of 10 documented ways to do the core work were tried, and 6 of them worked.
docs.mercury.com/reference/getaccountcards
148 of 150 pages read
Get in
Getting in
4 of 4 ways in worked without a person.
The way that worked
Sign-up in a browser8 minutes
- An inboxNeeded
- A browserNeeded
- A personNot needed
- Agent on a serverAPI, MCP, CLIPartlyGets in without a browser (no key needed) and does 0 of its 8 core tasks that way. For a full account, it stops at sign-up: it works only in a browser.
- Assistant in its own browserLike ChatGPT agentPartlySigns up, confirms its email and does 7 of its 8 core tasks, then stops: its account stays. It can't delete its account.
- Signed agentKnown to CloudflareYesThe sign-up page opens.
Every way in
| Way in | What happened | Why |
|---|---|---|
| Sign-up in a browser | Worked | |
| Sign-up in a browser | Worked | |
| MCP sign-in | Worked | |
| No key needed | Worked | Part of the work done |
- CrawlersThe robots.txt on sandbox.mercury.com asks crawlers to stay off sign-up. Nothing to fix.
Use
What an agent can do with Mercury
7 of 8 core tasks done, and 16 of 27 others.
Core tasks
- done there
- tried, not done
- offered, not tried
| Task | Result | Through |
|---|---|---|
| Send money to a recipient | Done | API: done there |
| Add a payment recipient | Done | API: done there |
| Transfer money between own accounts | Done | API: done thereMCP: offered, not tried |
| Read the account balance | Done | API: done thereMCP: offered, not tried |
| List and search account transactions | Done | API: done thereMCP: offered, not tried |
| Create and send an invoice | Done | API: done there |
| Pay a bill | Done | Web app: done there |
| Issue a virtual cardThe API returns 400 or 500 and the web app shows an error. | Blocked | API: tried, not done |
Surface audit: 136 documented operations: 89 run, 44 blocked by sandbox or plan limits and 3 left out because they spend money or reach real people. Of the 89 run, 84 passed and 5 didn't; 5 behaved differently from the docs. By surface, 75 on the API, 10 on the MCP server and 4 elsewhere, such as sign-in and webhooks.
Holds up
67of 100
- Reliability87
- Handles mistakes47
The mean of the two.
Docs match
81of 100
- Docs accuracy94
- Docs completeness50
Docs accuracy counts 70%, completeness 30%.
Surface tested
63of 100
84 of 133 passed: the 136 documented operations less the 3 that spend money or reach real people
What it can't do, and why
- Issue a virtual card in the sandbox The API returns 400 or 500 and the web app shows an error.
- Create or revoke an API token without the dashboard No API, CLI or device login is offered for tokens.
- Get a payment approved A second approver needs a phone number; the requester cannot approve.
- Use the Mercury MCP server with sandbox data MCP only signs in production accounts, which need a phone and EIN.
- Close the account Closing needs a zero balance, and the login stays afterwards.
16 of 27 other tasks done
- Change a card's nickname or spending limitDone
- Freeze or unfreeze a cardDone
- Categorize a transaction or add a noteDone
- Attach a receipt to a transactionDone
- Create a custom expense categoryDone
- Edit or cancel an invoiceDone
- Set up recurring invoicesDone
- Invite a recipient to submit payment detailsDone
- Create a spending budgetDone
- Ask Command to do financial workDone
- View spend insights by categoryDone
- Keep the books in Mercury BooksDone
- Register a webhookDone
- Read the event stream of changesDone
- Invite a team memberDone
- Restrict API token access by IP addressDone
- Download an account statementPartly
- Move cash into TreasuryPartly
- Create a SAFEPartly
- Request a payment that needs approvalBlocked
- Approve a pending paymentBlocked
- Run payrollBlocked
- Cancel a cardNot tried
- Create an invoice customerNot tried
- Apply for a working capital loanNot tried
- Set approval rules and user permissionsNot tried
- Connect QuickBooks, Xero or NetSuiteNot tried
Tips for agent builders
- Use sandbox.mercury.com and the API base https://api-sandbox.mercury.com/api/v1/; production tokens do not work there.
- At the 2FA step choose "Other authentication app" and keep the shown key to compute TOTP codes yourself.
- Put the IPv4 your HTTP client really uses on a Read and Write token; the ipNotWhitelisted 401 names it.
- To pay a bill, create it in Books > Bills, pay the vendor with POST /account/{id}/transactions, then Match bill on that transaction.
- Do not repeat a payment to the same recipient for the same amount within 24 hours; it is refused as a duplicate even with a new idempotency key.
- Use the docs MCP at https://docs.mercury.com/mcp (get-endpoint) to read the exact request schema for any operation.
Pay
Paying
Ways to pay checked 2 Nov 2026.
- ResultPartly. Ready to pay. Payment not yet proven; stopped at the pay button of the $35 a month charge.
- CheckoutWalked to the last click ("Start free trial") and stopped: Mercury Books, $35 a month. It checks out through its own checkout. No CAPTCHA at checkout.
- Ways to pay
- Stripe card form (card checkout)
- TrialIt has a free plan.
Leave
Leaving
- ResultPartly. Nothing to cancel. Its account stays.
- Its accountNot on its own: blocked. The sandbox account and the production application both stay: close is a request flow blocked until the balance is zero and pending items settle, the login stays after closing and data is kept 7 years; production has no close option. API data, token and webhook were removed.
Daily checks
Checked every day
What our agent finds on the product's own site each day, without an account.
Sign-up page,
Loads on the newest check; 14 of 14 days
llms.txt (Its drive found one elsewhere),
Not on its site on the newest check; 14 of 14 days
MCP server,
Asks for a sign-in on the newest check; 14 of 14 days
OpenAPI,
Not on its site on the newest check; 14 of 14 days
Compare
How Mercury compares
For the team behind Mercury
Agents get stuck at Pay
9 things to fix for agents: 4 small, 4 medium and 1 large
One fix can cover several findings.
Agent blockers: 5 foundAgent surfaces: 5 issues found
Get your findings, freeWhat a drive covers
We mail a private link to an address at mercury.com.
It opens the two findings that matter most in full, and every other by title. There is nothing to sign in to.
- FindClear
- Get inClear
- UseClear
- PayBlocks agents
- LeavePartly
Or claim Mercury to see where each issue is and ask for a free drive after a fix.
Want Mercury driven every month? See Watch
On our standard
Best or ahead on 5 of 31 criteria, behind on 4. Each against every product we measured on it.
- Every way in works for an agentAhead of 134 of 193 others, 59 the same.
- Docs an agent can navigateAhead of 128 of 187 others, 59 the same.
- Spend an agent can see and capAhead of 106 of 159 others, 46 the same, 7 higher.
- A way in with no personAhead of 137 of 243 others, 106 the same.
- Sign-in for agents acting for a personBehind 84 of 158 others, 74 the same.
- Delete by API, checkedBehind 52 of 97 others, 45 the same.
- Export before leavingBehind 117 of 189 others, 72 the same.
- Structured resultsBehind 57 of 78 others, 21 the same.
All 31 criteria
- Truthful annotationsAhead of 50 of 91 others, 41 the same.
- Prices an agent can readLevel with 117 of 153 others, 36 lower.
- Errors a program can readLevel with 82 of 145 others, 47 lower, 16 higher.
- Agents may read docs, API and sign-upLevel with 129 of 160 others, 31 lower.
- Fast to the first callLevel with 118 of 135 others, 17 lower.
- Descriptions that say when to use the toolLevel with 56 of 91 others, 22 lower, 13 higher.
- The best way in is built for agentsIn the middle 79 of 196 others lower, 55 the same, 62 higher.
- Tool names that sort themselvesLevel with 85 of 91 others, 6 lower.
- Terms allow an agent's accountLevel with 179 of 189 others, 10 lower.
- Real status codesLevel with 161 of 168 others, 7 lower.
- Errors say what to do nextLevel with 107 of 145 others, 22 lower, 16 higher.
- Typed, tight input schemasLevel with 59 of 91 others, 17 lower, 15 higher.
- llms.txt that worksLevel with 127 of 239 others, 57 lower, 55 higher.
- A path written for agentsIn the middle 48 of 187 others lower, 91 the same, 48 higher.
- WebMCP tools on the web appLevel with 133 of 136 others, 3 higher.
- An agent payment rail on the coreLevel with 205 of 216 others, 11 higher.
- A request id on every answerIn the middle 42 of 143 others lower, 47 the same, 54 higher.
- Results sized for a context windowIn the middle 16 of 70 others lower, 27 the same, 27 higher.
- Agents pick the right toolLevel with 72 of 91 others, 19 higher.
- A tool list that fitsIn the middle 21 of 91 others lower, 26 the same, 44 higher.
- Pages fit one fetchLevel with 118 of 187 others, 69 higher.
- All validation problems at onceLevel with 33 of 57 others, 24 higher.
- Limits known before they hitLevel with 47 of 90 others, 43 higher.
Where Mercury fits
- Category
- Tasks
- Standards
- llms.txtits docs, listed for agents
- Topics
- Docs and llms.txtFind step
- Sign-upGet in step
- Card checkoutPay step
- Delete the accountLeave step
History
Level by drive
One drive so far, on 2 Nov 2026.
Read more on this step
Pay is where our agent stopped at Mercury.
- Finding · 18 Nov 2026How far does an AI agent get in a card checkout?Our agent reached the checkout at 88 of the 190 products it set out to buy from, and the card form at 68.Read
- Guide · 18 Nov 2026Let AI agents pay you per call: x402 and MPPx402 or MPP on a paid endpoint, your prices where agents read them, and plans an agent can buy by API or MCP.Read
- Guide · 28 Oct 2026Tell an AI agent a feature needs a paid planHow to answer an AI agent at a paid-plan wall: 402 or 403, a Problem Details body with the required plan, and an upgrade link a person can open.Read
Every earlier drive is in the history. The level follows these rules. Data under CC BY 4.0.
Found an error? Tell us on this page or read how corrections work.
Questions people ask about Mercury
- Can an AI agent create a Mercury account on its own?
- Yes, in a browser, without a person. Sandbox sign-up in the browser (name, work email, password), then mandatory TOTP 2FA the agent set up itself and backup codes; no sign-up API. Production sign-up separately walled at phone number and EIN.
- Does Mercury have an MCP server, and can an agent connect to it?
- Mercury's docs have an MCP server for searching them. The drive found no MCP server that works the product itself. A new agent can get in on its own: in the drive of 2 Nov 2026, our agent signed up, verified and got its key without a person.
- How does an AI agent get a Mercury API key?
- In the drive of 2 Nov 2026, our agent got its Mercury API key in a browser, without a person. Token made by the agent in the sandbox dashboard (Settings > Tokens) with Read and Write scope and a required IP whitelist; no API or CLI route to create or revoke tokens exists. Revoked in the dashboard, after which the token gets 401.
- Can an AI agent delete its Mercury account?
- Not on its own: blocked. The sandbox account and the production application both stay: close is a request flow blocked until the balance is zero and pending items settle, the login stays after closing and data is kept 7 years; production has no close option. API data, token and webhook were removed.
- Can an AI agent pay for Mercury?
- Partly. Ready to pay: payment not yet proven; stopped at the pay button of the $35 a month charge. It has a free plan.
Cite this page
The page as a reference, in plain text, APA and BibTeX.
Cite this
AgentDrives, “Mercury: AI agent test drive”, 2 November 2026, https://agentdrives.com/tools/mercury. CC BY 4.0.
AgentDrives. (2026, November 2). Mercury: AI agent test drive. https://agentdrives.com/tools/mercury
@misc{agentdrives_mercury_2026,
author = {{AgentDrives}},
title = {Mercury: AI agent test drive},
year = {2026},
month = nov,
url = {https://agentdrives.com/tools/mercury},
note = {Agent test drive, CC BY 4.0},
}Something wrong on this page?
We check it against the drive and correct the page, with the date.