What authentication does the All-Images.ai API use?

Every call requires an X-API-Key header. Through Jentic, the key is stored in the encrypted vault and injected at execution time, so it never appears in agent prompts or logs.

Can I generate an image and get the URL in a single call?

No. Generation is asynchronous: POST /v1/images/generate returns an imageId, and you poll GET /v1/images/{imageId} until the rendered URL is available. Plan for retry logic in the calling code.

How do I generate an image via the All-Images.ai API through Jentic?

Run pip install jentic, then in code search for 'generate an AI image', load the input schema for POST /v1/images/generate, execute with your prompt, and poll the returned imageId via GET /v1/images/{imageId} until complete.

What are the rate limits for the All-Images.ai API?

The OpenAPI spec does not declare explicit rate limits. Treat the asynchronous job model as the throttle and design polling intervals (e.g. 5 seconds) to avoid spamming the retrieval endpoint.

Can I retrieve an image after the original job has finished?

Yes. GET /v1/images/{imageId} returns the image record including the rendered URL as long as the imageId is known. Store the imageId from the generation response if you need to fetch the image later.

Can I limit what my agent is allowed to do with the All-Images.ai API?

Yes. Because you run Jentic One yourself, your own rules decide which of the two All-Images.ai operations the agent may call, so you can grant it only POST /v1/images/generate to start a render, only GET /v1/images/{imageId} to fetch a finished image by id, or both. You also control which stored credential the agent uses, so a read-only agent can retrieve images without ever being able to start new generation jobs. Nothing is callable unless you explicitly allow it.