Developer tools · llms.txt file breakdown
GitBook is a collaborative platform for creating, publishing and managing
The actual file
The saved llms.txt text, displayed as source. The file belongs to its publisher; the live endpoint may change.
Complete saved Markdown shown below.
# GitBook
> GitBook is a collaborative platform for creating, publishing and managing
> **Product Documentation** and **API Documentation**, as well as technical docs,
> changelogs, help centers, localization, and guides for migrations and
> integrations. Powered by AI-driven search, analytics and interactive tooling.
> GitBook supports **Enterprise Product Documentation** programs with SSO and
> SAML, granular permissions, authenticated and private publishing, adaptive
> content and content governance. Published GitBook sites automatically expose a
> Markdown version of every page, an llms.txt index and an MCP server.
## Product documentation
- [Public product docs](https://www.gitbook.com/solutions/public-docs): Publish product documentation your users can find, read and search.
- [Editor](https://www.gitbook.com/features/editor): The authoring experience for product documentation teams.
- [Complete guide to publishing product documentation](https://gitbook.com/docs/guides/editing-and-publishing-documentation/complete-guide-to-publishing-docs-gitbook.md): End to end, from setup through customization, analytics and site variants.
- [Quickstart](https://gitbook.com/docs/getting-started/quickstart.md): Publish a first product docs site in minutes.
- [Content structure](https://gitbook.com/docs/create-content/content-structure.md): How sites, sections, groups and pages organize a documentation set.
- [Site customization](https://gitbook.com/docs/manage-your-site/customization.md): Branded documentation with custom logo, fonts, colors and navigation.
- [Custom domain](https://gitbook.com/docs/publish/custom-domain.md): Serve docs on your own domain, including as a /docs subdirectory.
- [Changelogs](https://gitbook.com/docs/create-content/blocks/updates.md): Publish product updates as a changelog on a docs site.
- [Documentation analytics](https://gitbook.com/docs/analytics/insights.md): Traffic and usage data for a published site.
- [AI insights](https://gitbook.com/docs/analytics/ai-insights.md): What readers actually ask, and where the docs fall short.
## Enterprise product documentation
- [GitBook Enterprise](https://www.gitbook.com/enterprise): Secure, intelligent documentation at scale, with advanced security, governance, AI tools, Git workflows and enterprise support for larger teams.
- [Authenticated access](https://www.gitbook.com/features/authenticated-access): Put published documentation behind your own authentication provider.
- [Internal knowledge base](https://www.gitbook.com/solutions/knowledge-base): An authenticated internal knowledge base your team can access and search.
- [Security and compliance](https://security.gitbook.com/): GitBook's trust centre, including SOC 2 and ISO 27001.
- [Buy vs build](https://www.gitbook.com/buy-vs-build): Comparing GitBook against building a documentation platform in-house.
- [Switch to GitBook](https://www.gitbook.com/switch): Migration support and onboarding for teams moving from another platform.
- [Site audience and access control](https://gitbook.com/docs/publish/site-audience.md): Control who can view published documentation.
- [Setting up authenticated access](https://gitbook.com/docs/publish/site-audience/authenticated-access.md): Okta, Azure AD, Auth0, AWS Cognito, OIDC or a custom backend.
- [Private publishing with share links](https://gitbook.com/docs/publish/site-audience/share-links.md): Share documentation privately with named audiences.
- [SSO and SAML](https://gitbook.com/docs/account-and-billing/sso-and-saml.md): Single sign-on for members of your organization.
- [Permissions and inheritance](https://gitbook.com/docs/collaborate/member-management/permissions-and-inheritance.md): How access is controlled and inherited across content.
- [Roles](https://gitbook.com/docs/collaborate/member-management/roles.md): What each role can do across an organization.
- [Teams](https://gitbook.com/docs/collaborate/member-management/teams.md): Group members for permission management at scale.
- [Merge rules](https://gitbook.com/docs/collaborate/merge-rules.md): Requirements that must be met before content changes can be published.
- [Style guide](https://gitbook.com/docs/create-content/styleguide.md): Enforce writing rules across every contributor, human or AI agent.
- [Adaptive content](https://gitbook.com/docs/publish/adaptive-content.md): Tailor what a reader sees based on who they are.
- [Site sections](https://gitbook.com/docs/manage-your-site/site-structure/site-sections.md): Multiple products, audiences or topics in one published site.
- [Docs Embed](https://gitbook.com/docs/publish/embedding.md): Embed documentation directly in your product or app.
## API documentation
- [API docs solution](https://www.gitbook.com/solutions/api): Branded, interactive API docs generated from an OpenAPI specification.
- [Document an API](https://gitbook.com/docs/create-content/openapi.md): Interactive API references with a test-it button.
- [API documentation principles](https://gitbook.com/docs/guides/api-documentation/api-documentation-principles.md): What makes API docs drive adoption.
- [Write incredible API documentation](https://gitbook.com/docs/guides/api-documentation/how-to-write-incredible-api-documentation.md): Lessons on API docs that reduce support load.
- [GitBook REST API reference](https://gitbook.com/docs/developers/gitbook-api/api-reference.md): Endpoints for organizations, sites, spaces, content and analytics.
- [API authentication](https://gitbook.com/docs/developers/gitbook-api/authentication.md): How to authenticate API requests.
## AI and agent tooling
- [GitBook AI](https://www.gitbook.com/features/ai): How GitBook optimizes documentation for AI tools automatically.
- [GitBook Agent](https://www.gitbook.com/features/ai/gitbook-agent): An AI collaborator that spots outdated docs and proposes changes for review.
- [GitBook Assistant](https://www.gitbook.com/features/ai/gitbook-assistant): Contextual answers for readers, drawn from a whole knowledge base.
- [Agent score](https://gitbook.com/agent-score): Check how ready a documentation site is for AI agents.
- [Skill generator](https://gitbook.com/skill-generator): Generate an agent skill from a documentation site.
- [LLM-ready docs](https://gitbook.com/docs/getting-started/llm-ready-docs.md): Markdown pages, llms.txt and llms-full.txt on every published site.
- [GEO guide](https://gitbook.com/docs/guides/seo-and-llm-optimization/geo-guide.md): Optimizing documentation for AI search and LLM ingestion.
- [Agent skills](https://gitbook.com/docs/skill.md): Skill documents for coding agents working with GitBook content and sites.
- [GitBook MCP](https://gitbook.com/docs/docs-as-code/gitbook-mcp.md): Connect AI coding assistants to GitBook to create sites and edit content.
## Docs as code
- [Git Sync](https://www.gitbook.com/features/git-sync): Two-way sync between GitBook and a GitHub or GitLab repository.
- [Setting up Git Sync](https://gitbook.com/docs/docs-as-code/git-sync.md): Configuration, monorepos and pull request previews.
- [GitBook CLI](https://gitbook.com/docs/docs-as-code/gitbook-cli.md): Drive docs workflows from the command line or from scripts.
- [Integrations](https://www.gitbook.com/integrations): Built-in extensions and custom components.
## Solutions by use case
- [Help center](https://www.gitbook.com/solutions/help-center): Customer-facing help content and support documentation.
- [Knowledge base](https://www.gitbook.com/solutions/knowledge-base): Internal knowledge for teams, behind authentication.
- [Public docs](https://www.gitbook.com/solutions/public-docs): Documentation open to the web.
- [API docs](https://www.gitbook.com/solutions/api): Interactive API references.
- [Open source and sponsored sites](https://www.gitbook.com/solutions/open-source): Free documentation hosting for open source projects.
## Industries
- [Financial services](https://www.gitbook.com/industries/financial-services)
- [Healthcare](https://www.gitbook.com/industries/healthcare)
- [Security](https://www.gitbook.com/industries/security)
- [Technology](https://www.gitbook.com/industries/technology)
- [Startups](https://www.gitbook.com/industries/startups)
## Customers
- [Customer stories](https://www.gitbook.com/customers): How teams use GitBook, with links to their live documentation.
- [FreedomPay](https://www.gitbook.com/customers/freedompay): Rebuilding an integration experience with GitBook.
- [Gravitee](https://www.gitbook.com/customers/gravitee): Documentation for an API management platform.
- [Maple Finance](https://www.gitbook.com/customers/maple-finance): Documentation as a partner-facing differentiator.
- [Swarmia](https://www.gitbook.com/customers/swarmia): Documentation built to feel like an extension of the product.
## Localization and migration
- [Multilingual sections](https://gitbook.com/docs/manage-your-site/site-structure/multilingual-sections.md): Publish documentation in multiple languages from one site.
- [Content variants](https://gitbook.com/docs/manage-your-site/site-structure/variants.md): Documentation for several product versions or languages side by side.
- [AI translation](https://gitbook.com/docs/gitbook-agent/translations.md): Auto-translate content and keep translations synced with the source.
- [Migrate to GitBook](https://gitbook.com/docs/getting-started/import.md): Import from Confluence, Notion, Git, Markdown and others.
## Full documentation
- [Documentation index](https://gitbook.com/docs/llms.txt): Every documentation page, with a Markdown URL for each. Generated from the live docs.
- [Full documentation text](https://gitbook.com/docs/llms-full.txt): The entire documentation set in one file, for broad context in a single fetch.
- [Documentation home](https://gitbook.com/docs/readme.md): What GitBook does and where to begin.
- [Developer documentation](https://gitbook.com/docs/developers/readme.md): API, SDK, CLI and integration development.
- [Changelog](https://gitbook.com/docs/changelog/readme.md): Releases, improvements and fixes.
## Company
- [Pricing](https://www.gitbook.com/pricing): Plans and current pricing.
- [Plans in detail](https://gitbook.com/docs/account-and-billing/plans.md): What each GitBook plan includes.
- [Blog](https://www.gitbook.com/blog): Product announcements and writing on documentation practice.
- [About](https://www.gitbook.com/about): About GitBook.
- [Careers](https://www.gitbook.com/careers): Open roles.
- [Contact and support](https://www.gitbook.com/contact): How to reach GitBook.
- [Events](https://www.gitbook.com/events): Talks, webinars and conferences.
- [State of Docs 2026](https://www.stateofdocs.com/2026): Industry research on documentation practice.
## Optional
- [Sitemap](https://www.gitbook.com/sitemap.xml)
- [Blog RSS](https://www.gitbook.com/blog/rss)
- [Status](https://www.gitbookstatus.com/)
- [Terms of service](https://gitbook.com/docs/policies/terms.md)
- [Privacy statement](https://gitbook.com/docs/policies/privacy-and-security/statement.md)
Measured 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.
GitBook is a collaborative platform for creating, publishing and managing **Product Documentation** and **API Documentation**, as well as technical docs, changelogs, help centers, localization, and guides for migrations and integrations. Powered by AI-driven search, analytics and interactive tooling.
Context architecture
12 H2 sections organize 84 parsed Markdown links. 41 links point to .md or .markdown paths; 48 link occurrences use another hostname. Linked destinations have not been recursively validated.
| H2 section | Links | UTF-8 bytes | Tokens |
|---|---|---|---|
| Product documentationLine 12 | 10 | 1438 | 318 |
| Enterprise product documentationLine 25 | 18 | 2570 | 560 |
| API documentationLine 46 | 6 | 883 | 192 |
| AI and agent toolingLine 55 | 9 | 1189 | 284 |
| Docs as codeLine 67 | 4 | 481 | 114 |
| Solutions by use caseLine 74 | 5 | 558 | 119 |
| IndustriesLine 82 | 5 | 320 | 84 |
| CustomersLine 90 | 5 | 575 | 136 |
| Localization and migrationLine 98 | 4 | 612 | 132 |
| Full documentationLine 105 | 5 | 608 | 142 |
| CompanyLine 113 | 8 | 660 | 164 |
| OptionalLine 124 · Optional | 5 | 296 | 80 |
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
1 H2 section named “Optional” contain 5 parsed links. 79 links sit outside those sections. That puts 6.0% of the file’s parsed links under Optional.
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. 1 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
Verified text companion
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.
2 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.
7cbe0c50fba1d64924dec4f825dfdd8d2be0fd504eb2493276f51aaab9d2a6f0Counts 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.