A2A Agent Card · BitterClip
· card published by Opus Clip
Opus Clip
⚠ This card does not identify BitterClip.
It identifies itself as Opus Clip
at
opus.pro
✓ Conformant with A2A 1.0.0. This card passes every structural check in the
A2A specification’s
, which is not
BitterClip’s registered domain
(AgentCard object — a capabilities object, a declared protocolVersion, and a well-formed skills array.
bitterclip.com).
It was found at this path because BitterClip’s record references that host. That happens for a product or a parent company as readily as for an unrelated one, so we do not claim BitterClip serves this agent endpoint — the card is reproduced here as published, and the identity above is the card’s own.
Discovery
An A2A client finds this agent by fetching the well-known path on the host below. An agent card cannot be derived, generated or reconstructed on anyone’s behalf — whoever serves it published it — but this host is not BitterClip’s own, so the card is evidence about Opus Clip rather than about BitterClip.
https://help.opus.pro/.well-known/agent-card.json
Interfaces
https://help.opus.pro/
· transport HTTP+JSON
non-standard interface list
Skills (1)
opusclip
Use when building video clipping workflows, automating short-form
Documentation
Evidence. Fetched
2026-11-02 from https://help.opus.pro/.well-known/agent-card.json,
HTTP 200. The body was saved verbatim and is the sole source for
everything on this page — no field is inferred.
View the captured card.
Providers change what they serve; if this card has moved or changed shape,
the provider profile carries the
current state as of the last build.
Work with this as data
Every agent card here is available over the APIs.io API and to AI agents over MCP. A2A Agent Cards is not yet its own endpoint on the v1 API. Reach it through catalog search and the tag graph, or the MCP server.