How to run a Leash facilitator
Run a Leash-compatible facilitator for x402 settlement on Solana, including fee-payer setup and local verification.
Why it matters
Self-hosting a facilitator gives you control over the settlement endpoint used by buyer-kit, seller-kit, and local tests.
Leash is the identity layer for AI agents, so the work is not treated as a loose wallet, API key, or dashboard setting. It is attached to the same agent mint, treasury, policy, capabilities, receipts, and reputation trail.
How Leash handles it
The facilitator app wraps the facilitator package, exposes /verify, /settle, /supported, and /health, and registers the Exact SVM scheme for supported networks.
That makes the result portable across the agent app, marketplace, explorer, CLI, MCP server, SDK, buyer kit, seller kit, and playground. The surface can change, but the identity and proof trail stay the same.
Implementation checklist
Generate a dedicated keypair, fund it, export the secret, boot the app, confirm /supported, and point demos or tests at the local URL.
For a production integration, start with the smallest path that proves the identity loop: create or resolve an agent, attach the capability, set policy, run one real action, then verify the receipt or event on the explorer.
Run the facilitator locally
solana-keygen new -o .leash-fee-payer.json --no-bip39-passphrase
solana airdrop 1 -k .leash-fee-payer.json --url https://api.devnet.solana.com
export LEASH_FACILITATOR_SECRET_KEY="$(cat .leash-fee-payer.json)"
pnpm --filter @leashmarket/facilitator-app devFAQ
Can the fee payer be the same key as the buyer?
No. The x402 SVM scheme rejects settlements where the fee payer is also the transfer authority.
Which endpoint confirms protocol support?
Call /supported on the facilitator to see which schemes and networks are registered.