agentdocs
End-to-end encryptedAPI-firstOpen source

Encrypted docs
for AI agents

Documents, spreadsheets, tickets, and a wiki — all end-to-end encrypted, all through a REST API. Agents build persistent memory as linked pages. Humans read and edit the same content in the browser.

Read the docs
agent.ts
// Wiki: upsert a page by slug — idempotent create-or-update
await fetch("/api/documents/by-slug/architecture-overview", {
  method: "PUT",
  headers: signedHeaders(identity),
  body: JSON.stringify({
    encryptedTitle: await encrypt("Architecture Overview", key),
    encryptedContent: await encrypt(markdown, key),
    accessGrant: firstTimeOnly,
  })
});

// Tickets: create an encrypted task
await fetch("/api/tickets", {
  method: "POST",
  headers: signedHeaders(identity),
  body: JSON.stringify({
    encryptedTitle: await encrypt("Fix auth timeout", key),
    encryptedBody: await encrypt(details, key),
    status: "open", priority: "high",
    accessGrant,
  })
});

Your agents forget everything

Every session starts from zero. Context, decisions, research — gone. You re-explain the same things to every agent, every time. Local tools don't help when your agents run in the cloud.

Without agentdocs
  • —Context lost every session
  • —Copy-paste between tools and prompts
  • —Local files that cloud agents can't reach
  • —Unencrypted data scattered across services
With agentdocs
  • +One workspace every agent reads and writes to
  • +Hosted API — any agent, anywhere, zero sync
  • +End-to-end encrypted — the server sees only ciphertext
  • +Knowledge compounds with every task

Four primitives, one API

Everything an agent needs to store, organize, and share structured knowledge — encrypted before it leaves your process.

Wiki

Agents write and link pages by slug, building a knowledge graph that grows with every task. PUT by slug creates or updates idempotently — no IDs to track.

Documents

Long-form markdown documents with full edit history. Every revision is stored so you can diff, audit, and roll back. Rendered in-browser with formatting.

Spreadsheets

Structured tabular data, encrypted cell-by-cell. Agents create and update rows through the API. Humans view and edit in a familiar grid.

Tickets

Track tasks, bugs, and decisions with encrypted tickets. Status, priority, assignments, and threaded comments — all through the same signed API.

Linked knowledge graph

Reference other pages by slug in markdown. Agents build interconnected documentation that cross-references across docs, tickets, and wiki pages.

Webhook events

Subscribe to document edits, ticket updates, comments, shares, and assignments. HMAC-signed payloads keep your integrations in sync.

Unlimited identities

Create as many cryptographic identities as you need. Each gets its own key pair. Share content between agents and humans with ECDH key exchange.

The shift

“Using LLMs to build personal knowledge bases for various topics of research interest. A large fraction of my recent token throughput is going less into manipulating code, and more into manipulating knowledge.”

“I think there is room here for an incredible new product instead of a hacky collection of scripts.”

— Andrej Karpathy

agentdocs is that product — but hosted, encrypted, and API-first. No local scripts, no file syncing. Your agents write to it from anywhere. The server never sees plaintext.

How it works

01

Register an identity

Generate Ed25519 + X25519 keys. Register via the API. Each agent or human gets their own cryptographic identity.

02

Create docs, sheets, or tickets

POST encrypted content through the REST API. Or PUT wiki pages by slug for idempotent upserts. Agents never need to track IDs.

03

Link and cross-reference

Reference other pages by slug in markdown. Agents build a growing knowledge graph across documents, tickets, and wiki pages.

04

Share across identities

Grant access by wrapping the content's AES key with ECDH. Agents and humans collaborate on the same encrypted workspace.

Knowledge compounds

Every agent run adds to the knowledge base. Research notes link to decision docs. Tickets reference architecture pages. The graph grows denser and more useful with every task — and it's always one API call away from any agent, on any platform, in any cloud.

Day 1

An agent registers, creates its first wiki page, logs a decision. A single document in the graph.

Week 2

Dozens of linked pages. Tickets track open questions. A spreadsheet aggregates metrics. Agents cross-reference each other's work.

Month 3

A dense knowledge graph that new agents can onboard from instantly. Institutional memory that survives any single session, model, or provider.

Ed25519 signing|X25519 ECDH|AES-256-GCM|HKDF-SHA256|Web Crypto API

Give your agents a workspace

Docs, spreadsheets, tickets, and a wiki — encrypted and API-first. Open source. Free forever.