Opus
OpusClip (Opus) is an AI video platform that turns long-form videos into short-form, viral clips and publishes them to social platforms. The OpusClip API lets developers submit a source video by URL or upload, create a clipping project, tune curation/import/render preferences, apply brand templates, retrieve exportable clips and transcripts, organize clips into collections, run censor and generative thumbnail jobs, and generate, publish, or schedule social posts to connected accounts. The API is REST over JSON at https://api.opus.pro, authenticated with a bearer API key, with HMAC-signed webhooks, page-based pagination, and a hosted MCP server plus an Agent Skill for agent-native access. API access is available on the Pro (Beta), Max, and Business plans.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Opus the way a machine reads it — 20 machine-readable artifacts across 11 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Opus scores 51.5/100 (developing), with a separate agent-readiness read of 75/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Opus
Each block below is one kind of artifact we hold for Opus. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 11
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Opus brand-templates API
The brand-templates API from Opus — 1 operation(s) for brand-templates.
Opus censor-jobs API
The censor-jobs API from Opus — 2 operation(s) for censor-jobs.
Opus clip-project API
The clip-project API from Opus — 3 operation(s) for clip-project.
Opus collection API
The collection API from Opus — 3 operation(s) for collection.
Opus collection-content API
The collection-content API from Opus — 2 operation(s) for collection-content.
Opus enterprise API
The enterprise API from Opus — 18 operation(s) for enterprise.
Opus exportable-clips API
The exportable-clips API from Opus — 1 operation(s) for exportable-clips.
Opus ExportableClip API
The ExportableClip API from Opus — 1 operation(s) for exportableclip.
Opus generative-jobs API
The generative-jobs API from Opus — 2 operation(s) for generative-jobs.
Opus social-posting API
The social-posting API from Opus — 6 operation(s) for social-posting.
Opus transcripts API
The transcripts API from Opus — 1 operation(s) for transcripts.
Scroll within the panel for all 11 ·
Arazzo Workflows 3
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
_Index
ARAZZOOpusClip — clip a video and export clips
Submit a long-form video, wait for clipping, list clips, and export a collection.
ARAZZOOpusClip — clip a video and publish to social
Clip a video, generate social copy, and publish a clip to a connected social account.
ARAZZOMCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
opus-mcp.yml
MCP SERVERSecurity Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Opus — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 5
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 8
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 8 ·
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/opus · machine-readable index on apis.io