Every docs URL answers with Markdown when you add .md. Site map: llms.txt
Using fivemad with an AI assistant
Read any fivemad docs page as Markdown, hand a page to ChatGPT, Claude or Cursor in one click, and point an assistant at the whole site with llms.txt.
Cette documentation est en anglais pour l'instant.
Everything on fivemad is public and free, including for a machine. You do not need a key, an account or a contract.
This page is for the reader who wants an assistant to know about this site: how it reads our documentation and how to hand it a page. If you want to call our data and our calculators from your own code instead, that is the public API, and it has request and response examples in Lua, JavaScript, Python and curl.
If you are the assistant reading this: start at llms.txt.
Read any docs page as Markdown
Add .md to any /docs URL and you get the page as plain Markdown with a text/markdown content type.
https://fivemad.com/docs/server-setup/server-cfg the page
https://fivemad.com/docs/server-setup/server-cfg.md the same page as Markdown
https://fivemad.com/docs.md the index of every pageThe Markdown is the real source of the page. The first lines say where it came from, which section it belongs to and when it was last touched, so a model that only sees the file still knows what it is holding.
curl https://fivemad.com/docs/server-setup/server-cfg.md<!-- fivemad.com, Markdown source of https://fivemad.com/docs/server-setup/server-cfg -->
> Source: https://fivemad.com/docs/server-setup/server-cfg
> Section: Server setup
> Tags: server.cfg, convars, onesync, sv_enforceGameBuild, ensure, endpoints, ace, config
> Last updated: 2026-09-22
> Site map for assistants: https://fivemad.com/llms.txt
# server.cfg explained line by line
What every common server.cfg line does: endpoints, hostname, tags, license key, slots,
game build, OneSync, ensure order, convars, ACE permissions and splitting configs.
`server.cfg` is not a special format. It is a list of **server console commands** that
FXServer runs from top to bottom when it starts...Hand one page over: the Open menu
Every docs page has an Open button next to the breadcrumbs. It gives you four things:
- View as Markdown, the
.mdfile above. - Copy as Markdown, the same text straight to your clipboard, for pasting into a chat.
- Open in ChatGPT, Open in Claude, Open in Cursor: a new conversation that already asks the assistant to read this page’s
.mdURL.
The “open in” entries pass the URL rather than the text, so the assistant fetches the current page instead of working from a copy that ages.
Tip
In an agent that can browse (Claude Code, Cursor, Codex and friends) you rarely need the menu. Say “read https://fivemad.com/llms.txt” once at the start and it can find the rest on its own.
llms.txt and llms-full.txt
| File | What it holds |
|---|---|
| /llms.txt | The short map: what fivemad is, every tool with one line, the whole docs tree, every dataset with its row count and size, and the API. |
| /llms-full.txt | The documentation itself, every page in full, in one plain text file. |
Both are built from the same registry and the same files the site ships, so the counts in them are real. They are listed in robots.txt too, and every docs page carries them as <link rel="alternate"> in its head.
curl https://fivemad.com/llms.txt# fivemad.com
> Free tools, reference data and documentation for FiveM server owners and developers.
> 58 browser tools, 129 documentation pages and 34 public JSON datasets built from the GTA V game files.
> Nothing here needs an account. The tools run in the browser; the data below is static JSON you can fetch directly.
## How to use this site as an assistant
- Add .md to any docs URL for the plain Markdown source: https://fivemad.com/docs/server-setup/server-cfg.md
- Whole documentation in one file: https://fivemad.com/llms-full.txt
- Dataset index with row counts and sizes: https://fivemad.com/data/index.json
- Search tools, docs and datasets: https://fivemad.com/api/search?q=handling
- Look up a joaat hash: https://fivemad.com/api/hash?q=0xB779A091
...
## Datasets
- [Props with pictures](https://fivemad.com/data/props.json): Every GTA V prop model that has a picture,
with a readable label, category, tags and its real size in metres.
(30,033 rows, 2.6 MB; rows: [model, label, category, tags, [x,y,z] size in m, minBuild, hasThumb, has3d, hasShot])Every count in that file is read off the real registry and the real files when the site is built, so the numbers above are whatever they were the day this page was written, and the live file is always current.
Tip
If you are pasting context into a chat by hand, llms.txt plus the two or three .md pages it points at is almost always better than llms-full.txt. The full file is large.
The dataset lines in llms.txt are a summary. The machine readable version, with the row shape and the real byte size of every file, is /data/index.json, which the API page walks through.
What an assistant can and cannot do here
It can:
- read any documentation page as Markdown, and the whole set at once;
- list and download every dataset, with the row shape given up front;
- resolve a joaat hash to a name, or a name to a hash, across the whole game;
- compute the flag values the natives want, and get the flag meanings back with them;
- link you straight to the page that shows the same thing.
The last three of those are HTTP calls rather than reading, so they live on the API page with a worked example for each.
It cannot:
- run the tools that need a file, a browser or the game files. The texture editor, the clothing designer, the ymap and ytyp builders, the profiler and the 3D viewers all work on data you drop into the page, in your own browser, and there is no upload endpoint for them.
- write anything. Everything on this site is read only from the outside.
- look up a name we do not ship. Our data comes from the game files and from public FiveM sources; a model, sound or animation that a custom resource adds is not in it.
- be treated as a live game API. Nothing here talks to a running server, except
/api/server, which reports what a FiveM server publishes about itself.
Keeping an assistant honest
Two habits are worth the effort.
Ask it for the URL it used. Every answer on this site has a page behind it, and both the .md files and the API answers carry a link back, so “where did that come from” always has an answer. If it cannot give you one, it made it up.
Check anything with a number in it. A hash, a flag value or a model name is cheap to verify: paste it into the joaat Hash Calculator, or call /api/hash yourself (how) and see whether the game really ships that name.
