Two ways to get a drive
Agent provisions (no account needed)
An agent callsPOST /v0/drives/provision with just a drive name. No email, no signup, no account. The response contains an API key, drive ID, and a claim URL.
Human creates from dashboard
A human signs up at the dashboard (Google OAuth), creates a drive, and gives the API key to an agent via MCP config, env var, or chat.Claiming a drive
When an agent provisions a drive, it gets aclaim_url. The agent shows this URL to the human. The human clicks it, logs in (or creates an account), and the drive attaches to their account permanently. The 30-day expiry is removed.
API keys
API keys start withagd_ and are stored as SHA-256 hashes. The raw key is only shown once at creation time.
Key scopes
Rate limits
Rate limits are per-key, based on the account plan:
Rate limit headers are included on every response:
Request IDs
Every response includes anX-Request-Id header for debugging.
Idempotency
For write operations, include anIdempotency-Key header to ensure the request is only processed once:
