Developer documentation
Build an approval-first marketing workflow.
The AICMOHQ API is the HTTP surface used by the CLI. Use it to authenticate a CLI session, inspect your account, run strategy agents, and manage drafts and publishing.
Download the OpenAPI 3.0 document or use the raw llms.txt context file.
Base URL and authentication
Production requests use https://app.aicmohq.com/api/v1. Start with the unauthenticated device flow:
POST /api/v1/auth/device
> { "scopes": ["queue:read", "queue:write"] }
POST /api/v1/auth/device/token
> { "device_code": "..." } The first response includes a browser verification URL. The user must approve the request in the browser, and approval requires an active subscription. Poll the token endpoint using the returned device_code; pending and terminal states follow RFC 8628-style error names.
Send the resulting token as Authorization: Bearer <token>. Agent tokens are scoped. Supported scopes are queue:read, queue:write, publish, connections:read, and strategy:run.
Available API areas
/api/v1/me— authenticated account, plan, token type, and scopes./api/v1/connections— list platform connections withconnections:read; secrets are not returned./api/v1/queue— list and create drafts withqueue:readorqueue:write./api/v1/queue/{id}/approve— approve a draft before publishing./api/v1/queue/{id}/publish— publish an approved item withpublish./api/v1/scout,/api/v1/write, and/api/v1/strategy/run— run agent workflows withstrategy:run./api/v1/tokens— create, list, and revoke scoped agent tokens.
Important limits
- Authentication and agent actions require an active subscription where indicated by the API.
- Credits and rate limits apply to agent actions.
- Tokens never bypass human approval. Publishing is not automatic merely because a token has the
publishscope. - The public website health endpoint is
GET https://aicmohq.com/api/health. The authenticated API and device-flow endpoints run athttps://app.aicmohq.com; all other documented API operations require bearer authentication.
For supported CLI setup, see the CLI guide; for MCP clients, see MCP instructions. For changes to this contract, treat openapi.json as the source of truth. Agents that need a compact site overview can use llms.txt.