How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Captions website screenshot

Captions

Captions is an AI video editor and generator built by Mirage, an AI research company headquartered in New York City. The consumer and enterprise apps automate the most time-consuming parts of video production — cutting scenes, adding B-roll, inserting music and sound effects, generating and styling captions, dubbing into 30+ languages, correcting eye contact, and generating entirely new videos from a text prompt or a selfie via AI Avatars, AI Actors, and AI Twins. The Mirage Video API (api.mirage.app) exposes this pipeline to developers: asynchronous AI video generation, adding stylized captions to videos, caption-template discovery, text-to-speech audio, and meta text overlays. Authentication is a simple x-api-key header, keys are minted in the Mirage platform dashboard, and long-running jobs are polled for status.

agent aware

Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.

Kin Score

API Evangelist profiles Captions the way a machine reads it — 34 machine-readable artifacts across 3 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 — Captions scores 65.9/100 (strong), with a separate agent-readiness read of 26/100 (agent aware). 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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.

Kin Score Kin Score How this is scored →
scored 2026-09-10 · rubric v0.20.0
Captions Kin Score — API readiness rating by API Evangelist

Put this on your own site. The badge is drawn live from Captions's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.

<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/captions/"
   title="Captions on API Evangelist — API profile and Kin Score">
  <img src="https://apis.io/badge/captions.svg"
       alt="Captions Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>

More shapes, themes and sizes → · Score as JSON · How badges work

How we profile Captions

Each block below is one kind of artifact we hold for Captions. 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 9

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.

Captions Audio API

The Audio API from Captions — 1 operation(s) for audio.

Captions health API

The health API from Captions — 1 operation(s) for health.

Captions internal API

The internal API from Captions — 8 operation(s) for internal.

Captions Meta Text Overlays API

The Meta Text Overlays API from Captions — 2 operation(s) for meta text overlays.

Captions root API

The root API from Captions — 1 operation(s) for root.

Captions Video Captions API

The Video Captions API from Captions — 3 operation(s) for video captions.

Captions Videos API

The Videos API from Captions — 3 operation(s) for videos.

Captions AI Ads API

Generate UGC-style AI advertising videos using AI creators

Captions AI Creator API

Generate talking-head videos using community AI avatars or AI Twins

Scroll within the panel for all 9 ·

Open Collections 10

Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Scroll within the panel for all 10 ·

Pricing Plans 2

Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.

Published pricing tiers and plan structures.

Captions Plans

5 plans

PLANS

Rate Limits 1

Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.

Documented rate limits and quota policies.

Captions Rate Limits

6 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.

Cost, billing, and metering signals for API financial operations.

Semantic Vocabularies 1

JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.

JSON-LD contexts and semantic vocabularies used across these APIs.

Captions Context

3 classes · 31 properties

JSON-LD

Spectral Rules 1

Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.

Captions API Rules

5 rules · 4 warnings

SPECTRAL

JSON Schema 3

Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.

Standalone JSON Schema definitions for this provider's data models.

MACaptionTemplate

5 properties

JSON SCHEMA

CreatorJobPollResponse

4 properties

JSON SCHEMA

MAVideo

12 properties

JSON SCHEMA

Examples 3

Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.

Example request and response payloads for these APIs.

Security Posture 2

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.

Captions Authentication

apiKey · 1 scheme

SECURITY

Captions Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

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.

Captions Agentic Access

23 operations · 11 acting · 5 human-in-the-loop

23 operations · 11 acting

AGENTIC

Resources

Every other property we hold for Captions — 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 3

Portal, sign-up, and the first successful call

Documentation 3

Reference material describing how the API behaves

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 3

Authentication, authorization, and security posture

Company 3

The organization behind the API

Other 3

Properties that don't map to a standard resource type

← All providers · Data indexed from github.com/api-evangelist/captions · machine-readable index on apis.io

Where this information came from

This is an independent, third-party profile of Captions, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.