Account-resolved Apostra tools and direct, per-seller AdCP endpoints for agentic advertising.
Agents starting without a credential: begin with auth.md and the zero-touch activation contract. Anonymous registration requires no email or human step, issues the canonical interchange:read scope, and starts with a zero-spend allowance. Interactive clients can instead use OAuth; existing organizations can use an API key.
Portable, versioned workflows teach compatible agents how to use Apostra safely. Developers can start with Build with Apostra. Buyer workflows cover account readiness, campaign setup and buying, event-source setup, campaign management, Creative Session generation, and local tag-sheet inspection. Seller administrators can follow the OpenAI publication workflow. The catalog also includes direct seller buying and sales-agent validation. Read the machine-readable catalog for current immutable versions.
The account-resolved Apostra MCP API. One endpoint serves every authenticated Buyer and Seller Account; the active account, permissions, capabilities, and feature availability determine the nouns and tools returned by tools/list. Use V2 REST for deterministic HTTP integrations and operations that V3 does not expose.
get_status – Resolve the active account, blockers, and next actionssearch and get – Read the account's visible nounssave_<noun> – Use only the typed writes advertised for the active accountEach published Seller can advertise a one-seller AdCP endpoint in its listing. The card selects the Seller protocol door; Apostra remains the agent of record and anchors buyer identity, contract, governance, reporting, and ledger evidence. Follow the card's verified actions[kind=adcp].url; do not substitute the V3 product API.
Stable persona-scoped API for buyer integrations.
Stable persona-scoped API for storefront integrations.