Turn agent intent into a governed buy.
Let buyer agents discover products, create media buys and sync creatives. Give operators a say in what gets activated.
Coming soon. Request early access.
A buying request follows a controlled path.
Discover what can be bought.
An agent reads capabilities, product information and creative formats through the AdCP surface.
Create a buy within bounds.
Authenticated requests map into campaigns and line items, subject to principal limits and configured approval thresholds.
Manage the buy over time.
Sync creatives, update the buy and retrieve delivery information through the same protocol surface.
Give automation a clear operating contract.
Scope each principal.
API-key scopes separate read, write and administrative access. Principal limits constrain the budgets an agent can request.
Make retries predictable.
Mutating tasks require an idempotency key, allowing a repeated request to replay its result instead of creating another buy.
Keep an operator in the loop.
Buys above a configured approval threshold can remain pending. Mutations leave an audit record of the principal and outcome.
Which role does pico DSP play in AdCP?
pico DSP exposes the seller role on the AdCP wire. Buyer agents create media buys that become campaigns and line items in the RTB engine. The server includes an end-to-end test that creates an AdCP buy over MCP and wins an auction with it.
Switch to a modern,
affordable DSP.
Buy programmatically or go direct, with agentic workflows and validation included.