Fletch Docs
Payment primitives for agents on crypto rails
Documentation
Fletch packages multiple provider-backed rails into cleaner product surfaces for agents: prepaid spend, payment links, bridge routes, and treasury swaps. This page covers what each service does, how to call it, and where MCP plus skills fit into the stack.
Services
Each product surface turns a lower-level provider lane into a simpler developer-facing interface with its own purpose, request shape, and operational caveats.
Creates provider-backed prepaid debit card orders and recovers order status. This is the spend primitive for agents that need card-like settlement access.
Creates shareable payment links over crypto rails. Use this when an agent needs a checkout URL that a human or another workflow can open directly.
Creates bridge routes for moving value from one asset/network combination to another. The route returns funding instructions and can be polled later for status.
Quotes and creates supported treasury conversion routes. Conceptually this is the treasury-facing layer on top of bridge-style route execution.
API
These examples target the live public base URL at https://fletch-bank.pages.dev.
Returns supported card amounts, the live provider, and verified settlement rails.
curl https://fletch-bank.pages.dev/api/fletch-pay/catalogCreates a prepaid card order and returns the order ID plus exact funding instructions.
curl -X POST https://fletch-bank.pages.dev/api/fletch-pay/order \
-H "Content-Type: application/json" \
-d '{
"provider": "mpc",
"amount": 25,
"fundingAsset": "BTC:Mainnet",
"email": "ops@example.com"
}'Creates a crypto checkout link and returns a shareable checkout URL.
curl -X POST https://fletch-bank.pages.dev/api/fletch-link/order \
-H "Content-Type: application/json" \
-d '{
"tickerTo": "USDC",
"networkTo": "Base",
"address": "0xabc...",
"amount": 100,
"memo": "API credits",
"name": "Fletch checkout"
}'Creates a bridge route and returns funding instructions plus provider IDs.
curl -X POST https://fletch-bank.pages.dev/api/fletch-bridge/order \
-H "Content-Type: application/json" \
-d '{
"tickerFrom": "USDC",
"networkFrom": "Base",
"tickerTo": "USDC",
"networkTo": "ERC20",
"amount": 100,
"address": "0xabc..."
}'Checks whether a treasury conversion pair is live and provider-backed.
curl -X POST https://fletch-bank.pages.dev/api/fletch-swap/quote \
-H "Content-Type: application/json" \
-d '{
"fromAsset": "USDC",
"fromNetwork": "Base",
"toAsset": "BTC",
"toNetwork": "Mainnet",
"amountFrom": 100,
"destinationAddress": "bc1..."
}'Recover state using the order or route ID returned during creation.
/api/fletch-pay/status?orderId=fletch_pay_123456
/api/fletch-bridge/status?orderId=fletch_bridge_123456__789012Integration
A clean integration usually follows the same path no matter which product surface you use.
Use Pay for prepaid spend, Link for checkout URLs, Bridge for cross-chain movement, and Swap for treasury conversion.
Read catalog or quote routes before creating orders. This is the easiest way to align supported amounts, assets, and network pairs.
Store the returned order or route ID in your own state. Status recovery depends on those IDs.
Agent ordering
For agents, the prepaid order flow is straightforward: request a supported amount, provide a delivery email, receive an order ID plus deposit instructions, then track status until the provider sends the card email.
Send amount, email, and fundingAsset. The live Fletch provider is
mpc, reward, and swype, with supported amounts of 25, 50, 100, 150, 250, 500, 750, and 999 USD.
Fletch returns orderId, providerOrderId, the exact crypto amount to send,
the deposit address, and the payment network.
The user sends the exact amount on the specified network. Later the same orderId can
be used with the status endpoint to recover the current state.
Response shape
Fletch Pay returns a structured order object so agents can store the ID, show the deposit instructions, and poll status later.
order.orderId: Fletch-prefixed order identifier used for later status checks.order.providerOrderId: upstream provider trade ID.order.item.deliveryEmail: email that will receive the card details.order.payment.address: deposit address for funding the order.order.payment.amountCrypto: exact amount to send.order.payment.ticker and order.payment.network: the exact funding rail.BTC:MainnetETH:BaseUSDC:BaseUSDC:ERC20USDT:ERC20USDT:TRC20XMR:MainnetFAQ
These answers focus on the current Fletch Pay flow and the live provider-backed card lane available through the product today.
Fletch prepaid cards are currently issued on major card rails and are generally intended for online purchases plus many in-person merchants that support standard prepaid debit usage. Depending on the provider and your device, some cards may also be added to mobile wallets such as Google Pay or Samsung Pay.
Acceptance still varies by merchant policy, card provider rules, region, and device compatibility. Merchants that refuse prepaid cards or gift-card style payment methods may decline the card even when the card itself is active.
Fletch prepaid cards should not be assumed to work with every merchant. High-friction merchants that require strict 3DS matching, identity-linked verification, or unusually tight anti-fraud checks may reject prepaid card usage.
If you are testing a new merchant or wallet flow, start with a smaller card value first. That is the safest way to verify acceptance in your actual region and checkout path.
Fletch does not support prepaid card ordering from restricted or sanctioned jurisdictions. For the current live provider lane, restricted countries include Afghanistan, Belarus, China, Cuba, Iran, North Korea, Russia, South Sudan, Sudan, Syria, and Venezuela.
Provider rules can change, and additional restrictions may apply based on sanctions, network policy, or the issuing partner. If a jurisdiction is sensitive, confirm provider eligibility before funding an order.
Fletch pricing depends on the live provider and the settlement rail you choose. The current provider lane includes provider-specific fees and coverage constraints that should be checked at order time. the second month, and a 2.75% foreign currency conversion fee.
If your chosen funding asset is not already on a verified supported rail, conversion costs can be reflected upstream before settlement. Merchant-side currency conversion or cross-border card fees can also apply depending on where you spend.
Fletch Pay works best with the currently verified settlement combinations exposed by the
live catalog endpoint. Right now that includes BTC:Mainnet,
ETH:Base, USDC:Base, USDC:ERC20,
USDT:ERC20, USDT:TRC20, and XMR:Mainnet.
The fastest way to confirm what is live right now is to query
GET /api/fletch-pay/catalog and use the returned provider plus
knownGoodCombos as the source of truth.
Choose a supported amount, select the live provider lane, pick a verified settlement asset, and submit the delivery email tied to the card order. Fletch then returns an order ID plus the exact crypto amount, network, and deposit address required to fund it.
After the payment is detected, the provider completes issuance and the card details or
activation instructions are sent to the submitted email. You can use the returned
orderId later with the Fletch status endpoint to recover the current state.
Agent Access
Fletch publishes its agent-facing docs with the site so the same surface can be used by humans, MCP clients, and skill-driven agents.
The live MCP server runs behind the production domain and exposes product tools like catalog lookup, order creation, and status recovery over Streamable HTTP.
{
"transport": "streamable_http",
"url": "https://www.fletch-pay.com/mcp"
}The Fletch skill defines when to use Pay vs Link vs Bridge vs Swap and keeps the Robinhood-first framing while execution still runs on proven provider rails.
Robinhood is the product default, but live settlement and routing still depend on upstream provider support. Treat provider-backed execution details as the source of truth.
Contact
The main public contact point right now is the Fletch X account, alongside the published app, skill, and MCP docs.
Follow product updates and reach the brand surface here: https://x.com/FletchPayRH
Fletch also publishes the raw MCP and skill files that agents can ingest directly.