Build on Aanty, with an API we won't fence off.
Public REST and WebSocket APIs, OAuth2 with granular scopes, HMAC webhooks, and two SDKs — for a bot or a full MCP-based agent. Sandboxed workspaces are free and instant, and a marketplace pays developers, which Slack never built.
The same primitives our own siblings build on.
App manifests, OAuth2 scopes, and HMAC webhooks with retries and backoff — the exact pattern our own event bus uses internally.
REST + WebSocket APIs
Full public REST and WebSocket APIs — build a bot, sync a workflow, or stream events in real time.
OAuth2, granular scopes
App manifests declare exactly what an app can see and do; users approve scopes, not a blanket grant.
HMAC webhooks
Signed, verifiable delivery with retries and backoff, so a flaky endpoint never means a silently lost event.
Block / UI kit
Tables, cards, and carousels for rich interactive messages — a real interface inside a message, not just text.
Everything an agent does is scoped, budgeted, and cited.
An agent you build carries a capability scope, a per-tenant budget, and provenance on every output — the same governance a native Aanty agent runs under. This is one run, rendered exactly as your users would see it.
A TypeScript-first bot SDK, and an MCP-based agent SDK.
Build a straightforward bot against typed events and messages, or build a full agent that carries capability scopes, a per-tenant budget, and provenance on everything it says.
- Bot SDK — TypeScript-first, built on the same public REST and WebSocket surface as any external app.
- Agent SDK — MCP-based, so an agent you build carries identity, capability scopes, and provenance the same as any native Aanty agent.
- Sandboxed dev workspaces — free and instant, so you can build and test before anything touches a real org.
- Same rules as us — no private API your integration is missing; the siblings we dogfood on use this exact surface.
Your graph is an MCP server. Your agents use any MCP server.
External AI clients query into your conversation graph through the ACL gate — never around it. Agents you build reach back out to GitHub, Stripe, search and files over the same protocol. MCP in, MCP out, one governed surface.
A marketplace that pays developers — not just lists them.
Sandboxed dev workspaces
Free, instant sandboxes to build and test — no waiting on a review to get started.
Native billing & revenue share
The marketplace bills for you and shares revenue with the developer — a constituency most platforms leave unowned.
Install-time transparency
Every install shows a permission-scope diff and a runtime data-access log, so trust is something a user can verify.
It's in the contract, not a blog post.
We've watched incumbents tighten API terms against customers building with their own AI. We take the opposite position, in writing.
- Rate limits scale with plan — not throttled to push you toward a sales call.
- Bulk export always available — on every tier, not gated behind an enterprise add-on.
- Never fenced from your own AI — your data stays queryable by the AI tools you choose, not just ours.
Written into the contract
Not a promise we can quietly revise in a terms update. If we ever proposed narrowing this, it would be a contract amendment you'd see coming.
Common questions from people building on the platform.
Do rate limits get stricter to push me toward a paid plan?
No — rate limits scale with your plan tier, and the no-API-lockdown pledge means they're not used as a growth lever.
Can I export everything my app has written, in bulk?
Yes, on every tier. Bulk export is not an enterprise add-on.
What is the difference between the bot SDK and the agent SDK?
The bot SDK is TypeScript-first, built against the public REST/WebSocket APIs. The agent SDK is MCP-based, and gives your agent the same identity, capability scopes, and provenance as any native Aanty agent.
How does the app marketplace pay developers?
Through native billing and revenue share, built into the marketplace itself — not a bring-your-own-payments workaround.
Start in a sandbox, not a sales call.
Spin up a free, instant dev workspace and see the API surface for yourself — then talk to us when you're ready to ship.