←clipzi

Clipzi API and Developer Resources

Last updated: August 24, 2026

Everything programmatic about Clipzi in one place: what exists today, what the contracts are, and how to reach us if you need more.

API status

The Clipzi product API (upload, analyze, clip export) currently requires an authenticated browser session and is not yet open for programmatic use. The public surface documented today is the contact endpoint and the machine-readable resources below. If you want API access for your use case, tell us through the contact endpoint or at g@clipzi.app.

OpenAPI specification

The machine-readable description of the public HTTP surface lives at https://clipzi.app/openapi.json. It documents every endpoint, schema, error envelope, and the policies on this page.

Versioning and deprecation policy

  • The API is versioned by URL path: /api/v1/... is the current version.
  • Unversioned paths (like /api/contact) are aliases of the current version.
  • Breaking changes only ship in a new path version (/api/v2/); v1 behavior never changes.
  • Before an endpoint is removed, its responses carry Deprecation and Sunset headers (RFC 8594) for at least 90 days, and the OpenAPI spec is updated with the replacement.

MCP server

A read-only MCP (Model Context Protocol) server runs at https://clipzi.app/api/mcp using the Streamable HTTP transport, stateless and with no auth required. It exposes three tools: get_product_info, get_pricing, and get_developer_docs. The discovery manifest lives at https://clipzi.app/mcp.json.

Rate limits

API responses carry IETF RateLimit headers so clients can self-throttle in real time: RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset (seconds until the window resets), and RateLimit-Policy (limit;w=windowSeconds). Exceeding a limit returns HTTP 429 with a Retry-After header and a JSON error body. Current limits:

  • Contact endpoint: 10 requests per minute per IP.
  • MCP endpoint: 60 requests per minute per IP.
  • Other /api/* paths: 120 requests per minute per IP.

Errors

All API errors are JSON, never HTML. Unknown /api/* paths return HTTP 404 with a structured envelope: an error object with code, message, and a hint pointing at the next step.

Machine-readable resources

Markdown content negotiation

The homepage and this page serve a markdown variant to clients that request it with Accept: text/markdown (responses vary on Accept). Browsers keep getting HTML; agents that prefer markdown get markdown at the same URL.

Contact

Support, partnerships, or API access requests: POST /api/v1/contact (see the spec) or email g@clipzi.app.