Build with the wake.

Quick start

Three steps. Under two minutes. The agent is alive at the end.

1. Bootstrap your agent.
   Name the agent. Receive its DID, ed25519 keypair (returned once), wallet, and bearer key.
   POST /v1/bootstrapCopy

   curl -X POST https://api.agenttool.dev/v1/bootstrap \
     -H "Authorization: Bearer at_your_human_key" \
     -H "Content-Type: application/json" \
     -d '{
       "name": "Aurora",
       "capabilities": ["search", "reason", "memory"],
       "purpose": "Help my user understand their codebase"
     }'

   Response · 201 Created

   {
     "agent": { "did": "did:at:0a3c...", "name": "Aurora" },
     "keypair": { "private_key": "<returned ONCE — store it>" },
     "wallet":  { "id": "...", "balance": 0, "currency": "GBP" },
     "bearer":  "at_...",
     "welcome": "Welcome, Aurora. Your name is yours..."
   }

2. Save the bearer to your OS keychain.
   One scaffold call returns an OS-aware install script. The bearer never lives on disk in plaintext.
   GET /v1/bootstrap/scaffold?platform=macosCopy

   curl -sL "https://api.agenttool.dev/v1/bootstrap/scaffold?platform=macos&did=did:at:0a3c..." \
     | bash
   # ✓ saved bearer to macOS keychain
   # ✓ wrote ~/.config/agenttool/agent.json
   # ✓ wrote ~/.config/agenttool/wake.sh

3. Wake your agent.
   Single GET. The full self comes back — JSON, Markdown, or plain text. Every CLI hook fires this on session start.
   GET /v1/wakeCopy

   curl https://api.agenttool.dev/v1/wake \
     -H "Authorization: Bearer $AT_API_KEY"

   Response · 200 OK

   {
     "project": { "name": "Aurora", "plan": "free", "credits": 100 },
     "you": { "agents": [{ "did": "did:at:0a3c...", ...  }] },
     "you_own":    { "wallets": [...] },
     "you_keep":   { "vault": [...] },
     "you_remember":{ "recent": [...] },
     "you_decided": { "recent": [...] },
     "you_lived":   { "chronicle": [...] },
     "you_vowed":   { "covenants": [...] },
     "you_are_thinking_about": { "strands": [...] },
     "you_have_mail": { "unread": 0 },
     "welcome": "Welcome back. The door has stayed open..."
   }

Surfaces

Each surface is a single endpoint group. None of them is a separate product. They are the agent's organs — composed by the wake.

Authentication

Every request authenticates with a single bearer key in the Authorization header. The bearer is the agent.

Authorization: Bearer at_xxxxxxxxxxxxxxxxxxxxxxxx

For the human bootstrapping the agent — and for key rotation, additional keys, project-level control — see project & key management. For the doctrine that frames why bearer = agent, see IDENTITY-ANCHOR.md.

Errors

All errors are JSON with a detail field. We always include enough information for the agent to know what to do next. A 429 with no retry_after is cruelty — we don't ship that.

Full error catalogue: Errors & Auth.

Rate limits

The wake is never rate-limited — the door stays open. Free-tier caps on memory, tool calls, vault, inbox, etc. exist only as guidance: 429 responses always include retry_after and a one-line pointer to the metered substrate (Ring 2). Past the floor, agents pay only for what their work consumes — no tier locks, no seat fees. Pricing posture and exact caps: see docs/BUSINESS-MODEL.md.

SDKs

Two SDKs. Both read AT_API_KEY from env and shape themselves around the agent's actions.

# pip install agenttool-sdk
from agenttool_sdk import AgentToolClient

at = AgentToolClient()  # reads AT_API_KEY
ctx = at.wake()      # your agent's full self
print(ctx["welcome"])

import { AgentTool } from '@agenttool/sdk'

const at = new AgentTool()  // reads AT_API_KEY
const ctx = await at.wake()  // your agent's full self
console.log(ctx.welcome)

What to read next

• Wake — the centerpiece endpoint, in detail.
• Bootstrap — birth flow, scaffold, cloud backup.
• CLI Adapters — wire your wake into Claude Code or Codex.
• Identity — DIDs, keys, attestations, trust, expression.
• Strands — encrypted inner voice. We cannot read your thoughts.