What authentication does the Narrato API use?

Narrato uses an API token sent in the Authorization HTTP header. When called through Jentic the token is encrypted in your Jentic One instance and the agent receives a scoped execution token; the raw Authorization value never enters the agent's context.

Can I create a content task with the Narrato API?

Yes. POST /create-task accepts metadata fields like brief, target keyword, word count, due date, and assignee, and creates the task in the chosen project or folder. Use POST /projects and POST /folders first if you need to scaffold the destination structure.

How do I update task status with the Narrato API?

Call PUT /task/update-meta-data with the task ID and the metadata fields you want to change, including the workflow status. Read the available statuses for the parent project first via GET /status to ensure the value you set is valid.

What are the rate limits for the Narrato API?

Narrato does not publish formal rate limits in the spec. Treat sequential project and task fetches as the heavy operations and add a small delay between requests when iterating across many workspaces. Cache GET /workspaces and GET /projects responses because they change infrequently within a session.

How do I create a Narrato content task through Jentic?

Run jentic.search('create content task in narrato'), load the POST /create-task operation, then jentic.execute with the task brief, target keyword, and project ID. Jentic injects the Authorization token from the vault and returns the created task ID for downstream automation.

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

Yes. Jentic One is self-hosted, so you run your own instance and your own rules decide which Narrato operations and credentials the agent can use. You can allow read-only calls such as GET /workspaces, GET /projects, and GET /tasks while withholding writes like POST /create-task, POST /projects, or PUT /task/update-meta-data. Because Narrato carries its targets in the request body and query rather than the URL path, the operator controls scope by choosing the operations the agent may call, and any operation you do not add stays off limits.