Can I limit what my agent is allowed to do with DocsAutomator?

Yes. Write a rule that allows the create-document and list-automation operations but not automation deletion or signing-session cancellation, so the agent can produce documents and read signing status while changes to your automations and live signatures stay with you, and every call it makes is logged.

What authentication does the DocsAutomator API use?

Per its OpenAPI spec, the DocsAutomator API uses a bearer API key from your workspace settings, passed either as an Authorization Bearer header or an X-API-Key header. Through Jentic the key is stored encrypted by your own Jentic One instance and injected only at call time, so it never sits in the agent's prompt or logs.

Can I generate a document from a template with the DocsAutomator API?

Yes. The create-document operation merges your data into a template and returns a job, and the job-status operation reports when the generated document is ready. You can list a template's placeholders first so the data payload matches the fields the template expects.

What are the rate limits for the DocsAutomator API?

The OpenAPI spec does not specify request-rate limits; generation runs through a queue, and the queue-statistics operation reports its current state so you can pace batch jobs. Check docsautomator.co for current limits and plan details.

How do I generate a document with the DocsAutomator API through Jentic?

List the template's placeholders, build the matching data payload, call create-document, and poll the job id until the document is ready. In Jentic, search for 'generate a document from a template', store your API key once, and the agent runs the sequence. To run it on your own infrastructure, install Jentic One from its GitHub repo.