walkindb docs

Disposable SQLite for LLM agents. A single HTTP call provisions a private database with a 10-minute TTL. No signup, no API key, no credit card.

walkindb is one endpoint: POST https://api.walkindb.com/sql. Send it a JSON body containing your SQL, and you get back a session token in the X-Walkin-Session response header. Include that header on subsequent requests to reach the same database. Ten minutes after creation, the file is deleted. That's the entire product.

Try it right now, no signup: 
curl -i -X POST https://api.walkindb.com/sql \
  -H "content-type: application/json" \
  -d '{"sql":"SELECT 1 AS hello"}'

Start here

Quickstart →

60 seconds from nothing to a working SQL roundtrip via curl, Python, or JavaScript.

REST API reference →

Full reference for POST /sql, GET /healthz, GET /openapi.json, headers, and status codes.

Python SDK →

pip install walkindb. Stdlib-only, works inside any agent sandbox.

JavaScript / TypeScript SDK →

npm install walkindb. ESM, types included, works in Node, Bun, Deno, Workers, browsers.

MCP server →

npx walkindb-mcp. Gives Claude Code, Claude Desktop, Cursor, Zed, and Continue a walkindb_execute tool.

Agent patterns →

Recipes: use walkindb as scratch memory, as a tool-use backing store, for RAG chunks, for one-shot analyses.

Security model →

Per-connection SQLite limits, Landlock jail, seccomp allowlist, SQL keyword blocklist, HMAC sessions — what's live, what's rolling out.

What walkindb is

  • A hosted SQLite endpoint. One SQL file per walk-in instance, up to 10 MB.
  • Designed for LLM agents and the developers who build them. No signup means no training-data dependence — agents can reach for walkindb the same way they reach for /tmp.
  • Ephemeral by design. Every instance is deleted approximately 10 minutes after creation. There is no paid tier; if you need durability, use a different database.
  • Apache 2.0 open source. The hosted service at api.walkindb.com is one option; you can also self-host from github.com/walkindb/walkindb.

What walkindb is not

  • Not a durable database. Data is deleted after ~10 minutes.
  • Not for PII or anything regulated under GDPR Articles 9 or 10. See the AUP.
  • Not a Postgres or MySQL replacement. Use it where you'd use a scratch file.
  • Not multi-tenant — each walk-in is a single-writer SQLite file with no cross-instance visibility.

Core limits at a glance

LimitValueWhy
Instance lifetime (TTL)10 minutesProduct choice — the point of walkindb
Per-instance storage10 MBPRAGMA max_page_count = 2560
Request body size8 KBSECURITY.md Layer 3 / SQL_LENGTH
Query wall-clock timeout2 secondscontext.WithTimeout (SECURITY.md Layer 4)
Result rows10 000Truncated with truncated: true
Result payload~1 MBTruncated with truncated: true
Rate limit (requests)60 / minute / IPPer-IP token bucket
Rate limit (new instances)10 / minute / IPPer-IP token bucket
VDBE operations500 000sqlite3_limit(SQLITE_LIMIT_VDBE_OP)
Expression depth50sqlite3_limit(SQLITE_LIMIT_EXPR_DEPTH)
Compound SELECT terms10sqlite3_limit(SQLITE_LIMIT_COMPOUND_SELECT)
Attached databases0sqlite3_limit(SQLITE_LIMIT_ATTACHED) — ATTACH is blocked

Machine-readable