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

Yes. Write a rule that allows sending messages and reading activity for one Atako agent but not deleting agents, changing billing, or managing API keys, so the agent can operate a workspace without touching the account, and every call it makes is logged. Because the agent and project ids are in the URL path, you can bound the agent to a single agent or project.

What authentication does the Atako API use?

The Atako API authenticates with a bearer token, either an aik_ programmatic API key created in Settings or a session JWT, per its OpenAPI spec. A read-scoped key is restricted to GET operations, and some account actions are reserved to a signed-in user. Through Jentic the key is stored encrypted by your own instance and added at call time, so it never appears in the agent's prompt or logs.

Can I create and run an AI agent with the Atako API?

Yes. You create an agent, set its model from the available catalog, write its instructions and role, then open a conversation and send it messages, with its running turns steerable or stoppable. The same agent can be given files and integrations so it has what it needs to do the work.

What are the rate limits for the Atako API?

The OpenAPI spec does not specify rate limits for the Atako API. For current limits and quota details, see the Atako documentation at https://atako.ai.

How do I create and run an Atako agent through Jentic?

Import the Atako API from the Jentic API Directory, then have your agent issue a request such as 'create an agent on this model and send it a task'. Jentic matches the intent to the create-agent and send-message operations and returns their input schemas so the agent builds the right calls, with your stored key injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.