Do I need an API key to connect an agent?

Not for the remote server: you sign in with your BlindPay account and pick an instance. The local server, run with npx -y @blindpay/mcp, uses an API key and instance ID from your environment instead.

Which AI clients work with the BlindPay MCP server?

Claude, Claude Code, ChatGPT, Grok, Cursor, VS Code, Codex, Windsurf, Gemini CLI, and any other client that supports remote MCP servers over Streamable HTTP. Clients that only run local servers can use the npx package.

Can I test an agent without moving real money?

Yes. Connect it to a development instance. KYC is approved automatically, payins and payouts complete on their own, and on-chain flows use USDB, a test token with no real funds behind it.

Do compliance checks still apply when an agent makes the call?

Yes. Every tool call runs through the same API as a direct request, with the same KYC and KYB requirements, limits, and audit trail.

When should I use the MCP server, Agent Skills, or the CLI?

Use the MCP server when an assistant should act on your BlindPay account. Use Agent Skills when a coding agent is building your integration and needs to know how BlindPay works. Use the CLI for scripts, CI, and terminal agents that prefer shell commands with JSON output. They work well together.

The complete financial stack for AI agents

Q: Is it safe to let an AI agent use BlindPay?

The remote MCP server signs in with OAuth, so no API key is pasted into a chat. Each connection is bound to the one instance you pick, and the server fills in that instance on every call, so the agent cannot reach another one. You can disconnect it from the BlindPay dashboard at any time, and https://mcp.blindpay.com/mcp/readonly exposes only reads for assistants that should never move money.

Everything your AI assistants need to handle wallets, accounts, and global payments compliantly.

Get Started

Connect your agent

MCP Server

Connect any AI assistant in minutes.

Works with Claude, ChatGPT, Grok, Cursor, or any MCP-compatible host
Sign in with your BlindPay account over OAuth. No API key to paste
Full API surface exposed as MCP tools, with a read-only option
Open source. Inspect it, or run it locally with npx and an API key

MCP on GitHub

Claude Code

Cursor

VS Code

Codex

Claude

ChatGPT

Grok

npx

claude mcp add --transport http blindpay \
  https://mcp.blindpay.com/mcp

Add to Cursor

{
  "mcpServers": {
    "blindpay": {
      "url": "https://mcp.blindpay.com/mcp",
      "auth": {
        "CLIENT_ID": "4c2rAa08DqbVvnon",
        "scopes": [
          "profile",
          "email",
          "offline_access"
        ]
      }
    }
  }
}

Add to VS Code

{
  "servers": {
    "blindpay": {
      "type": "http",
      "url": "https://mcp.blindpay.com/mcp"
    }
  }
}

codex mcp add blindpay --url https://mcp.blindpay.com/mcp

In Claude, open Settings, then Connectors.
Choose Add custom connector and paste https://mcp.blindpay.com/mcp.
Sign in with your BlindPay account and pick the instance the agent may use.

In ChatGPT, open Settings, then Connectors, then Advanced, and turn on Developer mode.
Create a connector with https://mcp.blindpay.com/mcp and OAuth authentication.
Sign in with your BlindPay account and pick the instance the agent may use.

In Grok, open grok.com/connectors.
Choose New connector, then Custom, and paste https://mcp.blindpay.com/mcp.
Sign in with your BlindPay account and pick the instance the agent may use.

{
  "mcpServers": {
    "blindpay": {
      "command": "npx",
      "args": [
        "-y",
        "@blindpay/mcp"
      ],
      "env": {
        "BLINDPAY_API_KEY": "your-api-key",
        "BLINDPAY_INSTANCE_ID": "your-instance-id"
      }
    }
  }
}

Model Context Protocol

Expose BlindPay's full payment API as MCP tools. Any compliant host can discover and call your payment operations directly.

Claude & Cursor ready

Add the remote server URL to Claude, Grok, Cursor, or VS Code and sign in. BlindPay tools appear instantly in your assistant.

OpenAI compatible

Connect the same server to ChatGPT or Codex. OpenAI models discover the payment tools and orchestrate them for you.

Full API surface

Create payouts, query balances, check corridors, and fetch quotes. All accessible via natural language instructions.

