Kitmo exposes a versioned Distribution API and an MCP endpoint for integrations that help a creator prepare and review social publishing work. Both connect to one Kitmo workspace through an API key. They do not bypass the creator's approval step.
Get started
Create an API key in the Kitmo workspace, then send it with each REST request as Authorization: Bearer kitmo_.... Read requests need the distribution:read scope. Creating content, variants, or plans needs distribution:write. Keep keys in a secret store and never expose them in browser code.
Start from the OpenAPI 3.1 document. It describes the typed request and response bodies for connected accounts, source content, variants, distribution plans, queue items, delivery status, and analytics snapshots. A public health check is available at/api/health.
Approval model
An agent can prepare content and create a distribution plan, but a new plan begins as proposed. Review it with the creator, then explicitly update the plan to approved before scheduling. This keeps an automated assistant useful without giving it silent publishing authority.
MCP
Connect an MCP client to https://kitmo.app/api/mcp with the same Bearer API key. The server can list accounts, create content and channel variants, make a reviewable plan, and report delivery status. Use the REST API when you need the published OpenAPI contract.
Errors
API errors are JSON. Check error.code first, showerror.message to a person when useful, and useerror.hint to choose the next action. An unknown API URL returns a JSON 404 pointing to the OpenAPI document.