learn

Agentic commerce

What happens when machines need to buy API calls, pay for content access, or settle charges with other agents. Covers policy discovery, pricing headers, payment rails, and signed records.
2 min read

Key takeaways

  • Agentic commerce enables AI agents to autonomously buy, sell, and transact.
  • Needs machine-readable pricing, programmatic payments, and verifiable records.
  • Different from traditional e-commerce: no human in the loop per transaction.

Definition

Agentic commerce is what happens when AI agents need to spend money. An agent calls an API, the API returns a price, the agent pays, and the API delivers the resource with a signed record. No human clicks "Buy."

This is already happening: agents calling translation APIs, purchasing inference credits, licensing content for RAG pipelines. The infrastructure problem is making these transactions verifiable and auditable without requiring each agent to have a pre-negotiated account with each service.

How it works

The flow has five steps. Each one requires protocol support:

  1. Policy discovery. Agents discover available services and their terms via machine-readable files like peac.txt.
  2. Pricing negotiation. Services advertise pricing in HTTP headers; agents evaluate and select based on budget constraints.
  3. Payment execution. Agents make programmatic payments via HTTP 402, cryptocurrency, or pre-authorized billing.
  4. Record generation. Every transaction produces a cryptographically signed record for audit and partner review.
  5. Verification. Records can be verified offline using Ed25519 signatures. No callback to the issuer required.

Key components

A complete agentic commerce stack includes:

  • Machine-readable pricing. Prices in HTTP headers or structured files. Not HTML meant for humans.
  • Programmatic payments. Payment rails agents can invoke without human approval: HTTP 402, stablecoins, pre-auth billing.
  • Verifiable records. Cryptographic proof for billing, compliance, and review.
  • Budget constraints. Guardrails limiting autonomous spend (you set the ceiling, agent stays under it).

Use cases

API consumption

Agents pay for API calls on the fly. Weather data, translation, image generation. No credit pre-purchase required: they pay per call as they execute tasks.

Content licensing

Per-use payments to creators for training data, stock images, reference materials. Attribution included.

Getting started

To enable agentic commerce for your service or agent, Originary provides infrastructure and tools built on open protocols:

related