Developer docs
Build on Automate10x
Every action in the app is callable over a public REST API and a first-class MCP server. Use it from your scripts, from Claude / Cursor / any MCP agent, or from n8n — the same primitives, nothing held back.
Quick start
- Base URL:
https://automate10x.com/api/v2 - Auth:
Authorization: Bearer sk_… - Get a key: Settings → API (create / rotate, with optional scopes)
curl -X POST https://automate10x.com/api/v2/posts \
-H "authorization: Bearer sk_•••" \
-H "content-type: application/json" \
-d '{
"text": "We shipped agent-ready publishing.",
"targets": [{ "accountId": "<id>" }],
"schedule": { "mode": "now" }
}'REST API
Multi-destination publish, async jobs, idempotent writes, dry-run validation, per-key rate limits, a capability manifest, media uploads, research sources, visuals, and signed webhooks.
MCP server
A first-class MCP surface (tools, resources, prompts) so Claude, Cursor, and any MCP-aware agent can publish, research, and schedule directly. Endpoint:
https://automate10x.com/mcpSDKs
Dependency-free clients that mirror the REST surface (publish, dry-run, job polling, sources, visuals, webhooks):
Or generate your own client from the OpenAPI spec.
n8n
A community node + an Automate10x Trigger (signed webhooks) for no-code automations.
npm install n8n-nodes-automate10xFor AI agents
Machine-readable summaries an agent can pull to learn the API:
llms.txt · llms-full.txt (full surface + capability table)
Webhooks
Subscribe a URL to signed events (post.published, post.failed, visual.ready, …). Deliveries carry a Stripe-style X-Automate10x-Signature you can verify.
See the reference for /v2/webhooks.
Already signed in? Your key and copy-paste client setup live in Settings → API.