Manage your treasury with
the AI you already use
Lynq Capital ships a remote MCP server for your business banking. Connect it to Claude, Claude Code, ChatGPT, Codex, or Kimi to check balances, review wallets and limits, and draft payouts — with company-scoped API keys and human approval on every dollar that moves.
POST https://lynqcapital.co/api/mcpAuthorization: Bearer lynq_sk_…
Connected in three steps
No SDK, no local install, no new vendor login — one API key and one URL.
Create an API key
In the Lynq dashboard, go to Settings → API keys and create a company-scoped key (prefix lynq_sk_). Choose read-only for questions and reporting, or add the write scope to let your AI draft wallets and payouts. Keys are revocable at any time.
Connect your AI client
Add https://lynqcapital.co/api/mcp as a remote MCP server (or custom connector) in your AI client and authenticate with your API key as the Bearer token. Works with Claude, Claude Code, ChatGPT, Codex, Kimi, and any MCP-compatible client.
Ask, draft, approve
Ask about balances, wallets, limits, and payout status in plain language. When your AI drafts a payout, it lands in your existing maker-checker approval queue — a different admin approves it before anything moves.
Works with your AI client
Any MCP-compatible client can connect. Here's how the popular ones do it.
Claude
On claude.ai or Claude Desktop, open Settings → Connectors and choose Add custom connector. Name it Lynq Capital, paste the MCP endpoint, and authenticate with your API key as the Bearer token. Available on paid Claude plans.
Claude Code
Add the server from your terminal:
claude mcp add --transport http lynq https://lynqcapital.co/api/mcp --header "Authorization: Bearer lynq_sk_…"
ChatGPT
In ChatGPT settings, open Connectors and add a custom MCP connector (developer mode on paid plans). Paste the MCP endpoint and your API key as the Bearer token, then ask ChatGPT about your treasury.
Codex
Add Lynq to ~/.codex/config.toml:
[mcp_servers.lynq] url = "https://lynqcapital.co/api/mcp" bearer_token_env_var = "LYNQ_API_KEY"
Kimi
In Kimi Code CLI, run /mcp-config and add an HTTP MCP server named lynq with the MCP endpoint and your API key as the Bearer token — Kimi walks you through the setup conversationally.
Any MCP client
MCP is an open standard. Point any compatible client at https://lynqcapital.co/api/mcp with your Bearer key and it will discover all seven tools automatically.
Agentic CLIs — skill file
Using Claude Code, Kimi Code, or Codex CLI? Drop our agent skill into your agent's skills directory and it learns the whole treasury API — balances, wallets, limits, and draft payouts — in one file.
Seven tools, zero surprises
Five read-only tools for visibility, two draft-only tools for action. The AI can never move money.
Read-only tools
| Tool | What it does |
|---|---|
| get_balances | Live balances across every wallet in your company. |
| list_wallets | All segregated wallets — treasury, client, campaign, entity — with labels and status. |
| get_wallet_activity | Recent transaction history for a specific wallet. |
| get_limits | Spending limits currently set per wallet, employee, or campaign. |
| list_payout_requests | The payout approval queue: pending, approved, executed, or rejected. |
Draft-only write tools
| Tool | What it does |
|---|---|
| create_wallet | Draft a new segregated wallet for a client, campaign, or entity. |
| create_payout_request | Draft a payout — it lands in the human approval queue and never moves funds on its own. |
Try: “What's our total balance across client wallets?” · “Show pending payout requests” · “Draft a $2,500 payout from the Acme Q3 wallet to our saved vendor.”
Built so the AI can advise, never act alone
The same controls that govern your dashboard govern your AI — scoped keys, human approvals, regulated custody, and an audit trail for everything.
Company-scoped, revocable keys
Every API key belongs to exactly one company, so your AI only ever sees your business. Rotate or revoke any key in Settings → API keys in seconds.
Read vs. write scopes
Issue read-only keys for questions, reporting, and reconciliation. The write scope is separate — and even it can only create drafts.
Draft-only writes
The AI can draft wallets and payout requests, but it can never move money. Drafted payouts sit in the approval queue with the full fee breakdown attached.
Maker-checker approvals
Every payout — drafted by a human or an AI — requires approval from a different admin before execution. No self-approval, no exceptions.
Treasury custody by Bridge
Funds are custodied by Bridge as the regulated provider of record. Lynq never holds keys, receives funds, or books customer balances.
Full audit trail
API key creation and revocation, every draft, and every approval decision is written to immutable audit logs with actor records.
- Segregated wallets per client, campaign & employee
- Spending limits per wallet, employee & campaign
- Fund by ACH or wire via dedicated virtual accounts
- Global payouts: USD → EUR, MXN & BRL
- Accept USDC — auto-converts to your USD balance
- Plaid bank linking & KYB-verified accounts
Put your treasury on speaking terms with your AI
Contact us to get early access. We'll set up your account, walk you through API keys, and connect your first AI client together.
Lynq Capital is a financial technology company and is not a bank. Stablecoin custody and payment services are provided by Bridge (Bridge Building Inc. / partner banks). Balances held with custodial partners are not bank deposits and are not FDIC-insured.