The agent channel

AI shopping agents can buy from your shop over the open UCP standard, and an agent channel is your set of controls for them. This guide is only a pointer: the channel's controls are ordinary operations of this API, documented in the reference, while the calls an agent platform makes are a separate channel that is not part of the API-key surface.

What it is

An agent channel is your shop’s set of controls for AI shopping agents buying over the open UCP standard — which store’s stock and prices they buy from, which collections they may see (nothing until you choose), an optional agent-only price list, whether discount codes work, a spending cap, how orders are fulfilled and where you ship (your own flat rates), which agent platforms may transact (none until you list them), consent defaults, your return and warranty policy words, and how long a checkout stays open. The engine mints and rotates the channel’s signing key. Exactly one channel per organization.

Your side, in this reference

The channel's own operations — creating it, publishing it, pausing and resuming it, retiring it — are in the Agent channel family, each with a request and a response to copy. An API key whose scope allows them can manage a channel exactly as an owner would in the office.

The other side

What an agent platform calls to browse, price and buy is the platform's own channel, opened by your channel's controls and secured by its signing keys. It is not reachable with an API key and is not documented here; the full schema at /schema.graphql lists those operations as reserved for the platform.