AI Catalog manifest · Opus

OpusClip

Opus serves an AI Catalog manifest at /.well-known/ai-catalog.json on opus.pro, declaring 1 agentic resource that a discovery service can index without asking anyone’s permission.

Open the live manifest → Opus provider profile

Structural grade · AI Catalog 1.0

Flavored

Fails a hard check in the data model. A catalog in spirit rather than in schema.

ARD conformance tool v0.5.0

FAIL

Run against this exact body with the project’s own conformance CLI — 1 critical error.

Declared spec version

0.1

The specVersion in the manifest. AI Catalog 1.0 is current; anything lower is an earlier draft.

⚠ Hard checks failed. An ARD client cannot assume this manifest parses to the model the specification defines.

entry-identifier-not-urn-air

The urn:ai: prefix is not sloppiness — it is the identifier scheme ARD itself specified until ADR-0009 moved the namespace identifier from ai to air for URN validity. This publisher implemented against the earlier draft.

Optional affordances missing. None of these break a client, but each one costs the publisher search relevance or verifiability.

cors-not-wildcard
host-identifier-not-did-web
representativeQueries-outside-2-5

1 entries

1 media type

10 representative queries

1 trust manifests

Host identifier: https://opus.pro

What this manifest advertises

OpusClip MCP Server

urn:ai:opusclip:video:clip-mcp

Turn long video into ready-to-post vertical clips with viral scoring, captions, reframes, B-roll, translation, and scheduled posting. Callable from any MCP client (Claude, Cursor, Cline, Continue, ChatGPT).

application/vnd.mcp+json artifact →

“clip a long video into viral shorts”
“turn a YouTube video into TikTok clips”
“repurpose a podcast into short clips”
“add captions to a video automatically”
“reframe a video to 9:16 vertical”
“edit and clip video inside Claude”
“video editing API for an AI agent”
“schedule social media posts from clips”
“AI video editing API”
“ffmpeg alternative for an agent”

How it is served

The publishing guide asks for three things at the transport layer, because a crawler is the consumer that matters and a crawler is a browser-shaped client.

HTTPS only — yes (HTTP 200)
Content-Type: application/json — yes
Access-Control-Allow-Origin: * — no — header absent

Evidence. Fetched https://www.opus.pro/.well-known/ai-catalog.json on 2026-07-31, HTTP 200. The verbatim body is stored alongside its manifest in the Opus repository as ai-catalog/opus-ai-catalog.json. Nothing on this page is derived or generated: an AI Catalog manifest is served from the publisher’s own domain or it does not exist, which makes it — like an A2A Agent Card — one of the few agent artifacts that cannot be produced on a provider’s behalf. Grades are recomputed on every build; the specification is a v0.9 draft and these verdicts will move when it does.

Work with this as data

Every descriptor here is available over the APIs.io API and to AI agents over MCP. Agent Discovery is not yet its own endpoint on the v1 API. Reach it through catalog search and the tag graph, or the MCP server.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for agent discovery

3 MCP tools reach this

apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools

Call it yourself

curl for this page

Search the catalog

curl "https://apis.io/api/v1/search?q=opus&limit=10"

Everything under a tag

curl "https://apis.io/api/v1/tags/opus"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.