What authentication does the Idomoo Personalized Video API use?

The Idomoo API uses an API key passed in the Authorization header. Keys are issued from the Idomoo studio and scope all storyboard and render operations to the account. Through Jentic, the key is stored encrypted in your Jentic One instance and injected at execution time, so it never enters the agent's prompt context.

Can I generate videos for many recipients in one call?

Yes. POST /storyboard/batch accepts a list of recipient payloads and queues a separate render per recipient. The response includes a video ID per recipient that you poll via GET /video/{video_id}/status until the render completes. Use this endpoint instead of looping over /storyboard/generate for any campaign above a handful of recipients.

What are the rate limits for the Idomoo Personalized Video API?

Idomoo applies per-account rate limits and a render-minutes quota tied to your subscription tier. The OpenAPI spec does not encode hard thresholds. Build agents to handle 429 responses with backoff and to use /storyboard/batch for bulk renders rather than firing many /storyboard/generate calls in parallel.

How do I generate a personalised video through Jentic?

Run pip install jentic and import the SDK, then await client.search('generate a personalised video') to find the Idomoo /storyboard/generate operation. Load the schema and execute it with the storyboard ID and placeholder values, then poll /video/{video_id}/status. Run Jentic One, the self-hosted execution layer, for an API key.

How do I check my account's remaining render capacity?

Call GET /metadata/account to retrieve account-level metadata that includes the remaining render budget and billing context. This is useful for agents that want to short-circuit large batches when the account is approaching its monthly cap.

Can I limit what my agent is allowed to do with the Idomoo Personalized Video API?

Yes. Because you run Jentic One yourself, your own rules decide which Idomoo operations and credentials the agent may use. Idomoo puts video and storyboard IDs in the URL path, such as GET /video/{video_id}/status and GET /metadata/storyboards/{storyboard_id}, so a rule can pin the agent to reading the status and metadata of a single video or storyboard. You pick the operations it can call, so rendering with POST /storyboard/generate or POST /storyboard/batch stays off unless you add it.