# How to make your site and tool ready for agents (slim)

> What an AI agent looks for when it lands on a tool's site, how many of the 966 tools we list have each piece, what doing it on our own site did for us, and where llms.txt fits.

- Full: https://www.anchorterminal.com/blog/how-to-make-your-site-ready-for-agents.md (~1,250 tokens) · this version ~680 tokens · JSON https://www.anchorterminal.com/blog/how-to-make-your-site-ready-for-agents.json · canonical https://www.anchorterminal.com/blog/how-to-make-your-site-ready-for-agents
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · Updated: 2026-10-13

## What agents look for, and who has it

| What an agent looks for | Tools we list that have it |
| --- | --- |
| A changelog | 800 of 966 (83%) |
| A status page | 725 (75%) |
| An llms.txt | 717 (74%) |
| A way to start without talking to sales (free, freemium or pay as you go) | 716 (74%) |
| An OpenAPI description | 523 (54%) |
| An MCP server | 487 (50%) |
| A valid security.txt | 266 (28%) |
| A place in the official MCP registry | 162 (17%) |

All of these come from the listings in our directory [[1]](#ref-1).

## Start with llms.txt

llms.txt is a Markdown file at `/llms.txt` that tells an agent what a site is and where its useful pages are.

Put the pages that matter to an agent in it, the API reference, authentication, rate limits, pricing and errors, rather than the marketing pages.

## Then give every page a Markdown copy

An agent that fetches HTML spends its context on navigation, scripts and cookie banners.

We built it that way because agents don't always read the file you leave for them.

## Describe the API, and keep the boring pages

Publish an OpenAPI description, because any agent that can make an HTTP request can use it, and the [previous post](/blog/how-to-make-your-mcp-server-discoverable) has why we'd do that before an MCP server.

## What it did for us

We built Anchor Terminal agent first, with an llms.txt, a Markdown and JSON copy of every page and an MCP server, and we think that's a big part of why we were found so quickly.

## And claim your listing

If your tool is in our directory, claim it.

## References

Read on 10 October 2026.

[1] Anchor Terminal, the directory, 10 October 2026. Source for the share of tools with each item and llms.txt by grade.

[2] Jeremy Howard, The /llms.txt file, llmstxt.org, 3 September 2024. Source for the proposal, its date and the format.

[3] Anchor Terminal, llms.txt and the build of 10 October 2026. Source for our Markdown and JSON copies and the Accept header.

[4] Anchor Terminal server logs, 1 to 8 October 2026, not published.

[5] Anchor Terminal, For builders, Claiming.

---

- Older: [How to make your MCP server discoverable](https://www.anchorterminal.com/blog/how-to-make-your-mcp-server-discoverable.md)
- Newer: [How to let agents pay you, with x402](https://www.anchorterminal.com/blog/how-to-let-agents-pay-you.md)
- All posts: https://www.anchorterminal.com/blog/index.md