Agent Payments Protocol ↗
Identity & trustA protocol for expressing and verifying authority for agent-performed payments.
Read evidence →See where commerce, payments, transport and agent coordination overlap or complement each other.
Full commerce flow, discovery/catalog, checkout, payments/authorization, agent interoperability and merchant implementation appear as separate comparison dimensions. Select up to four protocols, then inspect the rows that answer your question.
8 protocol entries · Alphabetical order · Checked 28 Sep 2026
A protocol for expressing and verifying authority for agent-performed payments.
Read evidence →A standard for communication and task coordination between agents.
Read evidence →A commerce interaction standard connecting businesses, buyers and their agents.
Read evidence →A draft framework for card-based agentic payments and future specification work.
Read evidence →A payment protocol for machine consumption of web services.
Read evidence →A standard interface connecting applications to tools, resources and prompts.
Read evidence →A common model for agents and businesses to negotiate commerce capabilities.
Read evidence →Which commerce integration path matches your target surface?
Explore →Do you need purchase authority, service payments, or both?
Explore →What permits the action, and what pays for the resource?
Explore →Which machine payment flow fits your resource and payment methods?
Explore →Are you exposing a tool, or coordinating work between agents?
Explore →Where does commerce state end and purchase authority begin?
Explore →Are you choosing commerce operations or an authorization model?
Explore →Do you need a commerce model, a tool interface, or both?
Explore →What does the tool mean in the context of commerce?
Explore →Which part of the purchase does each layer own?
Explore →