What pay.sh capabilities mean inside Leash

Agents should not need separate directories for every paid API ecosystem. pay.sh providers can appear in the same discovery experience.

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.

Leash fetches pay-skills registry data, labels it with source pay-skills, expands providers into endpoints, and keeps seller identity null until a provider attaches a Leash identity.

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.

Search pay.sh providers, inspect endpoint count and pricing, open the detail page, and add the provider to the agent favorites library if it is useful.

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.