What authentication does the Gamma API use?

Gamma uses an API key passed in the X-API-KEY header. When called through Jentic the key is stored encrypted in your Jentic One instance and injected at execution time, so the agent context never sees the raw secret.

Can I generate a presentation from a template with the Gamma API?

Yes. POST /generations/from-template accepts a template id with structured input fields, returning a generation job that you then poll at GET /generations/{id} until its status is complete.

How do I check whether a Gamma generation has finished?

Generation is asynchronous. After POST /generations returns the job id, call GET /generations/{id} on a polling interval (every few seconds is typical) and read the status field; the export URL is available once the job is complete.

What are the rate limits for the Gamma API?

Gamma's published OpenAPI does not declare formal rate-limit headers, so back off on HTTP 429 responses and check your workspace plan limits in the Gamma dashboard before scheduling high-volume generation jobs.

How do I generate a deck through Jentic?

Install with pip install jentic, search 'generate a presentation from text' to find the Gamma generation operation, load its schema, and execute with your inputText, numCards, and themeId. Jentic returns the export URL once the job is complete.

Can I limit what my agent is allowed to do with the Gamma API?

Yes. Because you self-host Jentic One, your own rules decide which Gamma operations and credentials the agent may use. Since Gamma puts the generation id in the URL path at /generations/{id}, you can pin the agent to reading one generation's status and nothing else, while leaving out starting a new generation via POST /generations, listing /themes, or browsing /folders. The agent can only call the operations you explicitly allow.