Mercury
live · conformance passing
Models Mercury's banking API — the organization, its users and its checking, savings, credit and treasury accounts, with balances projected from their transactions; the transaction lists Mercury pages two different ways; recipients and recipient invites; ACH, check, wire and real-time payments with the 24-hour duplicate guard, approval requests a dashboard reviewer moves, and internal transfers; the event stream as RFC 7396 merge patches and signed webhook deliveries; virtual cards that freeze, unfreeze and cancel; expense categories and merchants; customers and invoices; statements, SAFEs and attachments — along with Mercury's read-only and read-write tokens over Basic or Bearer auth, and the error envelopes it actually answers.
- Category
- Banking
- Environment key
- secret-token:mercury_…
- Verified against
- https://docs.mercury.com/llms.txt 291e3f235e9d6224f86fd1db04af260deb840aa511ff3af4f7d8c6bb903ec554
- Replaces
- A real Mercury bank account, whose payments settle, fail and return on demand and whose webhooks the sandbox cannot send
What it models
Records your code can read, write and edit for the life of the environment. A route the twin does not model returns a provider-shaped refusal rather than a plausible response.
- organizations
- users
- api_tokens
- accounts
- recipients
- recipient_invites
- recipient_attachments
- transactions
- transaction_attachments
- send_money_requests
- transfer_requests
- categories
- merchants
- cards
- statements
- treasury_statements
- treasury_transactions
- events
- webhook_endpoints
- webhook_deliveries
- customers
- invoices
- invoice_attachments
- safe_requests
- oauth_clients
- oauth_grants
Verified in CI against
- openapihttps://docs.mercury.com/llms.txt291e3f235e9d6224f86fd1db04af260deb840aa511ff3af4f7d8c6bb903ec554