Protocol
ACP (Agentic Commerce Protocol)
A commerce protocol for AI-assisted purchase flows where agents, people, and merchants complete orders together.
ACP is a protocol direction for agentic commerce where AI surfaces can pass order context to merchants while merchants keep control of acceptance, payment processing, fulfilment, returns, support, and customer relationships.
Why it matters
Agentic checkout turns product discovery into a transaction surface. That makes approval, data minimisation, payment scope, support ownership, and auditability business-critical.
How HARNEXA uses it
HARNEXA maps ACP readiness before implementation: catalogue evidence, policy facts, order acceptance rules, human approval points, and AgentOps reporting must be defined first.
FAQ
Questions this definition answers.
Does ACP mean the agent can place orders autonomously?
Not in HARNEXA deployments. Financial or order-submission boundaries require explicit human approval unless a signed client scope defines otherwise.
What should a merchant prepare before ACP?
Structured product data, inventory and policy facts, acceptance rules, payment scope, fulfilment ownership, support ownership, and audit evidence.
Need these definitions mapped to a live commerce workflow, agent estate, or protocol-readiness path?
Book diagnostic sprint