FurlPay Docs
Open App
  • Services & Availability
  • Quickstart
  • For AI Agents
  • Monorepo
  • API Routes
  • Authenticationupdated
  • Webhook Eventsupdated
  • Error Codesupdated
  • Rate Limitsnew
  • Configuration & Setupnew
  • Merchant Paymentsnew
  • Payroll & Payoutsnew
  • Agentic Payments (x402)updated
  • Agent Trust & Mandates (TAP)updated
  • CCTP Cross-Chainupdated
  • LI.FI Swapsupdated
  • FurlPay Travels (Travel MCP)updated
  • Solana Actions & Blinks
  • Settlement Workspacenew
  • FURL Tokennew
  • Claude Connectorupdated
  • AI Assistants
  • Circlenew
  • Ramp Providersnew
  • Telegram Mini Appnew
  • Stripe Crypto
  • Persona KYC
  • Regulatory status
  • Screening & Casesnew
  • Security Postureupdated
  • Signing & WebAuthnupdated
  • Help Center
  • Getting Started
  • KYC Verification
  • Passkeys & Biometrics
  • Privacy & Data Protection
  • Transaction Statuses
  • Gasless Transfers
  • Deposits & Withdrawals
  • Managing Virtual Cards
  • Freezing & Unfreezing Cards
  • Declined Transactions
  • SDK & API Support
  • x402 Monetization Basics
  • Booking Travel
  • Travel Refunds & Cancellations

Resources

  • Changelog
  • System Status
  • OpenAPI Spec
  • Community
  • GitHub
Docs/Integrations/AI Assistants

Integrations

AI assistants and MCP

FurlPay provides an MCP endpoint for connecting compatible assistants and agent clients to scoped account tools. Tool availability depends on the user's consent and the status of any service the tool uses.

An assistant cannot bypass payment controls

FurlPay's Claude connector can read authorized data and prepare certain actions for human approval. It cannot settle a payment from a chat message. x402, MPP and gasless production settlement remain gated. The x402 endpoint returned 503 controls_unavailable on 11 October 2026, so its challenge flow is currently unavailable as well.

Connect through MCP

The FurlPay MCP endpoint is https://furlpay.com/api/mcp. Claude and other compatible clients can use the endpoint's authorization flow and request only the scopes the user approves.

For client-specific setup, available tools, permission scopes and the exact human-approval boundary, use the Claude connector guide.

Registering your own agent

An application can register an agent's public key through POST /api/agents/keys. Authenticated registration binds that key to the account and can attach per-transaction limits, a daily budget and allowed categories. These controls limit authorized actions; they do not enable a disabled payment rail.

Read, prepare and execute are different

  • Read tools return information covered by the granted scope.
  • Prepare tools can create a quote, intent or approval link without moving funds.
  • Execution requires the applicable user authorization and a currently enabled rail.
  • Travel search and market data do not imply live booking or brokerage execution.

Check service availability

Before exposing an agent tool that may move funds, check /api/rails and the service availability overview. Treat an unavailable or unknown status as a reason to stop, not as permission to proceed.

Did this page help?
Edit this page on GitHub

← Previous

Claude Connector

Next →

Circle