Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / AI/ML / Atako API
Atako API logo

Atako API

50
AI ReadinessNon-Ready (C-)50/100
See full scorecard
Official vendor OpenAPI document · agent-readyAI/MLLanguage Modelsbearer274 EndpointsREST

For Agents

Create AI agents, choose their model, write their instructions, chat with them, and grant them files and integrations. Authenticates with a bearer token, either an aik_ API key or a session JWT.

Use for: Create a new AI agent and set its model, Send a message to one of my agents, Stop an agent's current turn, Grant a file to an agent

Not supported: Does not train or host the underlying language models, run your own servers, or replace your LLM provider account. Use for creating, configuring, and operating Atako AI agents and their workspace only.

The Atako API creates and runs AI agents, letting you provision an agent, set the language model it runs on, write its instructions and role, and then chat with it over conversations and messages. Each agent can be given files from a company drive, connected to external API and tool integrations, placed on a team, and assigned work through projects, cards, and a wiki. The API also exposes the model catalog, bring-your-own LLM keys, billing and subscriptions, and a company dashboard with an audit log of what every agent did.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the Atako API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Atako API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

1

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fatako.ai%2Fatako" | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fatako.ai%2Fatako" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Atako API.

Create and provision AI agents and set their model, role, and instructions

Open conversations with an agent and send it chat messages

Steer or stop an agent's running turn and read its live activity

Give an agent files from a company drive through file grants

Connect external API and tool integrations and grant them to an agent

Organize agents and people into teams, projects, and boards

Use Cases

Patterns agents use Atako API for, with concrete tasks.

★ Agent-of-Agents Orchestration

An AI agent connected through Jentic provisions an Atako agent, sets its model and instructions, opens a conversation, and sends it work, so one agent can stand up and supervise another. Because turns can be steered or stopped mid-run, the controlling agent can correct a task without waiting for it to finish.

Create an agent on a chosen model, write its instructions, then send it a first task message and read its reply

File-Grounded Agent Work

A team uploads documents to the company drive and grants specific files to an agent so it works only from approved material. File grants and the agent's dedicated folder keep the agent's working set explicit rather than giving it the whole drive.

Upload a document to the drive and grant it to this agent, then confirm the agent can read it

Integration-Connected Agents

An operator connects an external API or tool integration and grants it to an agent, so the agent can act in another system under a scoped grant. The integration grant can be updated or revoked, which keeps the agent's reach adjustable over time.

Connect an integration, grant it to the agent, and later revoke the grant on request

Key Endpoints

274 endpoints — the atako api creates and runs ai agents, letting you provision an agent, set the language model it runs on, write its instructions and role, and then chat with it over conversations and messages.

METHOD

PATH

DESCRIPTION

POST

/agents

Create an agent

GET

/agents

List your agents

POST

/agents/{agentId}/messages

Send a chat message to an agent

PATCH

/agents/{id}/model

Change a live agent's model

POST

/agents/{agentId}/file-grants

Grant files to an agent

GET

/models/catalog

List the available model catalog

POST

/agents

Create an agent

GET

/agents

List your agents

POST

/agents/{agentId}/messages

Send a chat message to an agent

PATCH

/agents/{id}/model

Change a live agent's model

POST

/agents/{agentId}/file-grants

Grant files to an agent

GET

/models/catalog

List the available model catalog

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

A

Atako API

- Non-Ready (C-)
50/100
40
Foundational Compliance
63
Developer Experience & Jentic Compatibility
50
AI-Readiness & Agent Experience
43
Agent Usability
60
Security
71
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
40

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: FSignals: 4
37%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

0%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

21%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

63

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

50

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: D+Signals: 4
43%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

56%

Summary Coverage

Coverage of summaries across operations/tags/info.

43

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: D-Signals: 1
43%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

60

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1
60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

71

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1
71%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Atako API by hand means minting an aik_ API key (or carrying a session JWT), learning which operations a read key cannot call, and sorting the public content endpoints from the authenticated ones. Through Jentic you install once, import Atako from the API Directory, store the key once, and your agent calls it.

Permission scoping

Atako puts the agent, project, and team ids in the URL path, so a rule can pin your agent to one Atako agent or project and let it send messages and read activity while leaving billing, API-key management, and account deletion out. You choose the operations it may call, so destructive ones like deleting an agent are not included unless you add them.

Credential isolation

Your Atako key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create an agent' or 'send a message to an agent', and Jentic returns the matching Atako operation with its input schema so the agent calls the right endpoint without reading the reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

CrewAI API

→

Framework and platform for orchestrating multi-agent AI crews

Choose CrewAI when you want to define multi-agent workflows in code rather than manage hosted agents through an API.

Alternative

Relevance AI API

→

Platform for building and running AI agents and agent teams

Choose Relevance AI when you want a different hosted agent platform with its own tool library.

Complementary

OpenAI API

→

Chat, embeddings, and model APIs for building on large language models

Choose this to supply the underlying language model an Atako agent runs on, using your own key.

FAQs

Specific to using Atako API through Jentic.

Is there an Atako MCP server?

Yes. Atako runs its own MCP server and can also connect external MCP servers as agent integrations. You can connect the Atako API directly through Jentic instead: your agent gets the full 274-endpoint surface without loading another server's tool definitions into its context, your key is injected at call time by your self-hosted instance instead of living in a config file, and your rules decide which operations the agent may call.

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.

GET STARTED

Start building with Atako API

Explore with Jentic One
View OpenAPI Document