--- title: "MediaCopilot Developer Resources — API, OpenAPI Spec, MCP Server" description: "Developer resources for MediaCopilot: REST API base URL and OpenAPI 3.1 spec, Bearer token authentication, MCP Server, versioning and deprecation policy, and the machine-readable surface of mediacopilot.io." canonical: https://mediacopilot.io/developers language: en html_version: https://mediacopilot.io/developers --- # MediaCopilot developer resources The MediaCopilot API, the MCP Server, and the machine-readable surface of this website — every endpoint, spec and policy in one place. ## MediaCopilot API The MediaCopilot REST API gives programmatic access to the whole processing pipeline: assets and uploads, transcription, translation, dubbing and voice over, clip generation, reframing, smart search, metadata and publishing. - **Base URL:** `https://api.mediacopilot.cires21.ai` — every endpoint is prefixed with `/v1`. - **OpenAPI 3.1 description:** [https://api.mediacopilot.cires21.ai/openapi.json](https://api.mediacopilot.cires21.ai/openapi.json) — the machine-readable contract, with typed request and response schemas for every operation. - **Interactive API reference:** [Swagger UI](https://api.mediacopilot.cires21.ai/docs). - **Guides:** [MediaCopilot API documentation](https://docs.mediacopilot.io/en/integrations/api) — upload flow, the async job pattern, processing modes and export destinations. ## Authentication Every MediaCopilot API request requires a Bearer token in the `Authorization` header: `Authorization: Bearer ` API keys are issued with your MediaCopilot account — request access at [hello@mediacopilot.io](mailto:hello@mediacopilot.io). Keys are secrets: keep them server-side, never in client code or a public repository. Full authentication documentation is part of the [API guide](https://docs.mediacopilot.io/en/integrations/api). This website (mediacopilot.io) is entirely public and needs no credentials. ## MCP Server (Model Context Protocol) MediaCopilot exposes its capabilities to AI agents through an MCP Server, so any MCP-compatible host — Claude, Cursor, or your own agent — can drive video workflows as tools: asset management, transcription, translation, dubbing, clip generation, smart search, metadata, collections, templates and publishing. See the [MCP Server documentation](https://docs.mediacopilot.io/en/integrations/mcp-server). The server is available to enterprise customers; contact [hello@mediacopilot.io](mailto:hello@mediacopilot.io) for the endpoint and credentials. ## Command-line tool There is no official MediaCopilot CLI on npm, PyPI or Homebrew today. Anything published under that name is not ours — script MediaCopilot through the REST API or the MCP Server instead. If a CLI would unblock your workflow, tell us at [hello@mediacopilot.io](mailto:hello@mediacopilot.io). ## This website, for machines mediacopilot.io is a static marketing site, and its content is available to agents without scraping HTML: - [/llms.txt](/llms.txt) — llmstxt.org index of every page. - [/openapi.json](/openapi.json) — OpenAPI 3.1 description of this host (also at [/v1/openapi.json](/v1/openapi.json)). - [/v1/site.json](/v1/site.json) — organization, contacts and every developer endpoint as JSON. - [/v1/pages.json](/v1/pages.json) — every page with its title, description, language and markdown URL. - [/v1/problems.json](/v1/problems.json) and [/problems](/problems) — the typed error model. - [/.well-known/api-catalog](/.well-known/api-catalog) — RFC 9727 API catalog listing both this surface and the MediaCopilot API. - [/sitemap.xml](/sitemap.xml), [/robots.txt](/robots.txt). Every page also has a markdown twin: append `.md` to any path, or send `Accept: text/markdown`. Negotiated responses carry `Vary: Accept, Accept-Encoding` and RFC 8288 `Link` headers. ## Versioning and deprecation Both the MediaCopilot API and the JSON surface of this website use **URL path versioning**: `/v1/…`. Within a version, changes are additive — new fields and new endpoints may appear, so ignore members you do not recognise rather than failing. A breaking change gets a new prefix (`/v2/…`) and the previous version keeps working during the notice period. When a versioned resource on this host is scheduled for retirement, its responses carry the `Deprecation` header (RFC 9745), a `Sunset` header (RFC 8594) with the retirement date, and a `Link` header with `rel="deprecation"` pointing at this section. We publish at least 180 days between the first `Deprecation` header and the `Sunset` date. Machine clients should read the policy from [/v1/site.json](/v1/site.json) (`api.versioning`) rather than parsing this page. ## Rate limits and errors The public surface of this website is served from a CDN and applies no per-client quota, so no `RateLimit` headers are emitted on a normal response. Write clients defensively anyway: on `429` or `503`, honour `Retry-After` and back off exponentially. Rate limits on the credentialed MediaCopilot API are agreed per account — ask [hello@mediacopilot.io](mailto:hello@mediacopilot.io). Errors this host generates are RFC 9457 `application/problem+json` with a stable `code` member to branch on. The catalogue of codes, with recovery hints, is at [https://mediacopilot.io/problems](/problems). --- Machine-readable index of this site: [llms.txt](https://mediacopilot.io/llms.txt) · [sitemap.xml](https://mediacopilot.io/sitemap.xml) · [openapi.json](https://mediacopilot.io/openapi.json) · [error reference](https://mediacopilot.io/problems.md)