Can an AI agent use Mercury?

Mercury is a business bank with a test sandbox.

mercury.comBanking APIs

Driven 2 Nov 2026

Evidence sha256 ff5485e0JSONMarkdownFeedCite

L3

Does the work

  1. L0
  2. L1
  3. L2
  4. L3
  5. L4
  6. L5

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
Holds up
tied #92
67/ 100
Reliability under errors

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

  1. Find

    On its own · 148 doc pages read

    Docs it can act on: llms.txt.

  2. Get in

    On its own · 8 minutes

    No key needed, MCP sign-in, sign-up in a browser.

  3. Use

    On its own · 7 of 8 core tasks

    Did: send payments and read them back; add, edit and delete payment recipients.

  4. PayFirst stop

    Partly

    Ready to pay. Payment not yet proven; stopped at the pay button of the $35 a month charge.

  5. Leave

    Partly

    Nothing to cancel. Its account stays.

  • On its own
  • Partly

To reach L4: Delete its account, so its keys and login stop working.

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 tested

    A server for searching the docs only.

    42 tools mapped in our drive

  • API

    75 of 82 tested

    REST, OpenAPI embedded per reference page.

    82 operations mapped in our drive

  • OpenAPI

    Unknown
  • CLI

    None found
  • SDK

    None found
  • llms.txt

    Yes
  • Agent payments

    None found

    Walked 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 part

    Covers 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

Every way in and what happened
Way inWhat happenedWhy
Sign-up in a browserWorked
Sign-up in a browserWorked
MCP sign-inWorked
No key neededWorkedPart 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
Core tasks of Mercury: the result and the surfaces they went through
TaskResultThrough
Send money to a recipientDoneAPI: done there
Add a payment recipientDoneAPI: done there
Transfer money between own accountsDoneAPI: done thereMCP: offered, not tried
Read the account balanceDoneAPI: done thereMCP: offered, not tried
List and search account transactionsDoneAPI: done thereMCP: offered, not tried
Create and send an invoiceDoneAPI: done there
Pay a billDoneWeb app: done there
Issue a virtual cardThe API returns 400 or 500 and the web app shows an error.BlockedAPI: 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

From this drive

6 tips
  • 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.

  1. FindClear
  2. Get inClear
  3. UseClear
  4. PayBlocks agents
  5. 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.

All 31 criteria
How each criterion is graded

Where Mercury fits

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.

Every earlier drive is in the history. The level follows these rules. Data under CC BY 4.0.

Found an error? 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
Plain
AgentDrives, “Mercury: AI agent test drive”, 2 November 2026, https://agentdrives.com/tools/mercury. CC BY 4.0.
APA
AgentDrives. (2026, November 2). Mercury: AI agent test drive. https://agentdrives.com/tools/mercury
BibTeX
@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.