Canonical Artifact
OACP artifacts remain the canonical trust input. Adapter payloads are deterministic views derived from source, freshness, policy, and capability fields.
Mappings
AgenticOrg can emit Schema.org, ACP-style, AP2-style, A2A, MCP, and OpenAPI compatibility payloads from verified cached artifacts. For UCP it renders the merchant's business profile in the published shape, and the UCP and ACP checkout routes are separate surfaces behind switches that default to off.
Boundary
Compatibility mapping is not official external approval. Public claims require separate partner review and evidence.
Frequently Asked Questions
Does an adapter create checkout?
No. Adapter payloads are metadata and buyer-safe compatibility views. Checkout sessions exist only on the UCP and ACP routes, which are off by default.
Can unsupported fields be guessed?
No. Unsupported execution fields are omitted or blocked.
Topics
Ready to try it?
Evaluate the workflow with your own approved data, integrations, review gates, and success criteria.
Explore OACP