Skip to content
J·BJon BishopFractional growth marketer

Developer tools · llms.txt file breakdown

Strapi llms.txt

A directly retrieved Markdown index for Strapi's documentation, with 295 links across 1 detected headings.

The actual file

Source Markdown

The saved llms.txt text, displayed as source. The file belongs to its publisher; the live endpoint may change.

Open saved text ↗

Showing the first 18000 characters. Load the complete file to read the remainder.

# Strapi Documentation

- [Cloud account billing details](https://docs.strapi.io/cloud/account/account-billing.md): Billing details and invoices are managed on the Profile page, where payment methods are updated and invoice history is available.
- [Cloud profile settings](https://docs.strapi.io/cloud/account/account-settings.md): Settings of the Profile page include account details, connected accounts, and account deletion options.
- [Cloud database configuration](https://docs.strapi.io/cloud/advanced/database.md): Default PostgreSQL can be swapped for any supported SQL database by aligning configuration and environment variables.
- [Cloud email provider](https://docs.strapi.io/cloud/advanced/email.md): Third‑party email services integrate through plugins and environment variables to replace the default sender.
- [Middleware Configuration for Strapi Cloud](https://docs.strapi.io/cloud/advanced/middlewares.md): On Strapi Cloud, middleware customizations must go in config/env/production/middlewares. Changes to the global config file are overwritten on deploy.
- [Upload Provider Configuration for Strapi Cloud](https://docs.strapi.io/cloud/advanced/upload.md): External storage like S3 or Cloudinary requires plugin setup, security middleware, and Cloud variables.
- [Upload size limits for Strapi Cloud](https://docs.strapi.io/cloud/advanced/upload-size-limits.md): Non-image files are capped at 200 MB on all plans. Image files have a memory-based recommended maximum that varies by format, plan, and Media Library settings. To upload larger images, disable Responsive friendly upload and Size optimization.
- [Command Line Interface (CLI)](https://docs.strapi.io/cloud/cli/cloud-cli.md): CLI commands handle login, project linking, deploying, listing, and logout without needing a remote repository.
- [Strapi Cloud fundamentals](https://docs.strapi.io/cloud/cloud-fundamentals.md): Strapi Cloud is a PaaS hosting platform for deploying Strapi CMS projects, offering three pricing plans with different features and support levels, two user roles (owners and maintainers), and REST/GraphQL APIs that behave identically to self-hosted servers.
- [Cloud caching & performance](https://docs.strapi.io/cloud/getting-started/caching.md): Edge caching via Cache-Control headers reduces latency and server load for heavy static content.
- [Strapi Cloud - Dashboard deployment](https://docs.strapi.io/cloud/getting-started/deployment.md): Deploy your Strapi project on Strapi Cloud using the dashboard by choosing a plan, connecting a Git repository, configuring your project settings, and setting up billing details.
- [Strapi Cloud - CLI deployment](https://docs.strapi.io/cloud/getting-started/deployment-cli.md): Deploy a Strapi project to Strapi Cloud using the strapi login, strapi link, and strapi deploy CLI commands, with optional automatic deployment on git repository commits.
- [Cloud project deployment](https://docs.strapi.io/cloud/getting-started/deployment-options.md): Deploy your Strapi application on Strapi Cloud using either the Cloud dashboard or the CLI, with step-by-step guides provided for both methods.
- [Cloud billing & usage](https://docs.strapi.io/cloud/getting-started/usage-billing.md): Strapi Cloud offers three plans (Starter, Pro, and Business) with usage-based pricing that varies by API requests, asset storage, and bandwidth, plus overages charged monthly; projects may be suspended for unpaid invoices or plan violations.
- [Welcome to the Strapi Cloud Documentation!](https://docs.strapi.io/cloud/intro.md): Strapi Cloud is a fully managed hosting platform for deploying Strapi applications, abstracting infrastructure complexity while enabling content management, collaboration, and compliance features.
- [Cloud project collaboration](https://docs.strapi.io/cloud/projects/collaboration.md): Project owners invite maintainers through the Share button, manage pending invitations, and revoke access.
- [Cloud deployments management](https://docs.strapi.io/cloud/projects/deploys.md): Deployment triggers can be manual or automatic on git pushes, with the ability to cancel active builds from dashboard or CLI.
- [Cloud deployment history & logs](https://docs.strapi.io/cloud/projects/deploys-history.md): Deployments tab lists every build with status and allows deep inspection of build and deployment logs.
- [Cloud project logs](https://docs.strapi.io/cloud/projects/logs.md): The Logs tab streams your project's live logs in a searchable, filterable table. Click any entry to inspect its full message and metadata.
- [Cloud notifications](https://docs.strapi.io/cloud/projects/notifications.md): Bell icon opens a feed of recent deployment events, automatically purged after 30 days.
- [Cloud project observability](https://docs.strapi.io/cloud/projects/observability.md): The Observability tab surfaces usage metrics, endpoint traffic, and infrastructure health data directly from your project dashboard. Use it to monitor API and bandwidth consumption, identify high-traffic endpoints, and track CPU and Memory usage over time.
- [Cloud projects overview](https://docs.strapi.io/cloud/projects/overview.md): Projects page lists all apps with status and quick actions; selecting one opens a dashboard with metrics and controls.
- [Cloud project settings](https://docs.strapi.io/cloud/projects/settings.md): Settings area spans project-level controls (general, billing & invoices, plans) and per-environment configuration.
- [Admin panel customization](https://docs.strapi.io/cms/admin-panel-customization.md): The admin panel can be tailored to match your branding, by editing src/admin/app and using an extensions folder to swap logos, favicon, locales, translations, themes, bundlers, or editors.
- [Admin panel bundlers](https://docs.strapi.io/cms/admin-panel-customization/bundlers.md): Supported JavaScript bundlers influence builds and development flow.
- [Admin panel extension](https://docs.strapi.io/cms/admin-panel-customization/extension.md): Strapi's React-based admin panel can be extended locally via /src/admin/app for project-specific needs or through plugins for reusable, distributable extensions across multiple Strapi instances.
- [Favicon](https://docs.strapi.io/cms/admin-panel-customization/favicon.md): Replace the Strapi admin panel favicon by replacing the favicon.png file at the project root or configuring the strapi::favicon middleware, then rebuild the app.
- [Homepage customization](https://docs.strapi.io/cms/admin-panel-customization/homepage.md): The admin panel homepage displays default content and profile widgets and supports custom additions through the app.widgets.register API.
- [Admin panel customization - URL, host, and path configuration](https://docs.strapi.io/cms/admin-panel-customization/host-port-path.md): Configure the Strapi admin panel's host, port, and URL path in the config/admin.[ts|js] file to change where it is accessible from its default location at /admin.
- [Locales & translations](https://docs.strapi.io/cms/admin-panel-customization/locales-translations.md): Configure the admin panel languages by updating the config.locales array and override default or plugin strings with config.translations or custom translation files.
- [Logos](https://docs.strapi.io/cms/admin-panel-customization/logos.md): Update login and navigation logos by extending the admin app. Prefer SVG for crisp rendering; provide light/dark variants when possible for contrast.
- [Theme extension](https://docs.strapi.io/cms/admin-panel-customization/theme-extension.md): Extend the Strapi admin panel theme for light and dark modes by customizing config.theme.light and config.theme.dark keys in /src/admin/app.js to override colors and other design system properties.
- [Customizing the rich text editor](https://docs.strapi.io/cms/admin-panel-customization/wysiwyg-editor.md): Strapi's admin panel includes a built-in WYSIWYG markdown editor for richtext fields. You can replace it by installing third-party editor plugins from the Marketplace or creating a custom field for deeper integration.
- [Docs MCP server](https://docs.strapi.io/cms/ai/docs-mcp-server.md): A Docs MCP server exposes the Strapi documentation to AI coding tools. Connect it to your IDE to get Strapi-aware code suggestions and answers directly in your development environment. The server at https://strapi-docs.mcp.kapa.ai requires OAuth. A request without a bearer token, including MCP initialize, returns 401. Protected-resource metadata is published at https://strapi-docs.mcp.kapa.ai/.well-known/oauth-protected-resource.
- [AI for content managers](https://docs.strapi.io/cms/ai/for-content-managers.md): Strapi AI helps content managers design content structures, translate content, and generate asset metadata from the admin panel. It is Strapi-managed on the plan. On the plan, it is powered by your own AI key, for translations and asset metadata only. Strapi also includes a built-in MCP server that lets AI clients manage content through natural language.
- [AI for developers](https://docs.strapi.io/cms/ai/for-developers.md): The Strapi documentation site includes free AI-powered tools including an AI toolbar, chatbot powered by Kapa, llms.txt files, and MCP servers to help developers learn and integrate Strapi more effectively.
- [Strapi Client](https://docs.strapi.io/cms/api/client.md): The Strapi Client is a JavaScript library that simplifies interactions with your Strapi back end for fetching, creating, updating, and deleting content through collection(), single(), and files() methods.
- [Content API](https://docs.strapi.io/cms/api/content-api.md): Strapi's Content API provides access to your content through REST and GraphQL APIs for front-end applications, plus lower-level Document Service and Query Engine APIs for backend and plugin development.
- [Documents](https://docs.strapi.io/cms/api/document.md): A document is an API-only concept representing all content variations (locales, draft/published versions) for a single content-type entry. Use the Document Service API to manipulate documents on the back-end.
- [Document Service API](https://docs.strapi.io/cms/api/document-service.md): The Document Service API is the recommended backend API for interacting with content, providing findOne, findMany, create, update, and delete methods that work with stable documentId identifiers and support Draft & Publish operations.
- [Using fields with the Document Service API](https://docs.strapi.io/cms/api/document-service/fields.md): Use the fields parameter in Document Service API queries to select specific fields to return with your results, reducing data payload across findOne(), findMany(), create(), update(), delete(), publish(), and other document operations.
- [Using filters with the Document Service API](https://docs.strapi.io/cms/api/document-service/filters.md): The Document Service API provides attribute operators ($eq, $lt, $contains, etc.) and logical operators ($and, $or, $not) to filter query results with support for case-sensitive and case-insensitive matching.
- [Using the locale parameter with the Document Service API](https://docs.strapi.io/cms/api/document-service/locale.md): The locale parameter in the Document Service API lets you query, create, update, delete, publish, and unpublish documents for specific language versions using methods like findOne(), findMany(), update(), and delete().
- [Extending the Document Service behavior](https://docs.strapi.io/cms/api/document-service/middlewares.md): Document Service middlewares allow you to perform actions before and after Document Service methods run by registering middleware functions via strapi.documents.use() with access to content type context and method parameters.
- [Using Populate with the Document Service API](https://docs.strapi.io/cms/api/document-service/populate.md): Use the populate parameter with the Document Service API to explicitly load relations, media fields, components, and dynamic zones at one or multiple levels deep, and within create(), update(), publish(), and delete() operations.
- [Using publicationFilter with the Document Service API](https://docs.strapi.io/cms/api/document-service/publication-filter.md): Use the optional publicationFilter parameter to query documents by the relationship between their draft and published versions, for example drafts that were never published, or entries modified since they were last published. It works with findOne(), findFirst(), findMany(), and count(), and combines with other query parameters. status still decides whether you get the draft or the published version.
- [Using Sort & Pagination with the Document Service API](https://docs.strapi.io/cms/api/document-service/sort-pagination.md): Use the Document Service API's sort and pagination parameters to order query results by single or multiple fields and control result limits with limit and start.
- [Using Draft & Publish with the Document Service API](https://docs.strapi.io/cms/api/document-service/status.md): Use the status parameter with the Document Service API to retrieve published or draft versions of documents, count documents by status, and directly publish documents during creation or updates.
- [Entity Service API](https://docs.strapi.io/cms/api/entity-service.md): In Strapi v5, the Document Service API (strapi.documents) replaced the Entity Service API. strapi.entityService is deprecated. In Strapi v4, the Entity Service API handled complex content structures such as components and dynamic zones, and provided CRUD operations, filtering, relation population, and pagination.
- [Components and Dynamic Zones](https://docs.strapi.io/cms/api/entity-service/components-dynamic-zones.md): Use the Entity Service API to create and update components and dynamic zones while creating or updating entries. Components are single objects while dynamic zones are lists of components with a __component type identifier.
- [CRUD operations](https://docs.strapi.io/cms/api/entity-service/crud.md): The Entity Service API performs CRUD operations on content through findOne(), findMany(), create(), update(), and delete() methods, supporting filtering, pagination, relations, and localization.
- [Filtering with the Entity Service API](https://docs.strapi.io/cms/api/entity-service/filter.md): Filter Entity Service API query results using logical operators ($and, $or, $not) and attribute operators ($eq, $contains, $gt, $between, etc.) with the filters parameter in findMany().
- [Ordering & Pagination with the Entity Service API](https://docs.strapi.io/cms/api/entity-service/order-pagination.md): Order and paginate Entity Service API query results using sort, start/limit, or page/pageSize parameters to control result ordering and retrieve specific data subsets.
- [Populating with the Entity Service API](https://docs.strapi.io/cms/api/entity-service/populate.md): The Entity Service API's populate parameter retrieves relations, components, and dynamic zones. Use populate: '*' for all root-level relations, arrays for specific fields, objects for advanced queries with filters and nested populating, or fragments for polymorphic content structures.
- [GraphQL API](https://docs.strapi.io/cms/api/graphql.md): The GraphQL API allows querying and mutating content-types with filtering, sorting, and pagination. It uses documentId as the unique identifier and provides singular and plural queries with support for relations, media fields, components, dynamic zones, and localization.
- [Advanced policies for GraphQL](https://docs.strapi.io/cms/api/graphql/advanced-policies.md): Policies can be attached to GraphQL resolvers to implement complex authorization rules, such as limiting results for unauthenticated users or restricting access based on group membership.
- [Advanced queries for GraphQL](https://docs.strapi.io/cms/api/graphql/advanced-queries.md): Advanced queries in Strapi's GraphQL API use nested selection sets to fetch multi-level relations and custom resolver chains to reuse logic across resolvers and apply context-specific behavior.
- [Using the locale parameter with the GraphQL API](https://docs.strapi.io/cms/api/graphql/locale.md): Use the locale argument with the GraphQL API to query, create, update, and delete documents for a specific locale.
- [OpenAPI specification](https://docs.strapi.io/cms/api/openapi.md): Strapi provides a CLI tool to automatically generate OpenAPI 3.1.0 specifications documenting all API endpoints, parameters, and responses. The generated specification can be integrated with Swagger UI for interactive API documentation.
- [Query Engine API](https://docs.strapi.io/cms/api/query-engine.md): The Query Engine API provides low-level, unrestricted backend access to Strapi's database layer through strapi.db.query, supporting single and bulk operations with filtering, populating, ordering, and pagination.
- [Bulk Operations](https://docs.strapi.io/cms/api/query-engine/bulk-operations.md): Bulk Operations with the Query Engine API enable you to create, update, delete, and count multiple entries at once using createMany(), updateMany(), deleteMany(), and count() methods.
- [Filtering with the Query Engine API](https://docs.strapi.io/cms/api/query-engine/filtering.md): The Query Engine API filters query results using the where parameter with logical operators ($and, $or, $not) and attribute operators (comparison, string matching, range) prefixed with $.
- [Ordering & Pagination with the Query Engine API](https://docs.strapi.io/cms/api/query-engine/order-pagination.md): The Query Engine API supports ordering results with the orderBy parameter on single or multiple attributes, including relational ordering, and pagination with offset and limit parameters.
- [Populating with the Query Engine API](https://docs.strapi.io/cms/api/query-engine/populating.md): The Query Engine API's populate parameter loads related data in queries, supporting basic population, selective attributes, f

Measured from the saved file

Linked document

UTF-8 text size
89.1 KB91203 bytes
Token count
19065o200k_base encoding
Markdown links
295295 distinct URLs
Fenced code blocks
0299 lines in the 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.

Project H1
Strapi Documentation

Context architecture

How the content is divided

0 H2 sections organize 295 parsed Markdown links. 295 links point to .md or .markdown paths; 0 link occurrences use another hostname. Linked destinations have not been recursively validated.

No H2 sections were detected 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

Code, installation and API examples

Fenced blocks
0 closed
Declared languages
No fenced blocks detected
Package-install commands
0 detected in fenced or inline code
Authentication examples
0 fenced lines match API-key, Authorization, Bearer, OAuth or access-token patterns
HTTP request examples
0 fenced lines match request-method patterns
Authentication links
0 links have authentication-related labels

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

The Optional section

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 references and configuration text

MCP-related text was detected in the captured file. 3 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

llms-full.txt companion

Verified text companion

Text companion verified

https://docs.strapi.io/llms-full.txt ↗
Discovery
Conventional sibling path checked
HTTP response
206 · text/plain; charset=utf-8
Text size
2.4 MB · 2483458 bytes (server-reported)
Token count
Not measured for the whole file
Retrieval scope
Bounded prefix inspected; the whole body was not downloaded

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

What can be said about freshness

This capture establishes a baseline. Update frequency cannot be determined from one observation.

Linked release and migration material

63 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.

Capture identity and measurement method
Requested endpoint
https://docs.strapi.io/llms.txt
Final endpoint
https://docs.strapi.io/llms.txt
HTTP status
200
Content type
text/plain; charset=utf-8
Text retrieval
Firecrawl literal text capture
Tokenizer
tiktoken 0.14.0 · o200k_base
SHA-256 of saved UTF-8 text
1de0e125505acfdfe653d493db6f075ad8f21e4aee8ddbb2897eefee5173d2c9

Counts 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.

Related tools and resources

Contact Jon