Agentic Commerce V1

Consent-first live commerce control for agents.

Grantex is live for the approved Shopify pilot merchant. It keeps consent, Commerce Passports, merchant policy, amount caps, audit, and provider boundaries in one control layer while agents use approved catalog, cart, consent, and payment-intent tools.

Production live pilot Shopify merchant imported OACP E2E verified Ops health green Plural UAT-compatible rails
1

Ground the cart

Agents search catalog, retrieve items, and check inventory through Grantex.

2

Ask for consent

Grantex creates a consent request and only approved scope proceeds.

3

Issue a passport

The Commerce Passport carries policy and amount limits as sensitive runtime material.

4

Control payment

Payment intents and checkout handoff stay provider-neutral and audit-visible.

Why Grantex sits between agents and payment providers

Consent boundary

Agents can prepare a purchase, but Grantex controls whether the requested action matches user consent and merchant policy.

Policy boundary

Amount caps, merchant status, trusted agent checks, and passport state are enforced before payment-affecting work proceeds.

Provider boundary

AgenticOrg commerce does not call Stripe, Plural, Pine, or provider credentials directly. Grantex owns the provider abstraction.

Readiness is live-pilot scoped

LayerStatusMeaning
Internal sandboxReadySynthetic data, mock-provider paths, and gated Plural sandbox adapter tests exist for controlled validation.
Temporary smokeVerifiedOption A and hosted AgenticOrg smoke evidence used temporary resources and scrubbed reports.
Shopify merchantLivemgx0n6-22.myshopify.com is imported as mch_shopify_mgx0n6_22 with 5 products and 5 variants.
Production discoveryLive pilotThe approved merchant profile is available through /.well-known/grantex-commerce.
Live-readiness gateCompleteRuntime acknowledgements are complete for the approved pilot; missing evidence still returns live_readiness_blocked.
Live checkout control planeEnabledConsent, Passport, policy, amount-cap, idempotency, webhook, reconciliation, and audit controls are deployed.
Plural adapterConfiguredWebhook intake is deployed. Current credentials authenticate against Plural UAT-compatible rails, so production Plural settlement is not claimed.
Local testsInternal sandbox
Option A smokeTemporary Grantex service
AgenticOrg evalGrantex-only path
Hosted API smokeMCP/A2A discovery
Shopify importReal merchant profile
Live gateEvidence complete
Plural settlementNot claimed

Start paths

Developers

Use the Commerce V1 developer guide and OpenAPI contract. Treat all auth, passport, idempotency, and provider material as runtime-sensitive.

Merchants and operators

Use the operator guide for catalog, policy, audit, webhook, emergency disable, and no-go checks.

Agent builders

Use Grantex Commerce REST/MCP only. AgenticOrg uses `grantex_commerce:*` tools and no direct provider credential path.

End users

The agent may help prepare a cart, but consent and policy checks determine whether checkout can proceed.

Use this page as the live-pilot map.

Production Commerce V1 is deployed for the approved Shopify merchant flow. Agents still use Grantex-only commerce surfaces, and Plural production settlement is not claimed until production Plural credentials authenticate against production rails.

Read the Commerce V1 docs