Clipkit

Clipkit Render API

Plain-HTTPS render API documented in the Vercel integration guide. POST a CKP/1.0 Source JSON to /api/v1/renders with Authorization Bearer CLIPKIT_API_KEY, then poll GET /api/v1/renders/{id} for status and a signed output_url to the finished MP4; webhooks deliver render.completed / render.failed. No OpenAPI is published; the contract here is generated from the documentation by API Evangelist (2026-11-04), not the provider's own document.

Documentation GitHub OpenAPI

Operations 2

POST /api/v1/renders POST /api/v1/renders #

GET /api/v1/renders/{id} GET /api/v1/renders/${submit.id} #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this

find_apisBrowse and filter every API in the catalog.
get_api_artifactsOne API's artifacts, grouped by type.
get_openapiThe primary OpenAPI for this API.
find_similar_apisAPIs that look like this one.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This API

curl "https://apis.io/api/v1/apis/clipkit-dev:clipkit-dev-render-api"

All apis

curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

openapi: 3.1.0
info:
  title: Clipkit API
  version: '2026-11-04'
  description: 'GENERATED FROM DOCUMENTATION by API Evangelist on 2026-11-04: 3 operation(s)
    read from 5 public documentation page(s) (each operation names its page in x-source).
    This is not the provider''s published contract; Clipkit has published no machine-readable
    contract that the pipeline could find. Engine: anthropic.'
  x-evidence-tiers:
    code-example: 3
    documentation: 0
    pages-with-code: 4
    pages-read: 5
  x-generated-from: documentation
  x-provenance: generated
  x-authored-by: API Evangelist
  x-generated: '2026-11-04'
  x-generator: generate-contract-from-docs.py
  x-engine: anthropic
  x-sources:
  - https://www.clipkit.dev/docs/mcp/grok.md
  - https://www.clipkit.dev/docs/vercel
  - https://www.clipkit.dev/docs/mcp/grok
  - https://www.clipkit.dev/llms-full.txt
  - https://www.clipkit.dev/docs/vercel.md
  x-correction: '2026-11-04 contract module: dropped post /v1/responses (xAI Responses
    API quoted on the Grok MCP quickstart, not a Clipkit operation); normalised JS
    template path ${submit.id} to {id} per docs/vercel.md; added server from docs/vercel.md.'
paths:
  /api/v1/renders:
    post:
      operationId: createRender
      tags:
      - Api
      summary: POST /api/v1/renders
      x-source: https://www.clipkit.dev/llms-full.txt
      responses:
        '201':
          description: Success (status as documented)
      x-evidence:
        kind: code-example
        language: javascript
        snippet: "fetch(\"https://www.clipkit.dev/api/v1/renders\", {\n    method:\
          \ \"POST\",\n    headers: {\n      Authorization: `Bearer ${process.env.CLIPKIT_API_KEY}`,\n\
          \      \"Content-Type\": \"application/json\",\n    },\n    body: JSON.stringify(source),\n\
          \  })"
  /api/v1/renders/{id}:
    get:
      operationId: getRender
      tags:
      - Api
      summary: GET /api/v1/renders/${submit.id}
      x-source: https://www.clipkit.dev/llms-full.txt
      parameters:
      - name: id
        in: path
        required: true
        schema:
          type: string
        description: Render id returned by POST /api/v1/renders.
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: code-example
        language: javascript
        snippet: "fetch(`https://www.clipkit.dev/api/v1/renders/${submit.id}`, {\n\
          \      headers: { Authorization: `Bearer ${process.env.CLIPKIT_API_KEY}`\
          \ },\n    })"
      x-source-quote: call `GET /api/v1/renders/{id}` again any time for a fresh one
        (https://www.clipkit.dev/docs/vercel.md)
components:
  schemas:
    PostV1ResponsesRequest:
      type: object
      properties:
        model:
          type: string
        input:
          type: string
        tools:
          type: array
          items:
            type: object
            properties:
              type:
                type: string
              server_label:
                type: string
              server_url:
                type: string
    PostV1ResponsesResponse:
      type: object
      properties:
        model:
          type: string
        input:
          type: string
        tools:
          type: array
          items:
            type: object
            properties:
              type:
                type: string
              server_label:
                type: string
              server_url:
                type: string
  securitySchemes:
    bearer:
      type: http
      scheme: bearer
security:
- bearer: []
tags:
- name: Api
- name: Responses
servers:
- url: https://www.clipkit.dev
  description: 'Stated in https://www.clipkit.dev/docs/vercel.md: fetch("https://www.clipkit.dev/api/v1/renders")
    with Authorization: Bearer CLIPKIT_API_KEY'