HomePART III · ChannelForge
CHAPTER 18 · CHANNELFORGE
API, webhooks and agents
Everything a member can do in the app, a program can do through the API — which is how agencies, automation tools and AI agents put ChannelForge to work.
- REST API (OpenAPI 3, 41 route files): channels, projects, episodes, films, jobs, quotes, insights, events, webhooks, style, topic imports, finished-video imports, publishing health; idempotency keys; a quote endpoint that says what a job will cost before it is queued — a Blender episode included; a 14-day request log per API key.
- Signed webhooks for job, episode, post and billing events, retried with backoff, delivered without redirects.
- MCP server: 30 tools an AI agent (Claude, for example) can call — 'generate episodes for this channel, but spend no more than 300 credits' — each respecting the member's project and channel access; the in-app 'Ask ChannelForge' assistant works through the same tools.
- Integrations: n8n, Make and Zapier connectors speak the same API.
Example: queue one episode with a credit ceiling#
POST /api/v1/episodes/generate Authorization: Bearer <api key> {"channel_id": "ch_…", "max_credits": 231, "count": 1} → 202 {"queued": [{"job_id": "job_…", "credits_held": 231}], …}