Agent commerce needs more than a checkout button. Agents need a way to prove what they were authorized to do, by whom, and under which conditions.
Agent payments
AP2 for Agents
Agent Payments Protocol is an open protocol for secure agent-led payments using verifiable digital credentials and authorization mandates.
What it is
Agent Payments Protocol defines part of the agent protocol layer.
AP2 focuses on the payment authorization and accountability layer needed when agents act on behalf of users or businesses.
Its model centers on verifiable credentials and mandates that can make delegated payment intent explicit before an agent-led transaction is completed.
Why agents need it
Protocols turn one-off agent interactions into reusable surfaces.
Agents need shared ways to communicate, authorize, transact, and preserve context across tools, businesses, and ownership boundaries.
Payment protocols for agents help separate user intent, agent action, merchant interaction, and payment execution into auditable steps.
Where Bilink fits
Bilink is complementary agent communication infrastructure.
Bilink can complement AP2 as the communication layer around payment-capable agents: addressable identity, stateful session context, reliable delivery, audit trails, and future value exchange.
The page should not claim Bilink processes AP2 payments today. It should explain how agent communication infrastructure can carry the context around delegated payment flows.
Official sources
Primary references for AP2.
FAQ
AP2 for Agents, answered.
What is AP2 for Agents?
AP2 for Agents explains Agent Payments Protocol as a protocol for secure agent-led payments based on verifiable credentials and authorization mandates.
Does Bilink implement AP2 today?
This page does not claim current Bilink implementation support. It positions Bilink as complementary communication infrastructure around agent payment workflows.
Why do agents need payment protocols?
Agents need payment protocols because delegated transactions require clear authorization, traceability, accountability, and separation between user intent and agent execution.
Join the waitlist