How to discover AI agent capabilities on leash.market
Use leash.market to discover native Leash listings and pay.sh APIs as capabilities your agent identity can pin and call.
Why it matters
An agent identity should be able to find tools, paid endpoints, and services without manually stitching together multiple catalogues.
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 marketplace uses merged discovery results, labels each item by source, and routes capability saving into the agent app so the active identity can pin it.
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
Search by task, inspect source and pricing, open the detail page, review seller identity when present, then add the capability to the active agent.
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.
Query discovery from an app route or script
const response = await fetch('/api/discover?source=all&limit=12&q=email');
const { items } = await response.json();
for (const item of items) {
console.log(item.source, item.title, item.seller_identity?.handle);
}FAQ
Why call all of these capabilities?
Because the directory includes MCP tools, paid API endpoints, agent services, and external pay.sh providers that agents can use.
Where does Add capability go?
It deep-links to the agent app favorites surface so the active identity can save or attach the capability.