Why Zaps
Redis was designed for caches. Zaps was designed for agents. The difference shows up the moment you give a thousand independent actors shared write access — Redis becomes a debugging nightmare; Zaps stays auditable, scoped, and predictable.
Documentationv0.1.0 · April 2026
Build with Zaps.
Ship in an afternoon.
Pick a language, copy the install command, follow the quickstart. Need depth? Concepts explain the architecture; guides cover the patterns enterprise teams reach for; the API reference is generated from a single OpenAPI spec.
InstallPick your stack
Browse6 sections · 29 pages
Getting Started
2 pagesConcepts
7 pages- 01ArchitectureFive layers, one port, three engines. The shape of the system.→
- 02Identity & authW3C DIDs at the wire. Scope checks at the edge. No anonymous code path.→
- 03Purpose databasesSeven workload-shaped profiles: agent-memory, cache, session, queue, …→
- 04Audit chainHash-chained BLAKE3 log of every mutation. Tamper-evident. Exportable.→
- 05Realtime subscriptionsWebSocket key-change events scoped per principal. Sub-millisecond fan-out.→
- 06Multi-tenancyKeyspace isolation enforced at the protocol layer.→
- 07SLA & reliability99.99% on Bolt and above. Hot-swap engines. Crash-recovery in 50–500ms.→
Guides
8 pages- 01AuthenticationAPI keys, OAuth 2.0 client credentials, JWT, mTLS.→
- 02WebhooksSetup, signature verification, retry behaviour, event catalog.→
- 03Error handlingExponential backoff, idempotency keys, retryable vs. terminal errors.→
- 04PaginationCursor-based and offset patterns. Auto-pagination iterators.→
- 05Rate limitingPer-tier limits, headers, automatic throttling.→
- 06TestingSandbox env, mock clients, recorded HTTP interaction replay.→
- 07Security best practicesCredential management, least privilege, audit logging.→
- 08Production readinessThe checklist enterprise teams use before go-live.→
SDKs
5 pagesAPI Reference
6 pages- 01IntroductionREST conventions, base URL, authentication, error envelope.→
- 02AuthenticationBearer tokens, OAuth flows, mTLS pinning.→
- 03ErrorsEvery error code the API can return, with causes and fixes.→
- 04Rate limitsPer-tier quotas, headers, burst handling.→
- 05KeysGET, SET, DELETE, SCAN endpoints with examples in 4 languages.→
- 06SubscriptionsSubscribe, unsubscribe, list. WebSocket and SSE.→
Concepts in briefEach section deep-links from the Concepts nav
Architecture
Five layers — Protocol, Edge, Engine, Persistence, Cross-cutting. One port handles RESP3, gRPC, and WebSocket. AkashaKV dual-mode storage powers the production path, with future adapters available behind the KvEngine trait.
Identity & auth
Every operation arrives with a verified W3C DID. Authorization runs at the edge, before the engine sees the request. There is no anonymous code path. API keys, OAuth 2.0 client credentials, JWT bearer, mTLS — all four are first-class.
Purpose databases
Seven workload-shaped profiles: agent-memory,cache, session,rate-limiter, queue,feature-flag, audit-log. Each ships engine, eviction, TTL, and replication defaults calibrated to its workload. You name what you're storing; Zaps picks the configuration.
Audit chain
Every write is captured in a tamper-evident BLAKE3 chain before it commits. The audit log is exportable as a single signed file with cryptographic proof of completeness.
Realtime subscriptions
WebSocket key-change subscriptions scoped per principal. Pattern matching with glob support. Sub-millisecond fan-out at 10,000 subscribers.
Multi-tenancy
Keyspace isolation is enforced at the protocol layer, not in application code. Agents cannot read other agents' keys — verified by the audit chain.
SLA & reliability
99.99% on Bolt and above. Engine hot-swap covers most outage classes. Crash recovery in 50–500ms via WAL replay on top of the latest snapshot.
Behind the docsWhat's powering this page
These pages are served by Next.js right now. The full Mintlify project lives in /zaps/mintlify-docs and is configured in mint.json with the Zaps brand already applied.
When the production Mintlify origin is configured (set theZAPS_DOCS_HOST environment variable and rebuild),/docs/* traffic on this domain proxies through to Mintlify automatically. URL slugs are kept identical between this page and mint.json so links keep working.
Owners by section are tracked in mintlify-docs/README.md. Quarterly audits against the SDK & Documentation mandate (April 2026) are the responsibility of those owners.
Spot something missing or wrong? File an issue at github.com/l1feai/zaps/issues — triaged within one business day.