REST API documentation
Query the international llmsmap.me directory from applications, agents, and data pipelines. Public read endpoints do not require an API key.
Base URL
https://llmsmap.me/apiThe machine-readable OpenAPI 3.1 contract is available at /openapi.json. It is the source of truth for the public REST surface; MCP uses its own protocol and manifest.
List international websites
GET /api/directory returns approved websites in the international edition.
curl https://llmsmap.me/api/directoryJavaScript
const response = await fetch('https://llmsmap.me/api/directory');
const { items } = await response.json();
for (const site of items) {
console.log(site.product_name, site.llms_txt_url);
}Example response
{
"items": [
{
"product_name": "Example",
"website_url": "https://example.com",
"llms_txt_url": "https://example.com/llms.txt",
"llms_full_txt_url": "https://example.com/llms-full.txt",
"llms_txt_tokens": 1250,
"llms_full_txt_tokens": 5400
}
]
}Filtered and paginated catalog
GET /api/catalog supports search, sorting, and pagination.
| Parameter | Values | Purpose |
|---|---|---|
search | string | Product name or domain |
sort | recommended, newest, ai_ready, alphabetical | Result order |
page | positive integer | Page number |
limit | 1–100 | Items per page |
curl "https://llmsmap.me/api/catalog?search=docs&sort=ai_ready&page=1&limit=20"Requests made through llmsmap.me default to the international edition. The response includesitems, counts, and pagination.
Submission status
GET /api/submission/:id/status?token=… returns safe public status fields. The private status token is returned after submitting a website and must not be shared.
Errors and rate limits
400— invalid request.403— missing or invalid status token.404— resource not found.422— validation failed.429— rate limit exceeded; respect theRetry-Afterheader.
Cache directory responses and avoid polling more frequently than the interface requires.
Agent integration
For AI clients that support Model Context Protocol, use the llmsmap.me MCP server instead of writing a custom REST integration.