← Action Library
01 Reference workflow · Acquire

Procurement Agent Purchase

An authorized procurement agent discovers an eligible product, validates the commercial rules, and creates a governed order without scraping a storefront.

Initiated byExternal buying agent
Intended outcome

The order is recorded against the represented account and the agent receives the documented payment or subscription actions required to complete fulfillment.

CatalogOrderingPaymentSubscriptionsAudit
Transaction path

From intent to completed outcome.

A buyer delegates a purchase objective and spending limit to an AI procurement agent.

01 · Discover

Resolve the commercial catalog

The agent retrieves products, prices, compatibility, and availability through a structured contract.

02 · Verify

Check authority and fit

PeakCommerce applies the API key scope plus catalog, account, pricing, and discount policies.

03 · Execute

Create the governed order

The order records the approved products, quantity, price, currency, and represented account with retry protection.

04 · Continue

Complete the required actions

The response directs the caller to the documented subscription or payment action required for the purchase.

Commerce contract

One action. Explicit context and control.

Context required

  • Buyer identity and represented account
  • Machine-readable product and pricing data
  • Currency and payment authority
  • Product compatibility and account eligibility

Guardrails applied

  • Tenant-scoped commerce credentials
  • Catalog, pricing, and discount policy
  • Idempotency and duplicate-order protection
  • Explicit handling of required next actions
REFERENCE REQUEST
POST /api/v1/orders
Idempotency-Key: req_4f8a
{
  "organizationId": "org_2048",
  "items": [{
    "productId": "prod_growth_annual",
    "quantity": 1,
    "priceCents": 480000
  }],
  "totalCents": 480000,
  "currency": "USD"
}
PeakCommerce result
201 Created
{
  "id": "ord_8c4d2e",
  "status": "confirmed",
  "nextActions": ["create_subscription"]
}

Availability and downstream effects depend on the billing and product integrations configured for the tenant.

Take the next step

Map this action to your commerce stack.

Start with this workflow already selected, then identify the billing, customer, and product systems involved in executing it.