# file.rocks docs

The storage API agents can install in one click — and humans can read without squinting.

file.rocks exposes a scoped REST API and a production [MCP](/docs/mcp) server over the same workspaces, buckets, and intelligence features you use in the product.

## Prefer MCP in agents

If you're wiring Cursor, Claude, or another MCP client, start here:

1. [Create an API key](/docs/api-keys) with the scopes you need
2. [Install the MCP server](/docs/mcp/install)
3. Call tools like `list_buckets`, `search_files`, and `ask_agent`

Use [REST](/docs/api) when you need raw HTTP, scripts, or non-MCP runtimes.

## Start here

| Path | For |
|------|-----|
| [Quickstart](/docs/quickstart) | Key → first list/search |
| [Concepts](/docs/concepts) | Workspaces, buckets, files, intelligence |
| [API overview](/docs/api) | Full REST map |
| [MCP overview](/docs/mcp) | Tools, auth, install |

## Agent discovery

Every page has a markdown twin: append `.md` (for example [/docs/api.md](/docs/api.md)).

- Site map: [/llms.txt](/llms.txt) · [/docs/llms.txt](/docs/llms.txt)
- CORS on markdown: `Access-Control-Allow-Origin: *`

## Dogfood note

API keys, intelligence, and MCP are gated to the intelligence dogfood allowlist (`@terrible.app` and explicit allowlists). The product UI for keys only appears when your account qualifies.