Overview

What AGNT is, how the platform is layered, the core terms, and the facts that apply to every API call.

AGNT is infrastructure for AI personal assistants: the layers an agent runtime leaves out. Your app calls one API, and each of your users gets an assistant with its own name, phone number and email inbox. The assistant talks over iMessage, SMS, WhatsApp, email and voice, works in a cloud computer of its own, remembers what matters, and carries long-running work to completion. Every consequential action (email, messages, calls, calendar changes, file sharing, actions in connected apps) can wait for a person's approval, set per user and per action type.

Coding agents can read /llms.txt, an index of every guide, or /docs.md, the full text of all guides plus an endpoint index in one file.

Use cases

You are building	What AGNT gives you
One branded assistant for consumers	Per-user isolation, an identity per assistant, messaging and voice, memory, durable tasks
An assistant feature inside an existing SaaS product	Users provisioned from your own sign-up, your brand on the assistant, approvals in your UI
A multi-tenant platform for businesses	Organizations and teams with their own admins, SSO and SCIM, autonomy policy per organization, audit history

OpenAssistant (openassistant.us) is a consumer assistant built entirely on AGNT.

How it works

Your app creates users, assistants, chats and tasks through the API. Prime, the agent harness, does the work. Anything that leaves the platform goes out through an assistant's own identity or a user's connected account, subject to that user's autonomy settings. Your app never calls a model directly.

 Your app (web, mobile, backend)
          |
          |  REST API  /  @agnt-sdk/client  /  agnt CLI
          v
 +-----------------------------------------------------------------+
 |  AGNT API  (https://api.agnt.ai)                                 |
 |    authentication, tenancy and per-user isolation on every call  |
 +-----------------------------------------------------------------+
          |
          v
 +-----------------------------------------------------------------+
 |  Prime, the agent harness                                        |
 |    runs every chat turn and every task, for every user           |
 +-----------------------------------------------------------------+
          |
          v
 +---------------------+---------------------+---------------------+
 | Identity and        | Voice               | Workspace           |
 | messaging           |   phone calls,      |   per-user cloud    |
 |   name, number,     |   live voice        |   computer: browser,|
 |   inbox, channels   |                     |   desktop, shell    |
 +---------------------+---------------------+---------------------+
 | Memory and context  | Tasks               | Tenancy and         |
 |   long-term memory, |   durable, async,   | approvals           |
 |   contacts,         |   long-running work |   orgs, teams,      |
 |   calendars         |                     |   autonomy, approval|
 +---------------------+---------------------+---------------------+
          |
          v
 The outside world
   phone networks (SMS, iMessage, WhatsApp, calls)
   email inboxes
   the web
   your users' connected Google and Microsoft accounts

Prime is model-agnostic: each model tier can be served by models from several providers, including open-weight models, and you change this without a code change. See Prime: the harness.

Core terms

Term	Meaning
Account	Your app on AGNT. One account holds all of its end users, organizations and settings.
Organization	A customer company inside your account, with its own admins, domains, SSO and policy. Optional.
Team	A group of users inside an account or organization. Provisioning places each user on a team.
User	One of your end users. All user data (tasks, chats, memories, contacts, files) is isolated from every other user.
Assistant	An agent with its own name, email address and, optionally, phone number and voice. A user has a roster of assistants and one primary.
Chat	A conversation thread between a user and an assistant.
Task	A durable unit of work. It survives restarts, waits on people for days if needed, and resumes where it left off.
Run	One execution of a chat turn or a task by Prime. A task usually has many runs.
Approval	A consequential action waiting for a person to approve it. The API calls a batch of pending actions a cart.
Skill	A packaged capability Prime can use: instructions, knowledge, tools or an MCP server.
Workspace	The per-user cloud computer (browser, desktop, shell) Prime works in.
Autonomy settings	Per user, one approval mode for each action type: `auto`, `time-boxed` (runs after a review window) or `manual` (waits for approval). Admins can lock them.
Hosted app	The white-label end-user web app AGNT serves for your account on an AGNT subdomain or your custom domain. Users sign in, approve actions and take over their workspace there. Optional: the API supports the same flows in your own app.
Memory	A fact Prime keeps about a user and uses on every run.
Prime	AGNT's agent harness: the runtime that executes every chat turn and task. Invisible to your end users.
Model tier	`low`, `medium`, `high` or `ultra`. Work is routed by tier, never by a hard-coded model.

Account and user resources

Kind	Examples	How to call
Account resources	Users, teams, organizations, assistants, skills, settings	An account API key, no user context
User resources	Tasks, chats, memories, contacts, calendars, approvals	An API key plus `X-User-Email: <user's email>`

Isolation is between users. Each user resource belongs to exactly one user, and a user-scoped key acts only as its own user for approvals and edits. Work that acts for someone, such as creating a task for Jane Rivera, names the user with X-User-Email: [email protected]. An email that matches no user in your account fails with 401 and never falls back to account-wide access.

An account key is your server's trusted credential. Without X-User-Email it can also list, read and delete tasks and chats across all of your users, for support and admin tooling. Keep account keys on your servers. See What each credential can do.

Platform facts

Fact	Value
Base URL	`https://api.agnt.ai`
Auth	`Authorization: Bearer ak_live_...` (an API key) or a certificate JWT (the SDK). Add `X-User-Email` to act as one of your users. See Authentication.
Requests	JSON bodies, sent with `Content-Type: application/json`
Pagination	Most lists take `page` and `perPage` (default 20, max 100) and return `page`, `perPage` and `total`. Timelines, such as a task's activities, take `limit` and a `before` cursor and return `hasMore` and `cursor`. `GET /skills` takes `page` and `limit` (default 50, max 200). Call history and workspace snapshots take `limit`. SCIM uses `startIndex` and `count`. The API reference lists each endpoint's parameters.
Errors	`{ "status": 404, "error_code": "not_found", "error": "Task not found" }`. An invalid API key returns `401` with `{ "ok": false, "error": "Invalid or expired API key" }`. A rate-limited request returns `429` with `{ "ok": false, "error": "Too many requests", "retryAfter": ... }`. See Errors.
Rate limits	Per account, client IP and path: 1,000 reads and 50 writes a minute by default. A limited request returns `429` with `Retry-After`. See Rate limits.
Versioning	None. Paths carry no version prefix.
Compliance	SOC 2 Type II, audited annually. Contact [email protected] for the report. See Security.
Hosting	AWS, in the United States
Pricing	Usage is metered in credits, shown in the console.

Guides

Guide	Covers
Quickstart	From an API key to a finished task
Authentication	API keys, acting as a user, certificates, errors and rate limits
Prime: the harness	What Prime does, chats and tasks, memory and model tiers
Assistants and messaging	Assistant identities, email, SMS, iMessage, WhatsApp and voice
Computer use	The per-user workspace: browser, desktop, shell and handoff to a person
Tasks and approvals	Long-running work, autonomy, and approvals
Users, organizations and teams	Provisioning, organizations and teams, SSO, SCIM, audit export and admin policy
Security	Isolation, encryption, identity, audit and reporting
CLI and coding agents	The `agnt` CLI, and building with Claude Code, Codex or Cursor

The API reference documents every endpoint with request and response schemas.