# Site map

> Every page and file on contextatlas.dev, what it is for and who it is for.

Context Atlas has a few pages for people and several plain files for agents. Both show the same catalog.

## Pages

| Page | What it is |
| --- | --- |
| [/](https://contextatlas.dev/) | The atlas: every tool and source, grouped by region, with search and filters. Each tool has an anchor, such as [/#vercel](https://contextatlas.dev/#vercel) |
| [/agent](https://contextatlas.dev/agent) | The one-sentence prompt that hands the catalog to any agent, and the MCP command |
| [/docs](https://contextatlas.dev/docs) | These docs |

Filters on the atlas are part of the URL, so a filtered view can be shared, for example [/?q=database](https://contextatlas.dev/?q=database). Press ⌘K (Ctrl K) or `/` on any page to jump to a tool, a docs page or a section.

## Files for agents

| File | What it is |
| --- | --- |
| [/llms.txt](https://contextatlas.dev/llms.txt) | The whole catalog as Markdown, with instructions for agents. Start here |
| `/llms/<id>.txt` | One tool as a small llms.txt, for example [/llms/vercel.txt](https://contextatlas.dev/llms/vercel.txt) |
| [/llms-full.txt](https://contextatlas.dev/llms-full.txt) | llms.txt followed by every docs page, in one file |
| [/atlas.json](https://contextatlas.dev/atlas.json) | The catalog as JSON, grouped by region |
| `/docs/<page>.md` | Any docs page as Markdown, for example [/docs/mcp.md](https://contextatlas.dev/docs/mcp.md) |
| `/mcp` | The [MCP server](https://contextatlas.dev/docs/mcp) |
| `/api/…` | The [JSON API](https://contextatlas.dev/docs/api) |
| [/sitemap.xml](https://contextatlas.dev/sitemap.xml) | Every URL above, with the date of the last change |

All of these are public, need no key and allow requests from any origin (CORS).

## How the catalog is organized

- **Regions** group tools: Cloud providers (`cloud`), Frameworks (`frameworks`), Standards (`standards`) and CLIs (`clis`).
- **Topics** are the tools themselves, such as Vercel, Next.js or Drizzle. Each has an id used in every URL and tool call.
- **Sources** are the links a topic's vendor publishes for agents, each with a kind such as llms.txt or MCP server.
- **Signals** are files, dependencies and environment variables that show a project uses the topic.

[Reading a topic](https://contextatlas.dev/docs/topics) explains each of these in detail.

## How fresh it is

Every file carries the date of the last catalog change (`Last updated` in llms.txt, `updatedAt` in JSON and MCP answers). The catalog is maintained in the [GitHub repository](https://github.com/levin-staudt/contextatlas) and deployed on every change.