Glossary
Definitions of terms used across the Pipevideo product and API.
| Term | Meaning |
|---|---|
| Organization | Billing and access boundary. Owns API keys, credits, usage, and webhooks. |
| API key | Secret credential (pv_...) authenticating HTTP requests for your organization. |
| Engine | Rendering system that produces the final video (e.g. HyperFrames). |
| Orchestration model | LLM that composes the video project. Specified as the model field in requests. |
| Generation | A single video creation request, identified by id (e.g. gen_abc123). |
| Response | OpenAI Responses-compatible API shape used for video generation requests and responses. |
| Provider | External video orchestration provider that fulfills a generation (e.g. framerate). Integrated via Pipevideo, not called directly by customers. |
| Framerate | Video orchestration provider at framerate.sh. Available through Pipevideo with slug framerate. |
| Provider routing | Selecting a provider via provider.order preference list. |
| Credit | Prepaid balance (in cents) used for token-based orchestration charges. |
| HyperFrames | Pipevideo's code-driven motion graphics rendering engine. |
| Webhook | HTTP callback delivered via Svix when a generation completes or fails. |
| MCP | Model Context Protocol server exposing video generation tools to AI assistants. |