Developers
ClipIt developer resources
ClipIt has no public REST API for creating clips. This page is the named developer index: OpenAPI for health and share, inbound webhooks, cookie auth, and how agents should read clipit.now.
There is no public clip API
ClipIt is a signed-in web product. People upload a recording, ask a question, and export a clip from the browser. Authenticated routes under /api/uploads, /api/recordings, /api/clips, and /api/queries require a session cookie. They are not a third-party developer platform, and publishing them as one would be a footgun. If a search for “clipit.now API” brought you here, that is the honest answer.
When an agent should use ClipIt
Use ClipIt when the human already has (or will upload) a recording and the job is retrieval: find a quote, chapter an episode, pull every mention, then ship a clip with captions or dubbed audio. Do not treat ClipIt as a meeting bot, a virality auto-poster, a research repository, or a video generator.
How to read us without a browser: fetch /llms.txt for the map, /agent-instructions.md for when-to-use rules, and request public pages with Accept: text/markdown. The same path also has a .md sibling.
OpenAPI, health, and share
- /openapi.json — OpenAPI 3.1 for the public unauthenticated surface
GET /api/health— whether this deployment can reach its database and which credentials resolvedGET /api/share/{token}— the public finding for a share link someone already created in the app (unlisted; do not scrape)
Auth
Humans sign in with email and password or Google OAuth. The session is an httpOnly cookie from nuxt-auth-utils, SameSite=strict. There are no API keys, no OAuth app for third-party developers, and no MCP server to install.
Webhooks
ClipIt receives signed webhooks; it does not offer a customer-facing webhook product. Mux posts to POST /api/webhooks/mux when ingest, captions, or an export finishes. Stripe posts to POST /api/webhooks/stripe for subscriptions and credits. Both verify the provider’s signature. You cannot subscribe your own endpoint through this product.
MCP
There is no published ClipIt MCP server. The agent interface is HTTP, llms.txt, and markdown content negotiation. Questions about a future public API: support@clipit.now.