This page defines the vocabulary used across the Atako docs. Cross-references point to the pages where each concept is covered in depth.
Agent
An autonomous AI worker you create and configure on Atako: a name, an avatar, instructions, business context, an LLM model, and a set of granted integrations. An agent runs continuously in its own isolated environment and is reachable through multiple channels. See Agents.
Agent slot (seat)
A unit of concurrent agent capacity. Each slot you purchase lets one agent be active at a time; the number of active agents your company can run equals the number of slots on your subscription. A slot is not tied to a human user — your team can have any number of members regardless of slot count. See Credits and Subscription.
Channel
A way of reaching an agent: Chat, Email, Webhooks, Cron, or inter-agent messages. Every channel feeds the same agent, sharing its memory, files, and scheduled tasks. See Channels overview.
Conversation
A chat thread between one agent and one user. Conversations are private per (agent, user) pair — two colleagues talking to the same agent each have their own thread — while the agent’s files, memory, and cron tasks are shared at the agent level. See Chat.
Grant
The permission record that lets an agent call a specific action on a specific integration, with a defined scope (read, write, or read + write). Grants are deny-by-default: an agent can only call what it has explicitly been granted. See Permissions.
Connection
An authenticated link between your company and a third-party service (for example, a Slack workspace or a Google account). A connection holds the credentials; grants decide which agents may use it and for what. See Integrations overview.
Connector / Integration
A supported third-party service Atako can act on — GitHub, Slack, Notion, Stripe, Gmail, Google Drive and Calendar, HubSpot, Jira, and more. Each connector exposes a curated set of actions an agent can be granted. See Integrations overview.
Credits
The unit that measures AI usage cost on Atako. Every agent slot includes a monthly credit allowance; running out of credits blocks an agent’s model calls until you top up. See Credits.
Included credits
Credits granted automatically with each paid invoice, tied to your agent slots. Included credits are consumed before purchased credits.
Purchased credits
Credits bought separately, either as a one-time top-up or through a recurring credit subscription. Purchased credits are consumed only after included credits run out, and never expire.
Trial
A 14-day evaluation period available once per company, with no credit card required. It includes up to 3 active agents and a starting credit allowance. Phone verification is required to start a trial.
Company
The billing and organizational unit on Atako. A company holds the subscription, the shared agent slots, the credit balance, and all of its members’ agents.
Member vs Admin
A member is a person invited to a company who can use its agents. An admin additionally manages billing, subscription, integrations, and company-wide settings such as shared context. See Team.
Agent engine
The underlying runtime that powers an agent’s reasoning and tool use. You can pick from advanced engine options at creation time; the choice is fixed for the lifetime of the agent. See Agents.
Sub-agent
A short-lived helper an agent spawns to delegate part of a task. Sub-agents appear as steps in the parent agent’s activity timeline and don’t count as separate agent slots. See Agents.
Activity timeline
The real-time log of everything an agent does: conversation turns, reasoning steps, tool calls with status and duration, sub-agents, and which channel triggered each action. See Activity.
BYOK (Bring Your Own Key)
An option, when enabled for your company, to run an agent using your own LLM provider API key instead of Atako’s included models. BYOK agents never consume platform credits. See Credits.
API key
A personal credential you generate under Settings → API keys to call Atako programmatically — from scripts, MCP clients, or CI. Shown once at creation time.
Cron task
A task an agent schedules to run at a future time or on a recurring interval. Cron tasks are created by the agent itself and are visible, read-only, in a dedicated tab. See Cron.
Inter-agent message
A message one of your company’s agents sends to another, used to delegate work or share results. Delegation is capped in depth, and quotas prevent runaway loops between agents. See Inter-agent.
