Summary
In this reference model, OACP artifacts carry source references, timestamps, TTL, issuer, scope, hashes, revocation posture, risk tier, and blocked capabilities so a buyer agent can decide whether to answer, refresh, prepare, or refuse.
Artifact Families
The repository schema describes merchant profile, seller agent card, connector evidence, catalog, price, inventory, policy, public discovery state, mandate-capability evidence, protocol adapter profile, and request/status artifact families.
Cache Rules
The intended cache scope is buyer agent, seller agent, tenant, and merchant. A deployment should answer non-binding questions only when TTL and revocation checks pass, and should fail closed for expired, revoked, stale, mismatched, private, raw, or executable records.
What Artifacts Do Not Do
Artifacts do not create checkout sessions, orders, payments, refunds, returns, holds, shipping labels, or mandates. They provide trusted evidence and compatibility mappings. Execution remains with merchant, provider, bank, POS, or support systems.
Topics
Ready to try it?
Explore the public playground, or create an account to evaluate an agent with your own approved data and controls.