A catalogue agents can actually read
Items, modifiers, prices, availability, and lead times published as structured data with stable identifiers. An agent does not have to scrape a menu page and guess.
Operations
Foundations
How it works
For developers
Agent Commerce
Agent Commerce exposes your catalogue, availability, and payment rails as a machine-readable interface, so an AI agent acting for a customer or a buyer can transact directly, under limits you set and against the same ledger as every other channel.
Items, modifiers, prices, availability, and lead times published as structured data with stable identifiers. An agent does not have to scrape a menu page and guess.
A customer or a buyer grants an agent a mandate: what it may buy, up to what amount, how often, and until when. The mandate is the credential, and it can be revoked mid-flight.
An agent order settles through the same processor and lands in the same deposit as a counter sale, so autonomous revenue is not a second set of books to reconcile.
Which agent, acting for whom, under which mandate, at what price, and what it was quoted. Written to the audit trail like any other privileged action.
The same interface lets your own agents restock from suppliers who publish it, so a par level breach can become a purchase order without a person in the loop.
Rate limits, quote expiry, and negotiated contract pricing per counterparty, so high-frequency agent traffic does not get treated like a human browsing session.
Agentic commerce is a transaction completed by an AI agent acting on a person or company's behalf, without that person opening an app or a website. The agent reads a machine-readable catalogue, checks availability, and pays under a mandate the principal granted it in advance.
An agent never holds an open payment credential. It holds a mandate that caps the amount per transaction and per period, restricts which categories it may buy, and expires. The mandate can be revoked at any time, including during an in-flight order.
No. If your catalogue and availability already live in Prinvia, the machine-readable interface is generated from them. You choose which items are agent-purchasable and what limits apply.
Identically to every other channel. An agent order settles through the same processor, posts to the same ledger, and appears in the same deposit, tagged with the agent and mandate that placed it.
Availability and lead time are part of the quote, and quotes expire. If stock moves between quote and commit the order is refused rather than accepted and cancelled later, because an agent retrying is cheaper than a human handling a refund.
Talk to us
Twenty minutes, your data, no slide deck.
Book a demoFree courses for managers, staff, and owners. Customer or not.
Browse the courses BuildCatalogue to settled order in six steps, under mandates you control.
Read the Agent Protocol