# Woosmap llms.txt and Markdown pages for your coding agent

**URL:** <https://forum.woosmap.com/t/woosmap-llms-txt-and-markdown-pages-for-your-coding-agent/178>\
**Category:** Announcements\
**Tags:** ai\
**Created:** [September 29, 2026, 8:57am UTC](https://forum.woosmap.com/t/woosmap-llms-txt-and-markdown-pages-for-your-coding-agent/178 "2026-09-29T08:57:26Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![gael](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.woosmap.com/gael/32/3_2.png) [@gael](https://forum.woosmap.com/u/gael)\
**Post date:** [September 29, 2026, 8:57am UTC](https://forum.woosmap.com/t/woosmap-llms-txt-and-markdown-pages-for-your-coding-agent/178/1 "2026-09-29T08:57:26Z")

</div>

We’ve added a few things to the Woosmap Developers documentation so it works better with coding agents like Cursor, Copilot and Claude Code.

There’s now:

| Resource | What you get |
| --- | --- |
| [`/llms.txt`](https://developers.woosmap.com/llms.txt) | A small index of the docs |
| [`/llms-full.txt`](https://developers.woosmap.com/llms-full.txt) | The full list of doc pages |
| [`/llms-rules.txt`](https://developers.woosmap.com/llms-rules.txt) | Rules and conventions for generating Woosmap API calls |
| [OpenAPI 3.1](https://developers.woosmap.com/assets/woosmap-openapi3.json) | REST endpoints, parameters and schemas |
| `.md` | Add `.md` to any docs URL to get the Markdown version |

They’re also referenced from `robots.txt`.

If you’re using Claude Code, Cursor, etc., you can just add this to your `CLAUDE.md`, `.cursorrules`, `AGENTS.md`, or equivalent:

```auto
Before writing any Woosmap API call, read and follow
https://developers.woosmap.com/llms-rules.txt

```

`/llms.txt` is usually enough to get started. It’s small, and it tells the agent which page covers what. `/llms-full.txt` is the exhaustive list, and the OpenAPI file is what you want when you’re working directly with the REST APIs.

The [API reference pages](https://developers.woosmap.com/api-reference/) are the source of truth for parameter names and allowed values. Guides show examples, but they don’t necessarily cover every option.

If you want the agent to actually call Woosmap at runtime rather than generate code, there’s also the [MCP Server](https://developers.woosmap.com/products/mcp-server/overview/).

> **[Build with AI](https://developers.woosmap.com/products/build-with-ai/)**
>
> Use the Woosmap documentation with LLMs and coding agents: a Markdown version of every page, a routing index, the OpenAPI spec, and a rules file for your agent.

If you’re using this and the agent gets something wrong, feel free to post the prompt and generated code here. That would actually be useful for us to see.