Agentic Commerce V1

Consent-first checkout control for commerce agents.

Grantex 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.

Internal sandbox ready Hosted smoke verified Production discovery disabled Live payments blocked Live Plural blocked
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 staged, not implied

LayerStatusMeaning
Internal sandboxReadySynthetic data and mock-provider paths exist for controlled validation.
Temporary smokeVerifiedOption A and hosted AgenticOrg smoke evidence used temporary resources and scrubbed reports.
Production discoveryDisabled/fail-closedRead-only discovery requires a later approved proposal.
Live checkout/paymentsBlockedLegal, compliance, security, operations, and provider gates remain required.
Live PluralBlockedNo current evidence enables live Plural or live provider credentials.
Local testsInternal sandbox
Option A smokeTemporary Grantex service
AgenticOrg evalGrantex-only path
Hosted API smokeMCP/A2A discovery
Read-only discoveryHuman proposal required
Live paymentsBlocked

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 education, not enablement.

Production Commerce V1 discovery, live checkout, live payments, live Plural, external pilot readiness, and provider certification remain blocked until explicit human gates approve them.

Read the Commerce V1 docs