Integration
Connect LawPay to Mercury
When New Event fires in LawPay, your agent runs Add customer in Mercury. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want LawPay and Mercury to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What LawPay can start in Mercury
When New Event in LawPay
then Add customer in Mercury
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with LawPay and Mercury
Triggers and actions 2 triggers · 31 actions
- New Event
Triggers when a new LawPay gateway event occurs, such as a transaction being authorized or completed.
- New Transaction
Triggers when a new charge, refund or credit is created in LawPay.
- Cancel Recurring Charge
Cancels a LawPay recurring charge so no further payments are collected.
- Capture Charge
Captures an authorization-only LawPay card charge so its funds settle.
- Create Charge
Charges a customer in LawPay using a saved payment method or a one-time payment token.
- Create Credit
Sends funds to a customer's card or bank account in LawPay without an original charge (the Credit feature must be enabled on the account).
- Get Current Merchant
Returns the LawPay merchant tied to the secret key, including its operating, trust and eCheck accounts.
- Get Event
Returns one LawPay gateway event, such as a transaction being authorized, with its data.
- Get Recurring Charge
Returns a LawPay recurring charge with its schedule, totals and next payment date.
- Get Transaction
Returns one LawPay charge, refund or credit by its ID, including any refunds applied to a charge.
- List Recurring Charge Occurrences
Returns the scheduled payments of a LawPay recurring charge with their due dates and status.
- Refund Charge
Refunds part or all of a LawPay charge back to the original card or bank account.
- Search Transactions
Returns LawPay transactions matching a text search, date range or account, newest first.
- Void Transaction
Voids a LawPay charge, refund or credit that has not been captured yet, releasing any hold.
- Add customer
Creates a new Accounts Receivable customer in Mercury that you can invoice.
- Add internal transfer
Transfers funds between two Mercury accounts in the same organization and returns the paired debit and credit transactions.
- Add invoice
Creates an invoice in Mercury for one of your customers, with line items, due date and payment options.
- Add recipient
Creates a new payment recipient in Mercury, with optional ACH, wire, real-time payment or check details.
- Get account
Returns a Mercury bank account by its ID, including its name, status, account and routing numbers, and current and available balances.
- Get invoice
Returns the details of a Mercury invoice, including its customer, amount, status, dates and line items.
- Get organization
Returns your Mercury organization's details, including legal business name, EIN, DBAs and subscription tier.
- Get recipient
Returns the details of a Mercury payment recipient, including name, emails, default payment method and routing information.
- Get transaction
Returns a single Mercury transaction by its ID, including amount, status, counterparty, attachments and related transactions.
- List accounts
Returns all Mercury bank accounts in your organization, including balances, account and routing numbers, and status.
- List account statements
Returns the monthly statements for a Mercury checking or savings account, optionally limited to a date range.
- List categories
Returns the organization's custom expense categories used to classify transactions.
- List customers
Returns the accounts receivable customers on your Mercury account (up to 1000).
- List invoices
Returns the accounts receivable invoices in your Mercury organization, up to 1,000 at a time.
- List recipients
Returns the payment recipients saved in your Mercury account (up to 1000).
- List transactions
Returns transactions across all Mercury accounts, optionally filtered by date, status, account, card, category or search text.
- Send money
Sends money from a Mercury account to a saved recipient by ACH, check, domestic wire or real-time payment. Returns the created transaction.
- Update recipient
Updates an existing payment recipient's name, contact details and payment routing information.
- Update transaction
Updates the note and/or category of an existing Mercury transaction.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from LawPay
LawPay to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
LawPay to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
LawPay to MailchimpMailchimp marketing automation and email platform.
LawPay to StripeStripe is a payment processing platform for online businesses.
LawPay to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
LawPay to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Mercury
HubSpot to MercuryHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to MercuryGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to MercuryGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to MercuryGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
LawPay and Mercury, answered
What can start an automation from LawPay?
Any of LawPay's 2 triggers in the catalog, including New Event and New Transaction. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Mercury when something happens in LawPay?
Any of Mercury's 19 actions, including Send money, Update recipient, Update transaction and Add customer. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Mercury to LawPay?
Mercury has no triggers in the catalog today, so automations start in LawPay. If you need the other direction, ask: your agent reads Mercury's API documentation and adds it.
Do I have to build a connector for LawPay or Mercury?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
Can my AI client use LawPay and Mercury without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.