# Algolia
> Build search, discovery, and AI experiences with Algolia. Guides, API references, libraries, UI components, and integrations for your stack.
- [Guides (574 pages)](https://www.algolia.com/_llms/guides.txt): Documentation for Guides.
- [Libraries and tools (645 pages)](https://www.algolia.com/_llms/libraries-and-tools.txt): Documentation for Libraries and tools.
- [UI libraries (277 pages)](https://www.algolia.com/_llms/ui-libraries.txt): Documentation for UI libraries.
- [Integrations (130 pages)](https://www.algolia.com/_llms/integrations.txt): Documentation for Integrations.
- [API reference (375 pages)](https://www.algolia.com/_llms/api-reference.txt): Documentation for API reference.
## OpenAPI Specs
- [search](/specs/search.yml)
- [agent-studio](/specs/agent-studio.yml)
- [abtesting-v3](/specs/abtesting-v3.yml)
- [abtesting](/specs/abtesting.yml)
- [advanced-personalization](/specs/advanced-personalization.yml)
- [searchstats](/specs/searchstats.yml)
- [personalization](/specs/personalization.yml)
- [composition](/specs/composition.yml)
- [crawler](/specs/crawler.yml)
- [ingestion](/specs/ingestion.yml)
- [insights](/specs/insights.yml)
- [monitoring](/specs/monitoring.yml)
- [recommend](/specs/recommend.yml)
- [query-suggestions](/specs/query-suggestions.yml)
- [composition-full](/specs/composition-full.yml)
> The links below point to documentation indexes. Follow each `/_llms/` index recursively until you reach documentation pages.
## Indexes
- [Guides (574 pages)](https://www.algolia.com/_llms/guides.txt): Documentation for Guides.
- [Guides / Search and Discovery platform (436 pages)](https://www.algolia.com/_llms/guides/search-and-discovery-platform.txt): Documentation for Guides / Search and Discovery platform.
- [Libraries and tools (645 pages)](https://www.algolia.com/_llms/libraries-and-tools.txt): Documentation for Libraries and tools.
- [Libraries and tools / API clients (419 pages)](https://www.algolia.com/_llms/libraries-and-tools/api-clients.txt): Documentation for Libraries and tools / API clients.
- [Libraries and tools / API clients / current (319 pages)](https://www.algolia.com/_llms/libraries-and-tools/api-clients/current.txt): Documentation for Libraries and tools / API clients / current.
- [UI libraries (277 pages)](https://www.algolia.com/_llms/ui-libraries.txt): Documentation for UI libraries.
- [Integrations (130 pages)](https://www.algolia.com/_llms/integrations.txt): Documentation for Integrations.
- [API reference (375 pages)](https://www.algolia.com/_llms/api-reference.txt): Documentation for API reference.
- [API reference / Search (154 pages)](https://www.algolia.com/_llms/api-reference/search.txt): Documentation for API reference / Search.
Measured from the saved file
Linked document
UTF-8 text size
2.7 KB2743 bytes
Token count
704o200k_base encoding
Markdown links
2924 distinct URLs
Fenced code blocks
041 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
Algolia
Opening blockquote
Build search, discovery, and AI experiences with Algolia. Guides, API references, libraries, UI components, and integrations for your stack.
Context architecture
How the content is divided
2 H2 sections organize 29 parsed Markdown links. 0 links point to .md or .markdown paths; 0 link occurrences use another hostname. Linked destinations have not been recursively validated.
H2 section
Links
UTF-8 bytes
Tokens
OpenAPI SpecsLine 11
15
752
222
IndexesLine 31
9
1251
301
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
No MCP or Model Context Protocol term was detected in the captured file. 0 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.
Whole-file size not established by the bounded response
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.
File changes can reveal documentation edits or navigation changes. They do not by themselves measure product release velocity, accuracy, agent adoption or AI visibility.
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.