Discover the catalog
Query products, plans, pricing dimensions, entitlement bundles, and compatibility metadata through structured APIs.
The agent evaluates current commercial data without scraping a page or interpreting UI markup.
Agentic Commerce Platform
The commerce primitives AI agents need — structured APIs, machine-readable catalogs, scoped authentication, and programmatic transaction execution as a first-class capability.
< 200ms
API response time for agent-driven catalog and transaction calls
Trusted by Leading Companies
"
PeakCommerce gave our procurement agents a clean, structured commerce surface to call against. We replaced months of bespoke integration work with a few authenticated API calls.
DM
Devon Mehta
Director of Platform Engineering, Northwind AI
A commerce surface designed for machines
Every product, price, entitlement, and transaction action is exposed as a typed, idempotent endpoint — so agents can act with the same fidelity as a human checkout.
peakcommerce.app
Agent Request
POST /v1/transactions/execute
Authenticated
// Authorization: Bearer agt_... // Idempotency-Key: req_4f8a... { "agent_id": "aurora-procurement-01", "customer_id": "cus_acme_corp", "action": "upgrade_subscription", "target_plan": "growth_annual", "line_items": [ { "sku": "seats","quantity": 25 } ], "constraints": { "max_amount_usd": 5000, "verify_entitlements": true } }
PeakCommerce Response
200 OK · 184ms
Provisioned
{ "transaction_id": "txn_8c4d2e...", "status": "completed", "amount_charged_usd": 3840.00, "proration_credit_usd": 412.50, "entitlements": { "plan": "growth_annual", "seats_total": 75, "effective_at": "2026-04-30T17:24:08Z" }, "audit": { "agent_scope": "upgrade:within_budget", "policy_checks": "passed" } }
From agent intent to provisioned transaction
The platform handles authentication, catalog discovery, policy verification, and execution — exposing each step as a discrete API call.
1
Authenticate
Agents present scoped credentials defining the actions, products, and budgets they are allowed to transact against.
2
Discover
Query the structured catalog for plans, entitlement bundles, pricing dimensions, and compatibility metadata.
3
Verify
Programmatically check entitlements, eligibility, and policy constraints before committing the transaction.
4
Execute
Submit an idempotent transaction call — payment, billing, and entitlement provisioning return as one structured response.
An agent buying through the platform
A walkthrough of how an autonomous procurement agent uses the agentic commerce APIs end to end.
Aurora — Procurement Agent
Autonomous Buying Agent (Enterprise IT)
"Aurora is configured with a scoped API key allowing seat upgrades up to $5,000 across the IT-owned SaaS portfolio. Usage signals indicate the team is at seat capacity."
1
Authenticate with a scoped agent token
Aurora presents an `agt_*` token whose scope explicitly permits `upgrade:within_budget` actions on the seats SKU. The platform binds every downstream call to that scope and writes it to the audit trail.
2
Resolve the catalog programmatically
A single GET to `/v1/catalog` returns plans, pricing dimensions, entitlement bundles, and compatibility rules in machine-readable JSON — no scraping, no UI parsing.
3
Verify entitlements and policy fit
Aurora calls `/v1/entitlements/verify` to confirm the proposed upgrade satisfies the customer's compliance posture and stays under the $5,000 ceiling baked into the token scope.
4
Execute the transaction with one idempotent call
POST `/v1/transactions/execute` returns in under 200ms with the provisioned entitlements, prorated charges, and a full audit envelope — all a downstream agent needs to confirm the buy.
Built into the platform your agents already speak to
Agentic commerce isn't a side product — it shares the same catalog, entitlements, and billing layer as every other PeakCommerce surface.
Structured Commerce APIs
Versioned, typed REST endpoints for catalog, pricing, and transactions
Machine-Readable Catalog
Plans, entitlements, and pricing dimensions exposed as structured JSON
PeakCommerce
Agent Auth & Scopes
Scoped API keys and OAuth tokens with per-action permission boundaries
Webhooks & Events
Stream transaction, entitlement, and audit events into your agent runtime
An API-first commerce capability
API-first
Architecture
Every capability programmable
Scoped
Agent authentication
Per-action permission boundaries
Idempotent
Transaction endpoints
Safe retries for autonomous callers
Audited
Every agent action
Full structured audit envelope
Related capabilities
Evaluate what an agent can discover, verify, and execute.
Agentic commerce requires more than a chatbot or purchase link. The agent needs structured catalog data, bounded authority, policy checks, safe execution, and a machine-readable result.
Verify authority and fit
Check customer state, entitlements, eligibility, product compatibility, budget, and permitted actions before commitment.
Invalid or unauthorized transactions stop before billing or provisioning changes occur.
Execute a transaction
Submit a scoped, idempotent purchase, upgrade, add-on, or account-change request against the same commerce contract used by human surfaces.
Billing, payment, entitlement, provisioning, CRM, and audit outcomes return as one structured result.
Observe every action
Stream transaction, entitlement, policy, and audit events into the systems responsible for monitoring and reconciliation.
Teams can attribute, review, and reconcile autonomous activity alongside every other channel.
What your team controls
Agent scopePermitted products, transaction types, accounts, budgets, and confirmation requirements.
Catalog contractStructured products, prices, entitlements, compatibility, and commercial metadata.
Policy checksEligibility, current account state, entitlement fit, and business guardrails before execution.
Audit envelopeActor identity, permission scope, request id, decision path, result, and downstream events.
Implementation path
ModelDefine the catalog, transaction actions, account context, and entitlement outcomes agents need.
AuthorizeCreate scopes, budget boundaries, confirmation rules, and policy checks for each agent use case.
IntegrateConnect billing or built-in ordering, payment, CRM, provisioning, and event consumers.
ValidateTest success, rejection, retry, duplicate-request, and downstream reconciliation paths.
Evaluate the implementation
See the role-specific path
Product & Engineering →Architecture, API contracts, permissions, events, and system ownership.Revenue Operations →Catalog governance, commercial rules, approvals, and agent transaction boundaries.Digital Commerce →Catalog discovery, autonomous buying paths, and channel-level transaction attribution.