Flick
Flick is an AI filmmaking studio that lets creators direct short films with AI on an infinite, node-based canvas. Rather than a linear prompt-to-clip generator, Flick gives directors a nonlinear workspace to plan, iterate and assemble complete narratives of any length — generating scenes, keeping character faces and styles consistent across shots, controlling shot composition, and editing images by reference. The product is a web app with a free tier (300 credits) and paid plans from $5/month, plus a Creative Partner Program and a Filmmaker Residency for AI filmmakers. Flick was founded by Ray Wang (previously a founding engineer on the Instagram AI team) and award-winning filmmaker Zoey Zhang, and is Y Combinator- and GV-backed. Flick publishes product documentation, a blog and a verbatim llms.txt, but does not currently expose a public developer API, SDKs, webhooks or an MCP server — the /api/ surface is an internal application API that robots.txt explicitly disallows.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Flick the way a machine reads it — 1 machine-readable artifact, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Flick scores 20.9/100 (emerging), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Flick
Each block below is one kind of artifact we hold for Flick. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Flick — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Access & Security 1
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 1
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 7
The organization behind the API
Scroll within the panel for all 7 ·
← All providers · Data indexed from github.com/api-evangelist/flick · machine-readable index on apis.io