BlindPay primary sources — 2026-04-30

Project status in this pass

• No canonical standalone whitepaper or litepaper surfaced.
• The clearest current source of truth is the official site, docs corpus, well-known AI/agent endpoints, and first-party GitHub repos.

Primary-source snapshots

1) Main site

• URL: https://www.blindpay.com/
• Key excerpt:
  • The homepage frames BlindPay as an “API-first infrastructure for global finance” that connects stablecoins, local payment rails, business accounts, and compliance through a unified API.
  • It prominently exposes machine-readable and agent-oriented surfaces including /.well-known/api-catalog, /.well-known/mcp/server-card.json, /.well-known/agent-skills/index.json, /.well-known/oauth-protected-resource, llms.txt, and llms-full.txt.
  • The homepage links directly to docs, API reference, GitHub-hosted agent skills, and an npm-delivered MCP server.

2) Docs overview

• URL: https://www.blindpay.com/docs/getting-started/overview
• Key excerpt:
  • The docs describe BlindPay as global payment infrastructure for worldwide money transfers using both traditional fiat currencies and stablecoins.
  • They explicitly say BlindPay does not provide wallet services and operates as a non-custodial payment processor.
  • The overview names support for EOA and account-abstraction wallets, multiple stablecoins including USDC and USDT, and networks including Mainnet, Base, Arbitrum, Polygon, Stellar, and Tron.
  • The payout-flow and payin-flow diagrams clarify that BlindPay collects approved stablecoins, initiates local fiat transfer, confirms settlement, and refunds the originating wallet if settlement fails.

3) Quickstart / stable-to-fiat flow

• URL: https://www.blindpay.com/docs/getting-started/quick-start
• Key excerpt:
  • The quickstart requires a BlindPay account, development instance, API key, terms acceptance, receiver creation, bank-account creation, and then payout execution on Base Sepolia Testnet.
  • This is strong evidence that BlindPay exposes a real operational integration surface rather than only high-level marketing copy.
  • The docs navigation also shows a broader surface including receivers, bank accounts, virtual accounts, blockchain wallets, offramp wallets, payout quotes, payin quotes, wallets, transfers, API keys, webhooks, partner fees, and upload.

4) MCP server materials

• URLs:
  • https://www.blindpay.com/blog/mcp
  • https://www.blindpay.com/.well-known/mcp/server-card.json
• Key excerpt:
  • The MCP blog says BlindPay connects AI coding assistants to its payment infrastructure so developers can execute payment operations with natural language instead of manual API calls.
  • The blog names capabilities including quote generation, receiver management, payout processing, virtual-account creation, webhook configuration, and FX rates.
  • The server card identifies @blindpaylabs/blindpay-mcp as a stdio MCP server that exposes BlindPay’s payments API as tools and points to a dedicated GitHub repository.

5) Agent skills index and repo

• URLs:
  • https://www.blindpay.com/.well-known/agent-skills/index.json
  • https://github.com/blindpaylabs/blindpay-skills
• Key excerpt:
  • The skills index describes “BlindPay Agent Skills” as domain knowledge, API patterns, and compliance flows for the BlindPay stablecoin payments API.
  • It advertises a full skill pack covering rails, corridors, fees, KYC/KYB, payouts, virtual accounts, and webhooks, plus the separate MCP server entry.
  • The GitHub repo README reinforces that BlindPay is intentionally packaging its infrastructure for assistants like Cursor, Claude Code, and Codex.

6) CLI materials

• URLs:
  • https://www.blindpay.com/blog/cli
  • https://github.com/blindpaylabs/blindpay-cli
• Key excerpt:
  • The CLI blog calls BlindPay “the most AI-native stablecoin infrastructure” and says the CLI is built for developers and AI agents with structured JSON output, schema introspection, and predictable exit codes.
  • The repo README shows concrete command groups for instances, receivers, bank accounts, blockchain wallets, quotes, payouts, payins, virtual accounts, webhook endpoints, partner fees, API keys, rails, and schema inspection.
  • Together these materials make BlindPay look less like a simple checkout widget and more like a programmable payments control plane with both human and agent operating modes.

Working conclusion

BlindPay is best cataloged as non-custodial stablecoin-fiat payments infrastructure with a broad developer control plane and an unusually explicit agent-facing surface. The clearest architectural signal is not a formal whitepaper but the combination of flow-of-funds docs, operational APIs around receivers and settlement, and first-party MCP / skills / CLI materials that show the company is packaging its payment stack for software and AI-assisted operators alike.