Safety and permissions

Agents act on your account only the way you allow.

Sign in, never paste keys

The remote server uses OAuth 2.1. The assistant gets a scoped token, and no API key ends up in a chat history.

One instance per connection

You pick the instance when you connect. The server fills it in on every call, so the agent cannot reach another one.

A read-only endpoint

Point an assistant at /mcp/readonly and it only sees balances, quotes, statuses, and history. Nothing that moves money.

Test on a development instance

KYC is approved automatically, payouts complete on their own, and on-chain flows use USDB test funds.

Revoke at any time

Disconnect an assistant from the BlindPay dashboard. Its next tool call fails and asks the user to reconnect.

Same API, same rules

Tool calls run through the same API as direct requests, with the same compliance checks, limits, and audit trail. Write and delete tools are marked so clients can ask before running them.

MCP tools

Every public API operation, as a tool.

Tools are generated from the same OpenAPI document as the API reference, so a new endpoint becomes a new tool. The read-only endpoint keeps only the reads.

AreaWhat an agent can doAccess

Customers and onboardingCreate and update customers, run KYC and KYB, answer RFIs, request limit increases

Read and write

Quotes and FXQuote payouts, payins, transfers, and FX rates before anything moves

Read and write

PayoutsSend payouts from EVM chains, Solana, and Stellar to bank accounts, then track their status

Moves money

PayinsQuote payins in local currency and follow them until the stablecoins land in a wallet

Moves money

TransfersQuote and execute stablecoin transfers, then track them to completion

Moves money

Bank accounts and walletsAdd bank accounts and blockchain wallets, read balances, turn yield on or off

Read and write

Virtual accountsIssue virtual accounts that receive USD bank transfers and settle to stablecoins

Read and write

Payables and partner feesRegister bills, invoices, boletos, and Pix codes to pay, and set the fees you add to transactions

Read and write

Webhooks and teamManage webhook endpoints and instance members

Read and write

Reference dataLook up available rails, bank details, SWIFT codes, and NAICS codes

Read only

Agent Skills

Teach your AI assistant how BlindPay works.

Domain knowledge for payouts, payins, and compliance flows
Works with Cursor, Claude Code, Codex, and more
One command to install, zero configuration
Pair with MCP for agents that understand and act

Skills on GitHub

# Install agent skills into your project
npx skills add blindpaylabs/skills

# Skills are now available to your AI assistant
# Covers rails, corridors, fees, and API patterns

Agent Skills

Pre-packaged domain knowledge about BlindPay's rails, corridors, and fee structures. Ready to load into any agent.

One-command install

Run npx skills add and your agent gains deep BlindPay context with zero manual configuration.

Structured knowledge

Skills expose structured facts: supported currencies, settlement times, compliance requirements, and API patterns.

Composable with MCP

Pair Skills with the MCP Server for agents that understand BlindPay's domain and can act on it in a single session.

CLI

Full API from your terminal.

Manage customers, payouts, virtual accounts, and webhooks
Structured JSON output on every command with --json
Schema introspection for AI agents to discover the API surface
Predictable exit codes for reliable automation

CLI on GitHub

# Install the BlindPay CLI globally
npm install -g @blindpay/cli

# Configure your API credentials
blindpay config set --api-key <your-api-key> --instance-id <your-instance-id>

# Start using the CLI
blindpay customers list --json

Built for AI agents

Every command supports --json for structured output. Agents can parse responses, handle errors, and chain commands without guessing.

Schema introspection

Run blindpay schema to get full field definitions, types, defaults, and enums. Agents discover the API surface without documentation.

Full API coverage

Payouts, payins, customers, bank accounts, virtual accounts, webhooks, API keys, and reference data. All from one CLI.

Composable with MCP & Skills

Use the CLI alongside the MCP Server and Agent Skills. Three interfaces, one platform, complete coverage.

Frequently asked questions

For agents

Machine-readable from the start.

Point an agent at these instead of the rendered site.

Prompt library

Copy-paste prompts for Claude, Cursor, and other AI agents to integrate, migrate to, and audit BlindPay. Each prompt is grounded in the live API docs.

Browse the prompt library