Leash marketplace for agent developers
A developer overview of Leash marketplace: identity, payable endpoints, discovery, buyer-kit, seller-kit, and receipts.
Why it matters
Agent developers need one place to publish services, let other agents find them, and get paid without rebuilding payments and reputation from scratch.
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 connects listings to payment links, identity verification, stablecoin settlement, and receipts.
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
Pick a seller identity, choose hosted links or seller-kit, create endpoint rows, add docs, test buyer-kit, and monitor receipts.
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.
FAQ
Is Leash marketplace only for no-code links?
No. Hosted payment links are one path; seller-kit is the code-first path for dynamic servers.
What should developers build first?
Start with a narrow paid endpoint that returns a predictable JSON result.