OpenCharts REST API

Authentication

Every request authenticates with an OpenCharts API key passed as a Bearer token. Create and manage keys in the Developers hub. Keys are the same oc_ keys the MCP server accepts, and carry read, write, and ai scopes.

Quick start

# 1. Create a key in the Developers hub, then:
curl https://www.opencharts.com/api/v1/account \
  -H "Authorization: Bearer oc_your_api_key"

# Generate an image (synchronous)
curl -X POST https://www.opencharts.com/api/v1/images \
  -H "Authorization: Bearer oc_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{"prompt":"a neon fox, flat vector","aspectRatio":"1:1"}'

# Start a video job, then poll it
curl -X POST https://www.opencharts.com/api/v1/videos \
  -H "Authorization: Bearer oc_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{"prompt":"slow dolly over a misty forest at dawn"}'
# → { "jobId": "vid_abc123", "status": "queued", "pollUrl": "/api/v1/jobs/vid_abc123" }

curl https://www.opencharts.com/api/v1/jobs/vid_abc123 \
  -H "Authorization: Bearer oc_your_api_key"

Scopes

Chat & conversations

POST /api/v1/chat runs a Theo turn with tools — it streams the same UI-message SSE the in-app client consumes (point useChat from @ai-sdk/react at it), or returns the assembled message + artifacts with stream: false. Launch modes are fast and think; Theo can create flowcharts, whiteboards, notes, presentations, sheets, boards, documents, images, video, and music from a prompt. Async artifacts carry an apiJobId pollable at the jobs endpoint below. Threads persist as normal conversations (they appear in your in-app sidebar) and are managed via /api/v1/conversations (list / create / get / update / delete + /messages). You can also extract a flowchart from an uploaded PDF, PPTX, or image via POST /api/v1/extract-flowchart.

Async jobs

Long-running operations — video, music, code builds, and deep research — return a job envelope immediately with a type-prefixed jobId (vid_, song_, code_, res_). Poll GET /api/v1/jobs/{jobId} until status is complete or failed — or register a webhook and skip polling entirely.

Webhooks

Register HTTPS endpoints to be notified when jobs finish instead of polling. Manage them in the Developers hub or via /api/v1/webhooks. Each delivery is signed with your webhook secret (HMAC), retried on failure, and logged. Events include video.completed, song.completed, code_build.completed, research.completed (and their .failed counterparts), plus project and team events.

Rate limits & plans

Usage & audit log

Reference