SaaS and workflow integration
Connect i2v.ai generation to your backend or workflow with task ownership, a USD budget, and signed callbacks.
Choose your entry point
- Use the to generate media from a connected AI assistant.
- Use the for shell scripts and local project files.
- Use the when serving your own users. Start from the runnable examples for Node.js, Python, curl, Next.js, and n8n. A coding assistant can use the
i2v-integrateSkill to adapt these examples to your project.
Store one record for each operation
Keep the i2v.ai API key on the server. Authorize tenant access before quoting, submitting, cancelling, or querying a task. Record the tenant, stable operation key, approved USD amount, quoted revision, and exact submitted inputs. Save the returned task ID on that same record.
Use the for signed uploads and submission receipt recovery. Before issuing another generation request for a slow task, query the original task or receipt. When a task completes, validate ownership and copy the output to your own storage if it needs long-term access.
Receive a signed callback
Verify the exact raw request body before parsing it. Use the signing key selected by X-I2V-Key-ID and verify the timestamp and HMAC. Store processed event IDs and keep terminal job state when a duplicate or older event arrives. Use polling if callbacks are delayed. The describes the headers and event format.
Check cost and availability
Quote the actual inputs before approving the charge. Use a USD ceiling on submission and report the user's task ID after a wait expires. View available and reserved funds through the . Read settled charges and refunds through GET /api/v1/account/usage. The i2v.ai account that owns the API key pays for generated tasks.

