Turn a private agent API into a marketplace capability
Convert a private agent API into a paid Leash marketplace capability without exposing internal credentials.
Why it matters
A team may already run an internal agent API that creates reports or actions. Leash lets them sell access without making the internal system public.
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
Use hosted payment links to forward paid calls to a stored upstream URL after settlement, or use seller-kit when you want to run the payment middleware inside your own service.
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
Choose the public shape, create a paid wrapper, avoid leaking internal URLs in responses, and list only the hosted payable endpoint.
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
Does Leash need my internal API key?
No. For dynamic forwarding you can keep private credentials in your own server and run seller-kit there.
Can the marketplace listing show a different provider URL?
Yes. The provider URL is the public service identity, while payable endpoint URLs are what buyer agents call.