Developer glossary
Use these practical definitions to choose a model, handle task states, verify callbacks, estimate usage and protect user media.
Definition
An API that accepts a media request, returns a durable task ID, and completes outside the original HTTP request.
Persist the task ID before polling or waiting for a webhook. Queued and running are active; succeeded, failed and expired are terminal. Accepted tasks cannot be canceled.
Related page →Definition
A client-generated identifier that lets repeated submissions resolve to one logical task instead of creating duplicate billable work.
Reuse the same key only for the same validated request. Store it with the task and return the original result when a retry arrives.
Related page →Definition
A cryptographic value attached to a callback so the receiver can verify that the event came from the API and was not changed in transit.
Verify the raw request body, reject stale timestamps and deduplicate event IDs before changing task or billing state.
Related page →Definition
The machine-readable contract describing a model's accepted fields, types, limits, defaults and output shape.
Generate forms and server validation from the published schema, but pin or record the schema version used for each task.
Related page →Definition
An input image used to guide identity, composition, style or motion in an image or video generation request.
Collect provenance and consent, validate format and size, and avoid treating a reference as permission to reproduce a real person's likeness.
Related page →Definition
A billing model based on measured usage. Each model states the applicable unit, such as each image, output second, megapixel, token or request.
Show the unit and the pre-run estimate before submission; minimum charges, duration and output count can change the final cost.
Related page →Definition
A model option with fewer content filters that may process a wider range of content; the label is product information, not platform approval.
Implement the age, consent, real-person and jurisdiction controls your own users and service require before submitting a request.
Related page →Definition
A product workflow that records who or what is depicted, what permission exists and which policy decision allowed generation.
Keep consent evidence outside prompt text, support withdrawal of consent for future use, restrict impersonation and retain an auditable decision record.
Related page →Review model inputs, examples and current pricing, then check the estimate for your actual settings before you run.
