Ablo is a state control API for AI agents and collaborative apps. It gives agents a narrow way to write production state: declare models, load current state, coordinate active work, and write with stale-state checks. Capabilities, tasks, commits, and receipts are the protocol underneath, not first-integration ceremony. Multiplayer is not a separate product mode. If humans, server actions, and agents use the sameDocumentation Index
Fetch the complete documentation index at: https://docs.abloatai.com/llms.txt
Use this file to discover all available pages before exploring further.
Ablo({ schema, apiKey }) client and write through
ablo.<model>, Ablo fans out confirmed deltas, exposes active intents, and
rejects stale writes for every participant.
Start here
- Quickstart — Make your first schema-backed write.
- Integration Guide — Choose Ablo-managed state, Data Source, React, multiplayer, and agent patterns.
- Guarantees — What confirmed writes, stale checks, and intents guarantee.
- Interaction Model — The commit plane and control plane.
- API Reference — Resource-by-resource method shape.
- Client Behavior — Options, errors, retries, timeouts, and imports.
- Connect Your Database — Keep canonical rows in your app database without giving Ablo database credentials.
- API Keys — Bearer tokens for the public API.
API shape
| Plane | Primitives | Purpose |
|---|---|---|
| State | Schema, Model, Intent, Receipt | The product path. Load, coordinate, write, confirm. |
| Commit | Resource, Commit | Advanced protocol path for custom runtimes and batches. |
| Control | Capability, Task, Usage | The authority path. Scope, attribute, meter, audit. |
| Storage | Managed State, Data Source | Ablo stores declared models by default; existing app tables use a signed Data Source. |
Use cases
- Let agents write to shared state — Give an AI agent scoped, revocable write access to your typed data.
- Coordinate multiple actors — Use intents to broadcast pre-write declarations across humans and agents.
- Audit every agent action — Trace any write back to a human in one query.
- Build collaborative editors — Humans and agents on the same record, with realtime updates and stale-read protection.
- Meter and gate API usage — Per-key, per-team usage reports and quota enforcement.
- Integrate with A2A and MCP — Speak the same protocols as Claude, Cursor, Gemini.
Concepts
- Model Methods — Load and write typed state.
- Integration Guide — The normal app path and optional pieces.
- Guarantees — Confirmed writes, optimistic state, stale-write protection, and agent lifecycle.
- Intent — Broadcast proposed work before committing.
- Advanced Commit API — Apply custom batch mutations.
- Connect Your Database — Where data lands when your app database is canonical.
- Receipt — Confirm what landed.
- Capability — Signed credentials for a bounded actor, operation set, sync group, and lease.
- Task — One agent run; the audit envelope for commits and cost.
- Usage — Metering and audit dimensions.
Examples
- AI SDK Tool — Put Ablo inside an AI SDK tool call.
- Existing Python Backend — Add multiplayer and future agent writes without replacing a Python API server.
- Agent + Human — Yield when a human is editing the same task.
- Server Agent — Schema-backed worker plus advanced schema-less run.
- Next.js — App-router setup with React bindings.
Runtime builds
@abloatai/ablo— schema-powered sync client for typed model operations, realtime, intents, and receipts.Ablo({ apiKey })— advanced resource client for runtimes that intentionally cannot import a schema.