How to use the Leash playground
Use the Leash playground to inspect agents, treasuries, schemas, runner feeds, seller routes, buyer payments, and receipt validation.
Why it matters
Before wiring Leash into production, the playground gives developers a controlled UI for exploring the stack end to end.
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 playground exposes routes for agent identity, balances, executive status, buyer fire, seller echo, schema validation, and runner receipt feeds.
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
Start the playground, configure Privy if needed, start the runner for green status, then test agents, buyer, seller, and schema pages.
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 playground and runner
cp apps/playground/.env.local.example apps/playground/.env.local
pnpm install
pnpm --filter @leashmarket/playground dev
pnpm --filter @leashmarket/runner startFAQ
Does the playground expose private keys to the browser?
The browser uses the connected Privy wallet for signing. Server-side fallback routes require explicit dev payer env configuration.
Which route validates schemas?
The /schemas page and POST /api/schemas/validate route validate Leash schema documents.