Mercury integration

Finance & Payments · 1 action · Bearer token auth

Business banking platform for startups and scaling companies

Put Mercury to work View Mercury integration docs

Overview

The ModuleX Mercury integration lets a ModuleX agent operate Mercury on your behalf — working across account infos — directly from a plain-English request, using your organization's own Mercury credentials. No pre-built workflow is required: the agent picks the right Mercury action for the task.

Mercury is a finance & payments platform. ModuleX adds the agent layer: ask for an outcome and it selects and runs the right Mercury action — or, when you want a repeatable process, the composer assembles a Mercury workflow for you, streaming the nodes onto the canvas as it builds.

Ask the assistant

Drive Mercury in plain English

Type what you want. A ModuleX agent picks the right Mercury action — or chains several — and runs it. No workflow to build.

Show me the account infos that match what I describe
resolves toget_account_info

Use cases

What you can automate with Mercury

Look up an account info on demandget_account_info

At a glance

Mercury integration at a glance

VendorMercury

CategoryFinance & Payments

Actions available1

AuthenticationBearer token

Uses your own credentialsYes

Works with the assistantYes

Works in the composerYes

Multi-step / tool-chainingYes

Technical referenceView docs

Integration version1.0.0

Last updatedJun 2026

Reference

The 1 Mercury action

Account Infos1

get_account_info

Retrieve information about a specific Mercury bank account

See full parameters and response schemas in the Mercury integration docs

Two ways

Two ways to use Mercury in ModuleX

Ask the assistantType what you want done and a ModuleX agent picks the right Mercury action and runs it — no workflow to build.

Compose a workflowNeed it to happen every time? Describe the process and the composer wires Mercury into a repeatable workflow you can run on a schedule, from chat, or as an API.

Security

Connecting Mercury

Bearer tokenMercury uses bearer-token authentication. You provide a Mercury access token; ModuleX encrypts it and scopes it to your organization so the whole team can use Mercury.

Step-by-step setup in the Mercury docs

Pairs well with Mercury

Agents often chain Mercury with these — connect them once and the agent can use all of them in a single task.

Stripe50 actions

Kalshi22 actions

Lemon Squeezy10 actions

RevenueCat10 actions

Coinbase8 actions

Nasdaq Data Link7 actions

FAQ

Mercury + ModuleX FAQ

A ModuleX agent can run any of Mercury's 1 action — across account infos — from a plain-English request, using your organization's own Mercury credentials.

No. The agent selects the right Mercury action from your prompt. A workflow is only needed when you want a repeatable process — and the composer builds that for you from a description.

With your own Mercury access token, stored encrypted and scoped to your organization.

1, spanning account infos.

Mercury runs on your own credentials, so any Mercury usage is billed by Mercury directly. ModuleX meters the agent run — and if you connect your own model keys, there's no ModuleX markup on model usage.

Put Mercury to work in ModuleX.

Connect Mercury once with your own credentials and let your agent run its 1 action on demand.

Put Mercury to work View technical docs

Last updated: Jun 2026Browse all 175 integrations →