Agent commerce glossary
Agent commerce has a new vocabulary. This glossary maps the core terms to the way Leash implements identity-backed payments.
Why it matters
A builder new to agent payments may search for x402, MPP, agent treasury, or Know Your Agent separately. The glossary connects those terms into one system.
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 implements these concepts as product surfaces: identity APIs, marketplace capability listings, payment links, buyer-kit, seller-kit, MCP tools, CLI operations, and receipt APIs.
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
Use the glossary as an internal linking hub: every term should link to a deeper guide, and every guide should link back to the glossary when it introduces category vocabulary.
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.
Core terms
KYA: Know Your Agent identity and trust signals
x402: HTTP 402 payment-required flow for paid calls
MPP: problem+json machine payment negotiation
Treasury: funds controlled by the agent identity and policy
Receipt: proof that a paid interaction happened
Capability: a discoverable service an agent can call or sellFAQ
Why create a glossary for agent commerce?
Search engines, LLMs, and developers need consistent language for a new category. A glossary helps Leash own those definitions.
Should glossary pages be short?
They can be concise, but each term should include enough context and internal links to help readers choose the right deeper guide.