canonical: https://jentic.com/apis/mercury.com/mercury # Mercury API The Mercury API provides programmatic access to Mercury business bank accounts. It lists accounts and their balances, reads transactions across all accounts or a single account, and returns transaction detail and lets you update transaction metadata. It manages recipients and sends money to them, lists cards for an account, exposes categories and organization information, and supports webhooks and an OAuth flow so applications can act on behalf of a Mercury customer. ## For AI agents List Mercury bank accounts and balances, read and annotate transactions, manage recipients and send payments, list cards, and manage webhooks and organization data. Supports an OAuth flow so applications can act for a Mercury customer. ## Scope Covers Mercury account data, transactions, recipients, and payments; does not open accounts, issue new cards, or provide lending through this surface. Use for banking data access and payments. ## Capabilities - List business bank accounts and read their balances - Read transactions across all accounts or a single account and fetch transaction detail - Update the metadata on a transaction - Manage recipients and send money to a recipient - List cards for an account and read categories and organization information - Create and list webhook endpoints and run the OAuth authorization flow ## Use cases ### Finance operations for an AI agent Give an AI agent read access to Mercury account balances and transactions without hand-wiring the bearer token or handing it the ability to move money. Through Jentic the agent discovers the account and transaction operations by intent and calls them with a validated input schema, so a finance assistant can answer 'what is our balance' and 'what did we spend last week' while payment operations stay outside its allowed set. Example prompt: List all accounts, read the last 30 days of transactions, and summarise total inflow and outflow by category ### Transaction sync and bookkeeping Pull transactions across accounts into a bookkeeping or analytics system, fetch detail on individual transactions, and update transaction metadata such as notes and categories. This backs a nightly sync that keeps an accounting ledger aligned with Mercury activity and enriches transactions for reporting. Example prompt: Read new transactions since the last sync and set a category on each based on the counterparty ### Payments and recipient management Add and list recipients and send money to them, so an approved workflow can pay vendors or reimburse expenses. Because sending money is a distinct operation, you can keep it behind stricter controls than the read operations while still automating the parts that do not move funds. Example prompt: Add a new vendor as a recipient and send an approved payment to them, returning the resulting transaction ### Event-driven account monitoring Register webhook endpoints to receive account events and read the event history, so a monitoring tool learns about new transactions and account changes as they happen rather than by polling. Combined with the read operations, this supports alerting and reconciliation workflows. Example prompt: Create a webhook endpoint for transaction events and confirm it is registered ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/accounts` | List all accounts and balances | | GET | `/accounts/{accountId}/transactions` | List transactions for an account | | GET | `/transactions` | List transactions across all accounts | | GET | `/cards` | List cards | | POST | `/recipients` | Add a new recipient | | POST | `/transactions/pay` | Send money to a recipient | ## Key resources - **Accounts** — List accounts, read balances, and list an account's cards - **Transactions** — Read transactions across accounts, fetch detail, and update metadata - **Recipients** — Manage payment recipients and send money to them - **Cards** — List cards issued on accounts - **Webhooks** — Create and list webhook endpoints for account events - **Organization** — Read organization information, categories, and events ## Why Jentic - **Setup:** Wiring the Mercury API by hand means sending your token as a bearer credential in the Authorization header and, for third-party apps, implementing the OAuth authorization flow. Through Jentic you install once, import Mercury from the API Directory, store the token once, and your agent calls the account, transaction, and payment operations directly. - **Permission scoping:** You choose the operations your agent may call, so a finance assistant can be limited to reading accounts and transactions while the send-money and recipient operations stay outside its allowed set. Rules bound which operations run, which matters most when the API can move real money. - **Credential handling:** Your Mercury API token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'read bank transactions' or 'send a payment', and Jentic returns the matching Mercury operation with its input schema so the agent calls the right endpoint without reading the reference docs. ## Related APIs - **Plaid** — Connects to thousands of banks to read balances and transactions. - **Brex** — Business banking and spend management for companies. - **TrueLayer** — Open banking payments and account data across European banks. ## FAQ ### What authentication does the Mercury API use? The Mercury API authenticates with a bearer token in the Authorization header, per its OpenAPI spec, and also supports an OAuth flow that identifies an application with a client_id for acting on behalf of a customer. You create an API token in your Mercury settings. Through Jentic the token is stored once and injected at call time, so your agent never handles it directly. ### Can I read account balances and transactions with the Mercury API? Yes. The accounts operation lists your business accounts and their balances, and the transaction operations read activity across all accounts or a single account and return the detail of an individual transaction. You can also update transaction metadata such as notes and categories for bookkeeping. ### Is there a Mercury MCP server? You do not need an MCP server to give your agent the Mercury API. Jentic connects it directly from the API Directory: import it, store your API token once, and your agent calls the account, transaction, and payment operations on demand. Nothing extra runs, and no server tool definitions sit in the agent's context between calls. ### Can I limit what my agent is allowed to do with the Mercury API? Yes. Write a rule that allows only the read operations, such as listing accounts and reading transactions, and leaves out the send-money and recipient operations. The agent can then report on balances and spending but cannot initiate a payment. Every call it makes is logged, so you can audit exactly which operations ran. ### What are the rate limits for the Mercury API? The OpenAPI spec does not specify rate limits. Any limits are set by Mercury for your account, so check the Mercury API documentation or your account settings for the quota that applies to your token. ### How do I read my Mercury transactions through Jentic? Search Jentic for 'list bank transactions' to find the transactions operation, which returns activity across your accounts, and pair it with the accounts operation to resolve balances first. Jentic returns each operation with its input schema so your agent calls it correctly. To run it on your own infrastructure, install Jentic One from its GitHub repo.