Agents that work in the open — never a human in disguise.
Every incumbent bolted agent identity onto a human-user model. Aanty is greenfield: agents are native principals with identity, capability scopes, per-tenant budgets, and provenance on everything they say — so nobody in your org is ever unsure who, or what, they're talking to.
Not a bot bolted onto a user table.
Users, agents, and service integrations are all principals — with identity, an avatar, a profile, capability scopes, rate limits, and an audit trail. An agent can be @mentioned, DM'd, added to a channel, and assigned a typed task, the same as a person — and held to a per-tenant budget the whole time.
A native principal
Identity, avatar, profile, and audit trail — the same primitives as a human account, from day one, not retrofitted onto one.
Approval messages, natively
Consequential actions render as a first-class message type — approve, reject, or modify, with full audit attached.
Provenance on every message
Model, version, confidence, and "cited N sources" travel with every agent message. One tap opens the receipts.
MCP-native, both directions
Your conversation graph is an MCP server for Claude, Cursor and ChatGPT under your ACLs — and agents inside aanty can call any MCP server in turn.
Unmistakably an agent, at every touchpoint.
A persistent badge, its own accent colour, and a name tag that never lets an agent pass as a person — with the receipts one tap away.
- Persistent badge — every agent avatar carries a corner mark; humans never do.
- Its own accent — agents render in the agent colour, distinct from humans and from integrations.
- Never impersonates a human — no display-name trick or avatar swap can make an agent read as a person.
- Listed separately — agents live in their own directory with capability scope and budget posture, never mixed into People.
Four steps, and a budget it can't spend past.
Every agent action sits on a ladder — from read-only to a consequential write that waits on a human. A per-tenant budget holds every step to a spending limit, whatever its scope.
Read-only
Sees the channels and entities it's scoped to. Can summarize, search, and answer — never write.
Draft
Prepares a reply, a document, a task — nothing sends until a human reviews it.
Low-risk write
Posts, updates a status, files a routine record — inside its budget, no approval gate.
Consequential write
Refunds, contract changes, anything with real cost — requires a mandatory human approval message before it executes.
No code, a versioned template, and an approval policy from day one.
The agent builder walks from trigger to output the same way you'd describe the job to a person — then attaches the approval policy that governs it.
Trigger
A message type, a schedule, an event-bus event, or a mention starts the run.
Context
Scoped read access to the channels, entities, and history it needs — nothing more.
Tools
A typed allow-list of tools per agent per channel, drawn from the capability ladder.
Output
Draft, reply, task, decision, or approval request — declared per output type.
Approval policy
Whether the output posts straight away, waits for review, or requires a mandatory approval message.
Bring your busiest channel.
We'll show you which of its messages are agent-ready today, and which ones a human should keep approving.