Skip to main content
Five ideas cover almost everything you need to reason about the API. Each links to a page with the full detail.

Collections

A collection is a named group of videos. Every video belongs to one collection. Pass collection_id to search within a known collection and reduce unrelated matches. See Collections.

Jobs and the processing lifecycle

Uploading a video creates a processing job. The job moves through queued → processing → done or reaches failed. A video becomes searchable when the job reaches done. See Processing lifecycle.

Search signals

Pureframe AI can match visual content, spoken words, scene context, and text visible on screen. Use modes to restrict a request when you know which signals matter. See Search overview.

Segments, not videos

Search returns timestamped segments grouped by video. Each segment includes timestamp_start, timestamp_end, and a relevance score. It can also include a thumbnail or matching text. One video can contain several matching segments. See Search results.

Credits

Pay as you go accounts are billed per action, deducted from a prepaid credit balance: indexing costs per minute of video, search costs a small flat fee per request. There’s no monthly subscription; you top up credits and they draw down as you use the API. Free accounts get a daily search quota and a one-time trial credit instead. See Usage and Billing.

Quickstart

Put all five to work in one walkthrough.

Metadata

Every field on every object, in one reference.