Skip to main content

OACP Authority Overview

This is the canonical Grantex OACP page. The canonical end-to-end flow starts here and links to the AgenticOrg runtime guide from the integration page. OACP is the trust and interoperability layer for agentic commerce. Grantex owns the protocol, trust, policy, artifact, verification, and protocol-adapter authority. AgenticOrg owns the buyer and seller AI-agent runtime, Shopify connector runtime, buyer sessions, channel bridges, OACP cache, and provider-owned mandate capability verification. Merchant systems such as Shopify remain the source of record. Pine Labs Plural/P3P and other provider rails own mandate and payment execution. Grantex must not become a toll booth for every buyer and seller interaction.

Four-Party Architecture

What Grantex Owns

AreaGrantex role
Trust authorityIssues or refuses canonical internal OACP artifacts.
Policy governanceDefines artifact TTL, freshness, source, revocation, risk, and blocked-capability rules.
Artifact verificationVerifies issuer, scope, payload hash, signature, TTL, and public-safe payload constraints.
Protocol adaptersGoverns compatibility mappings from canonical OACP artifacts to Schema.org, UCP-style, ACP-style, AP2-style, A2A, MCP, and OpenAPI payloads.
Integration boundaryAccepts allowlisted AgenticOrg authority requests with public-safe connector evidence.

What Grantex Does Not Own

Grantex does not own Shopify runtime credentials, merchant onboarding UX, buyer sessions, WhatsApp or Telegram webhooks, MCP/OpenAPI client sessions, AgenticOrg artifact cache storage, final checkout execution, order creation, stock holds, mandate setup, payment capture, refund execution, or provider settlement.

Runtime Reality

StatusReality
Implemented runtimePOST /v1/commerce/oacp/c6z/authority-requests, internal artifact issuance, verifier helpers, adapter preview helpers, and OACP guard tests.
Implemented docs onlyHistorical Commerce V1 planning and C6 audit/review reports remain useful as internal history but are superseded for the public OACP split.
Requires external credentials or approvalAgenticOrg service token and tenant allowlist, merchant Shopify access, channel approvals, and provider rail approval.
MissingPublic standards program approval, universal channel launch, and broad payment/order execution.
Stale/confusing documentationOlder Commerce V1 pages that frame Grantex as the merchant control plane are historical; use this OACP group for the current authority narrative.

Artifact Families

Grantex currently issues or refuses these internal OACP families for the C6Z AgenticOrg runtime path: merchant_profile, seller_agent_card, connector_evidence, catalog_snapshot, offer_price_snapshot, inventory_snapshot, policy_scope, public_discovery_state, mandate_capability, protocol_adapter, and authority_request_status.

Buyer-Safe Rule

AgenticOrg may continue non-binding product questions and comparison from valid cached artifacts. A request that would commit the buyer, create a checkout, create a mandate, capture payment, reserve inventory, create an order, refund, return, or ship must use the approved provider, merchant, and channel path. OACP artifacts do not invent success.