DistributionOS
Get API Now
API/MCP docs

Connect Codex or Claude Code to DistributionOS.

These docs cover the current setup path: app-scoped API keys, Brain Doc context, SEO brief handoffs, shipped URL reporting, and analytics setup.

Getting started

  1. 1. Join now and create or select an app.
  2. 2. Create or improve the Brain Doc so Codex or Claude Code has positioning and product context.
  3. 3. Create a write-scoped API key from the dashboard.
  4. 4. Add the key and app ID to Codex or Claude Code.
  5. 5. Ask the agent to read context, create a brief or handoff artifact, ship the work, and report what shipped.

Authentication

API keys use bearer authentication and are scoped to a single app. The full key is shown once, then only the last four characters are visible in the dashboard.

Authorization: Bearer dos_live_...
Content-Type: application/json

read

Use for context-only agent workflows.

write

Use for normal artifact creation and reporting.

admin

Use sparingly for automation that manages access.

MCP setup

Codex and Claude Code are the currently tested and supported MCP clients. The supported agent receives an app ID and authentication, then reads DistributionOS context before creating or reporting marketing work. Other MCP clients remain untested and are not currently supported.

# Agent environment
DISTRIBUTION_OS_API_KEY=dos_live_...
DISTRIBUTION_OS_APP_ID=app_...

# MCP server name
distribution-os

Plans and credits

Monthly

$50/mo/app

Every feature, unlimited tasks and handoffs, 50 media credits, 5 social profiles, 50 fresh research runs, and 250 AI visibility checks per month.

Yearly

$500/yr/app

The same full access and monthly allowances. Save $100 compared with monthly billing.

Hosted article generation is disabled. DistributionOS provides context, research, briefs, media credits, and reporting; Codex or Claude Code writes, edits, publishes, and reports the shipped URL. Hosted images for social, landing, launch, blog/page, and video reference assets can use included media credits first, then account-shared top-up credits.

AI Visibility readiness audits use the existing paid-plan daily audit allowance and page cap; they do not consume the 100/500 monthly monitored-question checks. Readiness, monitored answers, crawler activity, referrals, and conversions remain separate evidence.

Current resources

Brain Doc

GET /api/v1/apps/{appId}/brain

Read positioning and marketing memory.

Brain patch

POST /api/v1/apps/{appId}/brain/patch

Update structured Brain Doc context.

Brief handoff

POST /api/v1/apps/{appId}/artifacts

Create a content_brief or distribution handoff for your agent.

Report implementation

POST /api/v1/apps/{appId}/artifacts/{artifactId}/report-implementation

Attach the shipped URL and verification details.

API keys

Dashboard API Keys page

Create, reveal once, list, and revoke keys.

Troubleshooting

  • Invalid key: revoke it, create a new one, and update your local agent config.
  • App mismatch: make sure the API key and app ID belong to the same app.
  • Payment or access paused: API/MCP usage should stop until account access is restored.
  • No useful output: improve the Brain Doc before asking the agent to create briefs or distribution work.

Need a key?

Create an app-scoped key in the dashboard, then come back here with your app ID.

Get API Now