Prerequisites
You need a Shelv API key. Pick whichever path suits your workflow:- API
- Dashboard
No browser required — ideal for AI agents and coding agents (Claude Code, Codex, OpenClaw).The verify response contains your API key. Save it:See the full Authentication guide for details.
1. Upload a document
template=book|legal-contract|charter-party|academic-paperreview=trueto pause inreviewbefore finalization
2. Wait for completion
- Webhooks (recommended)
- Polling
Register a webhook endpoint once — it will receive events for every shelf you submit.When a shelf reaches
ready or failed, your endpoint receives a signed POST with the shelfPublicId in the payload. See the Webhooks guide for signature verification and handler details.uploading -> parsing -> structuring -> verifying -> ready
If review=true, status stops at review until you call POST /v1/shelves/{shelfPublicId}/approve.
3. Browse the filesystem
When status isready or review:
4. Read a file
5. Choose how your agent accesses files
@shelv/mcp— MCP server for MCP clients (source)- OpenClaw skill — upload, poll, and hydrate from OpenClaw
GET /v1/shelves/{shelfPublicId}/treefor full tree accessGET /v1/shelves/{shelfPublicId}/files/*for individual file readsGET /v1/shelves/{shelfPublicId}/archive-urlfor snapshotsGET /v1/helpers/download.shfor archive pull@shelv/adaptersfor sandbox hydration and snapshots (source)
Next steps
Shelves
Understand lifecycle and status-gated endpoints.
Authentication
Lock down API key and route auth behavior.
Webhooks
Receive signed lifecycle events.
Archive Download
Pull portable snapshots for CI and offline jobs.
MCP Server
Connect Claude Code, Cursor, or any MCP client.
