# OpenAPI and llms.txt

> Machine-readable entry points to Search1API — an OpenAPI schema for code generators, and llms.txt for agents.

Canonical URL: https://s1.dev/docs/integrations/openapi

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

## OpenAPI schema

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

This is the canonical contract used to validate the [official SDKs](https://s1.dev/docs/integrations/sdks). You can also point a code generator at it to create a lower-level client in another language, or import it into tools such as Postman and Insomnia.

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://s1.dev/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`](https://s1.dev/docs/llms.txt) — a compact index of every documentation page.
- [`/docs/llms-full.txt`](https://s1.dev/docs/llms-full.txt) — the full documentation as clean Markdown, with imports and rendering code removed.

The product-wide [`/llms-full.txt`](https://s1.dev/llms-full.txt) automatically combines the curated product index, the agent-friendly [`/pricing.md`](https://s1.dev/pricing.md), and the generated full documentation.

## Which to use

Writing TypeScript or Python application code? Use an [official SDK](https://s1.dev/docs/integrations/sdks). Generating another language 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](https://s1.dev/docs/integrations/mcp).