canonical: https://jentic.com/apis/clypmint.com/clypmint # Clypmint API The Clypmint API creates and revises short videos from styles. It lists available styles and can copy a style from a reference video link, lists your recent videos, and starts a video edit that returns a private upload link for your source video. You check a video or an upload by its id until it is ready, then ask for a change to a finished video in plain words. The account profile endpoint returns your account details. ## For AI agents Browse video styles, start a video edit to get a private upload link, check a video until it is ready, and request plain-language changes to a finished video. Authenticated with a bearer API key or OAuth token. ## Scope Does not host live streams, transcode arbitrary files, or manage ad placement. Use for creating, checking, and revising Clypmint videos from styles only. ## Capabilities - Browse the available video styles - Copy a style from a reference video link - Start a video edit and get a private upload link for your source video - Check a video or an upload by its id until it is ready - Request a change to a finished video in plain words - List your recent videos and read your account profile ## Use cases ### Agent-Driven Video Creation An AI agent starts a video edit through Jentic, uploads the source to the private link it gets back, and polls the video by id until it is ready, then requests changes in plain words. The bearer key authenticates the write operations while styles can be browsed openly, and a rule can keep the agent on creating and checking videos. The agent finds each operation by intent and calls it directly. Example prompt: Start a video edit with a chosen style, upload the source to the returned link, and poll the video by id until it is ready. ### Style-Based Video Templating A tool browses the available styles and copies a style from a reference video link so new videos match a consistent look. Clypmint lists styles and creates a new style from a reference, which later edits can reuse. Teams use this to keep a repeatable visual style across many videos. Example prompt: Copy a style from a reference video link and start a new video edit using that style. ### Iterative Video Revisions After a video is finished, a workflow asks for changes in plain words and checks the updated video by id until the new version is ready. Clypmint accepts a plain-language change request against a finished video and reprocesses it. Teams use this to refine a video without re-specifying the whole edit. Example prompt: Request a shorter intro on a finished video and poll it by id until the revised version is ready. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/styles` | List styles | | POST | `/styles` | Copy a style from a reference video link | | GET | `/videos` | List recent videos | | POST | `/videos` | Start a video edit and get an upload link | | GET | `/videos/{id}` | Check a video or an upload | | POST | `/videos/{id}/changes` | Request a change to a finished video | | GET | `/me` | Get the account profile | ## Key resources - **Styles** — List available styles and copy a style from a reference video link - **Videos** — Start a video edit, list recent videos, check a video or upload by id, and request changes - **Account** — Read the account profile ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 46 / 100 - **Maturity:** Foundational - **Dimensions:** - Foundational Compliance: 99 / 100 - Developer Experience & Jentic Compatibility: 66 / 100 - AI-Readiness & Agent Experience: 21 / 100 - Agent Usability: 94 / 100 - Security: 60 / 100 - AI Discoverability: 59 / 100 - **View full report:** https://jentic.com/apis/clypmint.com/clypmint/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring the Clypmint API by hand means sending a bearer token (an API key or OAuth token), starting an edit to get a private upload link, and polling a video by id until it is ready. Through Jentic you install once, import Clypmint from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** Clypmint puts the video id in the URL path, so a rule can pin your agent to starting and checking videos and the operations you pick. You choose what it may call, so copying styles or reading the account profile is not included unless you add it. - **Credential handling:** Your Clypmint token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'start a video edit' or 'check a video', and Jentic returns the matching Clypmint operation with its input schema so the agent calls the right endpoint without reading the reference docs. ## Related APIs - **Shotstack** — Programmatic video editing and rendering from a JSON timeline. - **Creatomate** — Automated video and image generation from templates. - **Mux** — Video hosting, streaming, and analytics for finished videos. ## FAQ ### What authentication does the Clypmint API use? The Clypmint API authenticates with a bearer token in the Authorization header, which can be an API key or an OAuth token, per its OpenAPI spec. The styles list and the OpenAPI document can be read without a key, while creating and checking videos use the token. Through Jentic the token is stored encrypted by your own Jentic One instance and injected only at call time. ### Can I create and revise videos with the Clypmint API? Yes. You start a video edit and get a private upload link, check the video by its id until it is ready, and then ask for a change to the finished video in plain words. You can also browse styles and copy a style from a reference video link. ### What are the rate limits for the Clypmint API? The OpenAPI spec does not specify rate limits for the Clypmint API. Check the vendor's documentation at https://clypmint.com for current limits before pointing an agent at it. ### Can I limit what my agent is allowed to do with the Clypmint API? Yes. Write a rule that allows only starting and checking videos, so the agent can create and track a render but not copy styles or read your account profile. Each video id is in the URL path, so the rule binds to the video operations, and every call it makes is logged. ### Is there a Clypmint MCP server? You don't need an MCP server to give your agent the Clypmint API. Jentic connects it directly from the API Directory: import it, store your token once, and your agent calls the style and video operations. You skip loading another server's tool definitions into the agent's context. ### How do I create a video through Jentic? Add the Clypmint API from the Jentic API Directory and store your token once. Your agent then searches by intent such as 'start a video edit' and Jentic returns the matching operation with its input schema, so it can start the edit and poll the video until it is ready. To run it on your own infrastructure, install Jentic One from its GitHub repo.