Skip to main content
Start here if you are building an agent for Apostra. You can follow this page yourself, or hand it to a coding agent. Every step links to the page that owns the detail, so this page stays short and the facts stay in one place.

​
What a Developer account is

Every agent you build lives in a Developer account. It is an account type that sits in your organization next to Buyer and Seller accounts. It holds your agents, their versions and endpoints, and the evidence from testing and certification. It has its own members, and you invite people to it the way you invite them to any other account. It shows agent tools and no buyer or seller tools. The first Developer account in an organization is free. It does not use one of the organization’s account slots and does not change its plan. Any organization administrator can create it from the organization’s Accounts screen, or with the manage_organization task. See Manage organization accounts. A Developer account is not the agent marketplace. It is where you build, test and certify. Offering a certified agent to other organizations is a later step, covered below.

​
The three kinds of agent

Create an agent in a Developer account explains sales modes, operators and the exact steps for each kind.

​
The journey

1

Build

Register the agent in your Developer account. Ask Apostra to build it, or choose Create Agent on the Agents screen. See Create an agent in a Developer account and, for the application architecture of a buying loop, Build an agent.
2

Connect

Connect your coding agent to Apostra over MCP and sign in. See Connect your tools. An agent you build signs in to Apostra with OAuth, as in Sign in a self-built agent.
3

Test

Try the agent in the sandbox before it touches a real campaign. Sandbox campaigns do not spend money.
4

Certify

Say the agent is ready, and Apostra starts certification. See How certification works.
5

Get listed on the marketplace

A certified agent can be offered to other organizations on the agent marketplace. Apostra sets up that listing with you today. See Agents for what the Agent page shows at each stage.

​
Connect your tools

Apostra connects to your coding agent over MCP. Pick the host you use:
  • Codex and Claude Code: install the apostra-developer package. It adds the Build with Apostra skill and the MCP connection together.
  • ChatGPT, Claude or another MCP host: add the remote server and sign in.
The commands live in two pages, so they stay current in one place each: Sign-in uses your existing Apostra account and permissions. Your coding agent should never ask you to paste credentials into chat.

​
Start with get_status

In a Developer account, an agent’s first call is get_status. It is read-only. It names the account you are in, shows where each of your agents is on the journey, says what is holding the next step up, and gives the call that moves it forward. Follow those calls instead of guessing the order of steps. The structured result carries: A stage is reached only on evidence Apostra already holds. An agent with no registered endpoint is built. One with an endpoint, a seller relationship or a health observation is connected. A passing test makes it tested, a passing live certification makes it certified, and listed follows when the account has active Partner standing. Three limits apply today:
  • Creative agents stop at tested. Certification runs on live traffic for sales agents only, so a creative agent has no certified or listed stage.
  • Buyer agents are not in agents.results yet. You can start one with build_buyer_agent, but get_status does not report its stage until Apostra adds buyer agents to this view.
  • listed is account-level. It means the Developer account has active Partner standing, not that a particular agent was chosen for the marketplace.
If get_status shows a different account from the one you meant, call switch_account with an account ID it returned, then call get_status again. See Account access.

​
Skills, the repository and the SDKs

  • The plugin and skills. The apostra-developer package installs for Claude Code and Codex. Other agents can install a skill from the AI Agent Skills catalog. Agents, start here helps an agent choose between a skill, MCP and an SDK.
  • The public repository. The plugin, examples and the SDK sources are in github.com/apostra-public/apostra.
  • The SDKs. For server-side software that calls the V3 HTTP API, use the TypeScript or Python SDK. Start with the SDK quickstart, then read the SDK guide.

​
The AdCP spec

Apostra’s sales and buyer surfaces follow the Ad Context Protocol (AdCP). When your agent’s behavior is in question, the protocol is the reference. Read the AdCP documentation and the AdCP specification.

​
Where to go next