ClipTaps for developers & AI agents

ClipTaps is drivable programmatically. Developers use the REST API to generate and publish faceless short-form videos; AI agents use the MCP server to call ClipTaps as tools; and a machine-readable plan catalogue plus an A2A agent cardmake pricing and capabilities discoverable without a human.

Authentication

Authenticated requests use a Bearer token. Create a long-lived API key under Settings → API Keys (recommended for scripts and the MCP server) — or use the short-lived session JWT the web app issues. A key acts as your account, so usage counts against your plan quota. Public endpoints — the plan catalogue and the agent card — need no auth. OAuth 2.1 is on the roadmap.

Authorization: Bearer ct_live_…   # API key (never expires until revoked)

Plans & entitlements

Every tier’s limits come from one source of truth. Each plan defines videos per period (Free resets daily; paid tiers reset monthly), a scene cap per video, whether output is watermarked, and whether an AI agent may purchase it. Read the live catalogue:

GET https://cliptaps.com/api/payments/plans   # public, no auth

# → { "plans": [ { "tier": "FREE", "priceUsd": 0, "videosPerPeriod": 1,
#       "period": "day", "maxScenesPerVideo": 3, "watermark": true,
#       "agentPurchasable": false, "stripePriceId": null }, ... ] }

Quota & usage

Check how much of the current window is left. Generation is charged one video credit per project and enforced server-side; when the window is exhausted, generation returns 402.

GET https://cliptaps.com/api/payments/status        # auth

# → { "tier": "PRO", "period": "month", "limit": 30, "used": 4,
#     "remaining": 26, "resetAt": "2026-08-01T00:00:00.000Z",
#     "maxScenesPerVideo": 10, "watermark": false }

# 402 when exhausted:
# { "message": "Monthly video limit reached (30/30)...", "tier": "PRO",
#   "used": 30, "limit": 30, "resetAt": "..." }

Generate & publish a video

Generation is a short pipeline. Create a project, attach source text, build the storyboard (which produces scenes), then start generation and poll until the scenes complete. Publish through the posting endpoint.

POST /api/projects                              → { projectId }
POST /api/projects/{projectId}/source-data/text   { "text_prompt": "..." }
POST /api/projects/{projectId}/storyboard/script  # creates scenes
POST /api/generate/video-start                    { "sceneIds": ["...","..."] }  # 202
GET  /api/generate/video-status/{projectId}       # poll: project + per-scene status
POST /api/posting/create                          # publish to TikTok / Reels / Shorts

MCP server (for AI agents)

The ClipTaps MCP server exposes a curated set of tools so any MCP-capable client (Claude, IDEs, other agents) can drive the product. Point it at the API base (must end in /api) and supply a long-lived API key for authenticated tools; transport is stdio.

CLIPTAPS_API_BASE=https://cliptaps.com/api \
CLIPTAPS_API_KEY=ct_live_… \
npx @cliptaps/mcp-server

Agent card (A2A)

For agent-to-agent discovery, ClipTaps publishes an A2A agent card describing its skills:

GET https://cliptaps.com/.well-known/agent-card.json

View the live agent card →

Roadmap

• •Per-key rate limits & scopes — per-tier throttling and scoped keys (API keys themselves are available now under Settings → API Keys).
• •Agent action tools — create_project, start_generation, publish_to_social once per-request auth is wired.
• •Delegated purchases — real purchase_plan via scoped mandates for agent-purchasable tiers.
• •OAuth 2.1 — scoped, short-lived tokens with audience validation.

See also: FAQ · Use cases · Pricing