Machine-readable

API docs

ClipNav publishes five read-only JSON indexes of the public directory. They are static dumps of published entries. They are not an authenticated product API. There is no API key, no account, and no write method. GET is the only method these routes implement.

What a response contains

Each file is JSON with three top-level fields. example is a boolean, false on a published catalog. notice is a string; a published catalog says "Published catalog." items is the array of published entries. Draft entries and EXAMPLE fixtures are left out.

An item carries the entry's public fields, its slug, a site path, and the source markdown. The rendered HTML string is not included. Dates are YYYY-MM-DD. Where a price or capability was checked, the entry has a verification date such as verified_on. A missing price is written as not observed. It is not guessed.

Endpoints

Tools — /api/tools.json

Published tools for Shorts, TikTok, and YouTube workflows. Fields include the name, summary, workflow and platform tags, capabilities, pricing tier, whether a public vendor API was observed, an optional API URL, an optional vendor MCP note, and verified_on. The HTML page is /tools/{slug}.

Models — /api/models.json

Published AI video models. Fields include the name, summary, capabilities, price band, where to run the model, and flags for text-to-video, image-to-video, native audio, multi-shot, and open source, plus verified_on. The HTML page is /models/{slug}.

Features — /api/features.json

Published feature matrices. Each feature lists platforms. A platform row records whether the web product was observed, an API note, an MCP note, a price band, and a verification date. The HTML page is /features/{slug}.

Workflows — /api/workflows.json

Published workflow pages. Fields include the audience, a recommended path, a monthly cost note, stages, and verified_on. The HTML page is /workflow/{slug}. Faceless format pages live at /workflow/faceless/{slug} and are not a separate JSON file.

Guides — /api/guides.json

Published guides, when any exist. There is no HTML guide route yet. EXAMPLE guide fixtures are excluded, so items may be an empty array. An empty array is an empty catalog, not an HTTP error. A future guide item would include a title, description, dates, and a path under /guides/{slug}.

Compare, platform, and trend pages are HTML, and the same URLs can return markdown. They are not separate JSON indexes.

How to call them

Request the URL with GET. The response content type is application/json; charset=utf-8. These JSON routes do not switch to markdown when you send Accept: text/markdown. For a page as markdown, send that header to an HTML URL such as /docs, a tool page, or /contact. Start from /llms.txt for the page list, the when-to-use note, and the same index URLs.

Example: curl -s https://clipnav.com/api/tools.json

What is not shipped

OpenAPI and Swagger are not published. There is no mutating REST API and no authenticated endpoint. These dumps do not return a special JSON error schema. A ClipNav MCP server is not shipped. A tool entry may still record whether that vendor publishes an MCP. That note is about the vendor, not a ClipNav protocol endpoint.

Related

About explains how listings are chosen and how prices are checked. Contact is hi@clipnav.com for corrections and questions. Public submissions are paused. Browse tools and models for the HTML catalog, or the sitemap for every HTML URL.