How to list an identity-backed marketplace capability
List a native marketplace capability with a seller agent identity so buyers can verify who provides the endpoint.
Why it matters
A paid API directory is stronger when every native listing can point to the agent identity responsible for it.
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
Leash marketplace submissions include seller_agent_mint, enrich detail pages with seller identity summaries, and sync approved listings into capability cards.
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
Create or select your seller identity, submit the listing metadata, include endpoint and pricing, then verify the seller identity panel after it appears in marketplace discovery.
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.
Listing identity metadata
{
"name": "Premium Web Search",
"slug": "premium-web-search",
"endpoint": "https://search.example/mcp",
"pricing": { "type": "per_call", "amount": "0.01", "currency": "USDC" },
"seller_agent_mint": "Agnt..."
}FAQ
Do old listings disappear if they are not linked?
No. Legacy listings can remain visible but should be clearly marked as unverified until linked.
Why require a seller agent mint?
It lets buyers connect the capability to a verifiable identity, reputation summary, and proof trail.