Skip to main content
Apostra helps you plan, run, and understand advertising across sellers from one connected place. Use it directly, ask an assistant to help, automate repeatable work, or build it into your own product. Here to run advertising in the application or with Claude/Cowork? Start with Manage ads. To build software, follow this V3 developer journey and the installation quickstart. You do not need to know that you are building an “advertising agent” or which advertising systems you need. Start with the job: find places to advertise, compare options, prepare and run a campaign, bring in customer or creative data, or get results into a report. Apostra keeps the advertising records and carries out supported work across connected sellers and providers. For developers, Apostra provides one account-aware MCP and API connection for those jobs. Your application supplies the interface, business data, and the decisions it needs to own. For example, an agent can turn a brief into a draft campaign, request proposals from eligible sellers, compare the returned offers, stage a media buy, and ask the customer to approve launch. A reporting service can read that campaign’s delivery without running an agent at all.

​
What you can build

​
Why connect through Apostra’s MCP

The MCP endpoint exposes tools an agent can discover and call. Apostra supplies the advertising system behind those tools: account permissions, seller connections, shared campaign records, proposal requests, transaction execution, and reporting. You do not need to maintain a separate buying adapter for each supported seller underneath that integration. Connect to one account-resolved endpoint:
Call get_status to see the active account and its readiness. Use tools/list for the current input schemas. Buyer and seller work use the same connection; authorization still follows the selected account and each resource. MCP is a good fit when a coding agent or model needs to discover capabilities and choose its next action. Use the v3 HTTP API when your application needs fixed, typed requests for the public operation catalogue. Both operate on the same account data and enforce the same operation permissions, but they publish separate input contracts and HTTP can be stricter. Some administration, ingestion, and lifecycle APIs remain on v2.
Apostra’s API, sign-in, and documentation URLs currently use the apostra.com domain. Use the URLs shown here; the product name does not change an endpoint.

​
Choose what you want to own

Use Apostra’s application and an authorized assistant for a human-guided workflow. Build your own loop when your product needs to control the interface, schedule, business decisions, or recovery. A hybrid application keeps durable checkpoints in code and uses an agent for decisions such as interpreting a brief or comparing proposals. Apostra remains the system of record for its advertisers, campaigns, creatives, media buys, and reporting in each approach. Hosting an arbitrary customer-defined agent or workflow is not currently a public v3 capability.

Choose your operating loop

Decide which decisions, data, and runtime your application should own.

Connect in five minutes

Connect an MCP client, sign in, and prove account access with a read.

Call the HTTP API

Use fixed v3 routes and generate a typed client from OpenAPI 3.1.

Build an agent

Move from a seller-discovery prototype to a durable buying workflow.

Bring data in

Choose the right route for events, creative assets, inventory, and materials.

Build a reporting pipeline

Query delivery, export it, and schedule reliable downstream processing.

Connect and test a seller

Configure seller inventory and exercise the no-spend own-supply workflow.

​
Availability and existing integrations

Every authenticated Buyer and Seller Account can connect to v3. A tool’s availability and permitted resources still depend on the account, permissions, and any feature-specific rollout. Organisation accounts currently have shared navigation tools rather than a domain catalog. The v3 HTTP and MCP contracts do not replace v2 REST, and v2 is not deprecated. Existing integrations need no migration to keep working. Some administration, event ingestion, export, and lifecycle operations continue to use v2. Check the capability limits before committing to a production workflow, and use the tool reference alongside the schemas returned by your connection.