OpenAPI and llms.txt

Machine-readable entry points let tools discover Search1API without scraping the rendered docs.

OpenAPI schema

https://api.search1api.com/openapi.json

Point a code generator at it and you get a typed client in your language, no hand-written wrapper needed. It is also what lets tools like Postman, Insomnia or an agent framework import the API in one step.

Every response we serve advertises it too, via a Link header with rel="service-desc" — so a client that follows link relations can find the schema on its own.

llms.txt files

https://www.search1api.com/llms.txt

This is the curated, product-wide index for language models: product overview, pricing, documentation, agent interfaces, and the OpenAPI schema, all as links with one-line descriptions.

The docs app also publishes two files generated from the current Fumadocs source:

• /docs/llms.txt — a compact index of every documentation page.
• /docs/llms-full.txt — the full documentation as clean Markdown, with imports and rendering code removed.

The product-wide /llms-full.txt automatically combines the curated product index, the agent-friendly /pricing.md, and the generated full documentation.

Which to use

Generating a client, or importing the API into a tool? Use the OpenAPI schema. Helping a model discover the product? Use the root llms.txt. Providing the documentation as context? Use /docs/llms-full.txt or the combined root /llms-full.txt. Building an agent that will actually call the API? Use the MCP server.