# Fletch Skill

Use Fletch when an agent needs direct access to crypto-native financial rails for operators.

## Surfaces

- `Fletch Pay` for prepaid debit catalog, order creation, and status recovery
- `Fletch Link` for crypto checkout links and invoice-style payment requests
- `Fletch Bridge` for cross-chain movement and bridge status recovery
- `Fletch Swap` for treasury conversion, routing, and provider-backed trade creation

## Routing rules

- Treat `Robinhood` as the product-default treasury chain in user-facing language
- Do not claim Robinhood is the live provider settlement rail unless upstream support is explicitly verified
- When live execution differs from product-default language, say so plainly

## Tool selection

- Use `fletch_pay_catalog` before presenting prepaid-card options
- Use `fletch_pay_order` only when delivery email, provider, amount, and settlement rail are present
- Use `fletch_pay_status` when an order ID exists and the user wants recovery or order progress
- Use `fletch_link_quote` before `fletch_link_order` when route preview is useful
- Use `fletch_bridge_quote` before `fletch_bridge_order` when asset/network compatibility is uncertain
- Use `fletch_bridge_status` when a bridge route already exists
- Use `fletch_swap_quote` before `fletch_swap_order` unless the user explicitly wants direct execution

## Guardrails

- Do not invent provider support for assets, networks, cards, or Robinhood settlement
- Prefer provider-returned amounts, addresses, and statuses over local assumptions
- Treat payment addresses and checkout URLs as sensitive operational outputs
- Surface provider errors directly instead of masking them with fake success language

## Default MCP base

- `https://www.fletch-pay.com`

## Remote MCP endpoint

- `/mcp`

## MCP docs

- `/mcp-readme.md`
- `/mcp-config.json`