HTML returned; not a verified text file
https://www.sanity.io/llms-full.txt ↗- Discovery
- Conventional sibling path checked
- HTTP response
- 206 · text/html; charset=utf-8
Business platforms · llms.txt file breakdown
A directly retrieved Markdown index for Sanity's documentation, with 785 links across 13 detected headings.
The actual file
The saved llms.txt text, displayed as source. The file belongs to its publisher; the live endpoint may change.
Showing the first 18000 characters. Load the complete file to read the remainder.
# Sanity
> Sanity is the Content Operating System for the AI era. It gives teams a structured content backbone (Content Lake), a fully customizable editing environment (Sanity Studio), and APIs that power everything from websites to AI agents. Model content around how your business actually works, automate the repetitive stuff, and deliver to any channel from a single source of truth.
## Docs
- [Manage Sanity with code](https://www.sanity.io/docs/blueprints)
- [Introduction](https://www.sanity.io/docs/blueprints/blueprints-introduction): Learn what Blueprints are, how they work, and how to get started.
- [Stacks and scope](https://www.sanity.io/docs/blueprints/stacks-and-scope): How one blueprint file maps to many stacks, and what project versus organization scope means.
- [Manage environments with Blueprints](https://www.sanity.io/docs/blueprints/manage-environments): Deploy one blueprint file to staging, production, and other stacks.
- [The resource graph](https://www.sanity.io/docs/blueprints/resource-graph): How resources reference each other with the $ syntax, and why a blueprint file is a connected system.
- [Errors and rollbacks](https://www.sanity.io/docs/blueprints/errors-and-rollbacks): How Blueprints catches mistakes early and what happens when a deploy fails.
- [Your first Blueprint](https://www.sanity.io/docs/blueprints/your-first-blueprint): Set up a blueprint, run a plan, and deploy your first resource (a CORS origin) to a real Sanity stack.
- [Project layout and monorepos](https://www.sanity.io/docs/blueprints/project-layout-and-monorepos): Lay out a Sanity project so Blueprints, Functions, and your application code coexist cleanly in monorepos.
- [Promote a stack](https://www.sanity.io/docs/blueprints/promote-stack-to-organization-scope): Learn how to promote an existing project-scoped blueprint stack to organization scope to unlock scheduled functions.
- [Manage stacks](https://www.sanity.io/docs/blueprints/manage-stacks): List your Blueprints stacks, see which stack your local blueprint deploys to, and remove stacks you no longer need.
- [Deploy from CI](https://www.sanity.io/docs/blueprints/deploy-blueprints-from-ci): How to deploy your Blueprint automatically from any CI system using a deploy token and environment variables.
- [Deploy with GitHub Actions](https://www.sanity.io/docs/blueprints/blueprint-action): Use the official Blueprints actions to plan and deploy your Blueprints with GitHub Actions.
- [Define a webhook](https://www.sanity.io/docs/blueprints/blueprints-webhook): Blueprints let you define and manage your webhooks in code, then deploy them in a predictable manner.
- [Define a CORS origin](https://www.sanity.io/docs/blueprints/blueprints-cors): Blueprints allow you to define and manage your CORS origins in code, then deploy them in a predictable manner.
- [Define a robot token](https://www.sanity.io/docs/blueprints/blueprints-robot-tokens): Blueprints allow you to create robot tokens alongside other resources for use in the blueprint.
- [Define a custom role](https://www.sanity.io/docs/blueprints/blueprints-role): Use Blueprints to define a custom role in code alongside your project's other resources.
- [Define an application](https://www.sanity.io/docs/blueprints/deploy-an-application-with-blueprints): Deploy an SDK app as a blueprint resource with defineApplication and its view definers.
- [Configure Media Library](https://www.sanity.io/docs/blueprints/blueprints-media-library): Configure Media Library fields as code with defineMediaLibraryConfig, a singleton config resource.
- [Configuration file reference](https://www.sanity.io/docs/blueprints/blueprint-config): Reference documentation for the Blueprint configuration files.
- [Application reference](https://www.sanity.io/docs/blueprints/application-blueprints-reference): Field reference for defineApplication and the application view definers: window, panel, tile, asset source, and web worker.
- [Blueprints glossary](https://www.sanity.io/docs/blueprints/glossary): Definitions of the core Blueprints terms: stacks, scopes, values, deletion policies, and more.
- [Blueprints scopes reference](https://www.sanity.io/docs/blueprints/scopes): Project versus organization scope, which resource types need which scope, and how the CLI resolves scope.
- [Blueprints](https://www.sanity.io/docs/cli-reference/cli-blueprints): Reference documentation for the Sanity CLI Blueprints command.
- [Deploy custom functions to automate content operations](https://www.sanity.io/docs/functions)
- [Introduction](https://www.sanity.io/docs/functions/functions-introduction): Learn how to take advantage of Functions in your Sanity projects.
- [Create a Document Function](https://www.sanity.io/docs/functions/function-quickstart): Start building with Functions by deploying a new function to Sanity's infrastructure.
- [Create a Media Library Asset Function](https://www.sanity.io/docs/functions/asset-function-quickstart): Start building a function that reacts to changes to a Media Library asset.
- [Create a Sync Tag Invalidate Function](https://www.sanity.io/docs/functions/sync-tag-function-quickstart): Build and deploy a new Sync Tag Invalidate function to Sanity's infrastructure.
- [Create a Scheduled Function](https://www.sanity.io/docs/functions/scheduled-function-quickstart): Create your first scheduled function, a Sanity function that runs on a set schedule, with Blueprints.
- [Create a PubSub function](https://www.sanity.io/docs/functions/pubsub-function-quickstart): Create your first PubSub (Publisher/Subscriber) function, a Sanity Function you can trigger from other functions.
- [Manage dependencies](https://www.sanity.io/docs/functions/function-dependencies): Functions can be self-contained, or part of a larger ecosystem. Learn how to manage function dependencies in your projects.
- [Local testing](https://www.sanity.io/docs/functions/functions-local-testing): Simulate Functions locally with real data and an interactive playground.
- [Function to function invocation](https://www.sanity.io/docs/functions/function-to-function-invocation): Learn how to invoke one function from another.
- [Configure @sanity/client](https://www.sanity.io/docs/functions/functions-js-client): Learn to use the JavaScript client in a Sanity Function.
- [Add environment variables](https://www.sanity.io/docs/functions/function-env-vars): Learn to add environment variables to your functions.
- [Assign custom robot tokens](https://www.sanity.io/docs/functions/robot-tokens-with-functions): Learn how to authenticate Sanity Functions using robot tokens defined with Blueprints.
- [Common patterns](https://www.sanity.io/docs/functions/functions-cheatsheet): Common patterns and techniques for creating Functions.
- [Handler reference](https://www.sanity.io/docs/functions/function-wrapper): Reference documentation for the shape of the function wrapper.
- [Functions](https://www.sanity.io/docs/cli-reference/functions): Interact with and test your Sanity Functions from the CLI.
- [Canvas](https://www.sanity.io/docs/canvas)
- [Introduction](https://www.sanity.io/docs/canvas/introduction-to-canvas): A familiar writing tool that understands your content structure, so content can flow directly into the right Studio fields with a single click.
- [Introduction](https://www.sanity.io/docs/canvas/writing): Write and collaborate in Canvas with AI assistance, contextual notes, and real-time collaboration.
- [Keyboard shortcuts](https://www.sanity.io/docs/canvas/keyboard-shortcuts): Reference for Canvas keyboard shortcuts covering text formatting, document navigation, text selection, document management, collaboration, and Canvas-specific features.
- [Working with templates](https://www.sanity.io/docs/canvas/templates): Create reusable Canvas templates with pre-configured content types and field labels for repeatable content workflows.
- [Troubleshooting Canvas](https://www.sanity.io/docs/canvas/troubleshooting): Common issues writers run into when using Canvas, with suggested fixes.
- [Configure Canvas for your content](https://www.sanity.io/docs/canvas/configure-canvas): Make your Studio schema available in Canvas and configure how it surfaces to writers.
- [Build with AI](https://www.sanity.io/docs/ai)
- [Best practices](https://www.sanity.io/docs/ai/get-started): Set up the Sanity Agent Toolkit and MCP server to help AI assistants generate high-quality Sanity code that follows established best practices.
- [MCP setup and introduction](https://www.sanity.io/docs/ai/mcp-server): Enable AI agents to interact with your Sanity workspace through the Model Context Protocol (MCP).
- [Agent skills](https://www.sanity.io/docs/ai/skills): Understand and use agent skills to help AI assistants generate high-quality Sanity code that follows established best practices.
- [Get to know Sanity Context](https://www.sanity.io/docs/ai/sanity-context): Sanity Context exposes the content kept in Sanity to your agents through a hosted, read-only MCP server, from your live dataset or from Knowledge Bases built ahead of time.
- [Quick start](https://www.sanity.io/docs/ai/sanity-context-quick-start): Install the Sanity Context skill, run the guided setup, and verify your agent can read your content.
- [Retrieval modes](https://www.sanity.io/docs/ai/sanity-context-retrieval-modes): How GROQ mode and Knowledge Bases differ, when each one fits, and where dataset embeddings bridge the two.
- [Inline initial context](https://www.sanity.io/docs/ai/sanity-context-initial-context): Fetch initial context over HTTP and drop the tool from your agent to remove a round trip from every conversation.
- [Knowledge Bases](https://www.sanity.io/docs/ai/sanity-context-knowledge-bases): A Knowledge Base is a pre-built index over material you choose, attached as sources and served to agents through Context MCP.
- [Knowledge Base source types](https://www.sanity.io/docs/ai/sanity-context-source-types): Dataset, website, and file sources for a Knowledge Base: what each accepts, how it is scoped, and which file formats a file source reads.
- [Create a Knowledge Base](https://www.sanity.io/docs/ai/sanity-context-create-knowledge-base): Create a Knowledge Base, add its first source, run a build, and review the entries and issues it produces.
- [Keep a Knowledge Base current](https://www.sanity.io/docs/ai/sanity-context-maintain-knowledge-base): Set refresh schedules for dataset and website sources, respond to change detection, and decide when to rebuild.
- [Resolve Knowledge Base issues](https://www.sanity.io/docs/ai/sanity-context-resolve-issues): Work through conflicts a build detected and turn your decisions into instructions that carry across future builds.
- [Add insights to Sanity Context](https://www.sanity.io/docs/ai/sanity-context-insights): Sanity Context insights tracks and analyzes your agent conversations
- [Sanity Context patterns and best practices](https://www.sanity.io/docs/ai/sanity-context-patterns): Production patterns and best practices for building agents with Sanity Context.
- [Connect Sanity Context with OpenAI Agents SDK](https://www.sanity.io/docs/ai/sanity-context-openai-agents-sdk): Connect Sanity Context to a Python agent using the OpenAI Agents SDK with built-in MCP support.
- [Connect Sanity Context with Vercel AI SDK](https://www.sanity.io/docs/ai/sanity-context-vercel-ai-sdk): Connect Sanity Context to a TypeScript agent using the Vercel AI SDK and Anthropic.
- [Connect Sanity Context with LangChain](https://www.sanity.io/docs/ai/sanity-context-langchain): Connect Sanity Context to a Python agent using LangChain and langchain-mcp-adapters.
- [Content access and security](https://www.sanity.io/docs/ai/sanity-context-security): How the organization token, the MCP's sources, and groqFilter decide what an agent connected to Context MCP can read.
- [Configure an MCP](https://www.sanity.io/docs/ai/sanity-context-configure-mcp): Create an MCP in the Context app, scope what it serves, and connect an agent to the endpoint.
- [Context MCP reference](https://www.sanity.io/docs/ai/sanity-context-mcp): The reference for Context MCP: endpoints, URL parameters, configuration fields, and text search.
- [Context MCP tools](https://www.sanity.io/docs/ai/sanity-context-mcp-tools): Every tool Context MCP serves, by mode, with what each one returns and when an agent reaches for it.
- [Content Agent API](https://www.sanity.io/docs/apis-and-sdks/content-agent-api): Build custom integrations with the Sanity Content Agent API.
- [Installation](https://www.sanity.io/docs/studio/install-and-configure-sanity-ai-assist): How to install and configure the AI Assist plugin for Sanity Studio.
- [HTTP API Reference](https://www.sanity.io/docs/http-reference)
- [Actions](https://www.sanity.io/docs/http-reference/actions): Reference documentation for the Actions HTTP endpoint.
- [Assets](https://www.sanity.io/docs/http-reference/assets): Upload images and files to Content Lake, and link Media Library assets to your dataset.
- [Copy](https://www.sanity.io/docs/http-reference/copy): The Copy API, or Cloud Clone, lets you copy existing datasets.
- [Backups](https://www.sanity.io/docs/http-reference/backups): Reference documentation for the Backups API.
- [Doc](https://www.sanity.io/docs/http-reference/doc): Retrieve one or more documents by ID and bypass the caching layer.
- [Export](https://www.sanity.io/docs/http-reference/export): Reference documentation for the export HTTP endpoint.
- [History](https://www.sanity.io/docs/http-reference/history): Reference documentation for the History HTTP endpoint.
- [Jobs](https://www.sanity.io/docs/http-reference/jobs): Reference documentation for the Jobs HTTP endpoint.
- [Listen](https://www.sanity.io/docs/http-reference/listen): Reference documentation for the Listen HTTP endpoint.
- [Live](https://www.sanity.io/docs/http-reference/live): Reference documentation for the Live HTTP endpoint.
- [Mutation](https://www.sanity.io/docs/http-reference/mutation): Reference documentation for the Mutation HTTP reference.
- [Query](https://www.sanity.io/docs/http-reference/query): Reference documentation for the Query HTTP endpoint.
- [Scheduling](https://www.sanity.io/docs/http-reference/scheduling): Reference documentation for the Scheduling HTTP endpoints.
- [Webhooks API reference](https://www.sanity.io/docs/http-reference/webhooks): Reference documentation for the Webhooks HTTP endpoints.
- [Agent Actions](https://www.sanity.io/docs/http-reference/agent-actions): Reference documentation for the Agent Actions HTTP API.
- [Content Agent](https://www.sanity.io/docs/http-reference/content-agent): HTTP reference documentation for the Content Agent API
- [Embeddings index API reference](https://www.sanity.io/docs/http-reference/embeddings-index): Reference documentation for the Embeddings Index HTTP endpoints.
- [Functions](https://www.sanity.io/docs/http-reference/functions-api): Reference documentation for the Sanity Functions HTTP endpoints.
- [Media Library API reference](https://www.sanity.io/docs/http-reference/media-library): HTTP endpoints reference for the Media Library API
- [Application management](https://www.sanity.io/docs/http-reference/applications-api): Reference documentation for the applications & user-applications HTTP endpoints.
- [Access](https://www.sanity.io/docs/http-reference/access-api): A centralized API to manage resource access control through roles and permissions.
- [Projects](https://www.sanity.io/docs/http-reference/projects-api): Reference documentation for the projects HTTP endpoint.
- [Roles](https://www.sanity.io/docs/http-reference/roles): Reference documentation for the Roles HTTP endpoints.
- [User attributes](https://www.sanity.io/docs/http-reference/user-attributes): Manage user attributes and attribute definitions to enable parameterized role-based access control
- [Activity Log](https://www.sanity.io/docs/http-reference/activity-log): HTTP endpoints for fetching organization/project activity logs of management activities. E.g. invites, role changes, plan changes.
- [Libraries and tooling](https://www.sanity.io/docs/libraries)
- [Embeddings Index CLI reference (deprecated)](https://www.sanity.io/docs/libraries/embeddings-index-cli-reference): Reference documentation of the Sanity Embeddings Index CLI to create and manage embeddings indexes for your content.
- [Specifications](https://www.sanity.io/docs/specifications)
- [Syntax reference](https://www.sanity.io/docs/specifications/groq-syntax): Reference documentation for the GROQ syntax.
- [Data types](https://www.sanity.io/docs/specifications/groq-data-types): Data types supported by GROQ
- [Parameters](https://www.sanity.io/docs/specifications/groq-parameters): User-provided parameters in GROQ
- [Operators](https://www.sanity.io/docs/specifications/groq-operators): A description of operators in GROQ
- [Functions](https://www.sanity.io/docs/specifications/groq-functions): Reference documentation for GROQ functions.
- [Pipeline components](https://www.sanity.io/docs/specifications/groq-pipeline-components): A description of GROQ pipeline components
- [Joins](https://www.sanity.io/docs/specifications/groq-joins): A description of joining multiple documents in GROQ
- [Visual Editing](https://www.sanity.io/docs/visual-editing)
- [Introduction](https://www.sanity.io/docs/visual-editing/introduction-to-visual-editing): Framework quickstarts, a framework-agnostic conceptual series, and task-focused guides for specific features.
- [Visual Editing for App Router](https://www.sanity.io/docs/visual-editing/visual-editing-with-next-js-app-router): Set up visual editing between Sanity Studio and a Next.js App Router frontend, including the Sanity client, Draft Mode, Visual Editing, and Live Content.
- [Visual Editing for Pages Router](https://www.sanity.io/docs/visual-editing/visual-editing-with-next-js-pages-router): Get started with Sanity Visual Editing in a new or existing NMeasured from the saved file
Size measures the captured UTF-8 text, not compressed transfer size. Tokens are counted with a named tokenizer; other models can count differently. Neither measure establishes context compatibility or answer quality.
Sanity is the Content Operating System for the AI era. It gives teams a structured content backbone (Content Lake), a fully customizable editing environment (Sanity Studio), and APIs that power everything from websites to AI agents. Model content around how your business actually works, automate the repetitive stuff, and deliver to any channel from a single source of truth.
Context architecture
12 H2 sections organize 832 parsed Markdown links. 0 links point to .md or .markdown paths; 1 link occurrences use another hostname. Linked destinations have not been recursively validated.
| H2 section | Links | UTF-8 bytes | Tokens |
|---|---|---|---|
| DocsLine 5 | 701 | 122572 | 26937 |
| ReferenceLine 710 | 1 | 209 | 46 |
| ProductsLine 714 | 9 | 1427 | 313 |
| SolutionsLine 726 | 3 | 529 | 112 |
| PricingLine 732 | 1 | 207 | 47 |
| LegalLine 736 | 9 | 631 | 169 |
| CompanyLine 748 | 3 | 440 | 105 |
| BlogLine 754 | 21 | 5248 | 1170 |
| EngineeringLine 778 | 17 | 3804 | 910 |
| GlossaryLine 798 | 51 | 12578 | 2630 |
| EventsLine 852 | 11 | 2362 | 526 |
| CommunityLine 866 | 5 | 704 | 163 |
1 distinct links point to other llms.txt paths. These are routes to more indexes, not proof their contents were included in this file.
Link counts exclude parsed fenced and inline code and resolve relative destinations against the final endpoint. Section sizes cover the text below each H2 until the next H2.
Embedded material
Embedded example text and links to further documentation are counted separately. A code block does not establish that a sample runs or that an authentication flow succeeds.
Publisher prioritization
No H2 section named “Optional” was detected in this file.
The community proposal uses Optional by convention for secondary links that can be skipped for a shorter context. This label does not establish that everything outside it is critical, or that the material inside it is deprecated.
Machine-readable routes
MCP-related text was detected in the captured file. 9 links have MCP-related labels or paths. 0 fenced lines match mcpServers, mcp_servers or an mcp add command.
These are text and link observations. No MCP server connection, authentication or tool call was tested.
Index and bundle
Not established
A verified text response establishes a companion at the checked URL. It does not prove the bundle contains all product documentation, that generation is automated, or that it fits an assistant’s context window.
Change evidence
This capture establishes a baseline. Update frequency cannot be determined from one observation.
29 links have release, changelog, deprecation or migration terms in their labels or paths. These provide places to investigate product changes separately.
File changes can reveal documentation edits or navigation changes. They do not by themselves measure product release velocity, accuracy, agent adoption or AI visibility.
b24076c940738aba0297ca71cec4a8b75d91c7edccbc8573d529bde87cce63deCounts use a deterministic parser, not a spec-compliance grade. Unusual Markdown and indented code can fall outside its recognized patterns. See the llms.txt proposal and tokenizer implementation.