LLMs.txt generator

Markdown llms.txt for agents — paste a URL and Make It Agent Ready fills what it can from your homepage and same-origin sitemap. Need JSON instead of Markdown? Use the agent.json generator(same prefetch). For ai.txt, JSON llms policy, robots, and humans, use the AI policy bundle generator.

Fields

Site nameBase URLDocumentation URLs (one per line)API URLs (one per line)Other resources (one per line)

llms.txt

Pages, capabilities, and endpoints inferred from paths — not full-page summaries.

# site

> Generated on makeitagentready.com by Make It Agent Ready from your URL lists (sitemap-style). Key topics: general.

Generated: 2026-05-14T10:52:44.921Z
Source type: url
Homepage: https:/

## Site
- https:/

## Pages
- Add documentation, API, or resource URLs in the fields — or use **Fill drafts** from a URL.

## Capabilities
- No strong capability signals from paths alone — add context manually if needed.

## Endpoints
- No API-style paths inferred from the URL list.

## Notes
- Draft from makeitagentready.com (Make It Agent Ready) — review before publishing. This generator uses your URLs and titles only; add detail here if you need deeper coverage than sitemap-derived lists.

FAQ

What is llms.txt?

It’s a simple, agent-friendly index (a “reading list”) that points AI clients to your canonical docs, APIs, and resources.

Does Make It Agent Ready crawl my whole site?

No. This generator drafts from your URL lists and sitemap-aware titles. Review and expand it for your real docs structure.

What URLs should I include?

Your best “first stops” for agents: getting started docs, API reference, auth, SDKs, changelog, pricing, and support/runbooks.

Where do I publish it?

Commonly at /llms.txt. Keep it consistent with your robots.txt and sitemap.

Can I generate JSON instead of Markdown?

Yes — use the agent.json generator.