# Limits and terms of use

> Rate limits, caching and terms of use of the EscortFox Public API, MCP server, A2A agent and WebMCP tools: attribution required, no bulk copying.

Source: https://escortfox.com/developers/limits. Index of all EscortFox developer docs: https://escortfox.com/developers/llms.txt

The same limits and terms apply to the [Public API](https://escortfox.com/developers/api.md), the [MCP server](https://escortfox.com/developers/mcp.md), the [A2A agent](https://escortfox.com/developers/a2a.md) and the [WebMCP tools](https://escortfox.com/developers/webmcp.md).

## Limits

- 30 requests per minute and 500 per day per client address.
- `GET /public/v1/listings/{id}`: additionally 10 per minute and 100 per day.
- AI assistants that call from their providers' published egress ranges (ChatGPT, Claude, Perplexity) carry many users on one address, so they get 600 per minute and 20,000 per day, and 200 per minute and 5,000 per day for listing lookups.
- Searches are city-scoped, 20 results per page, and only the first 5 pages are available. Narrow the search (district, service) instead of paging further.
- Over a limit you get `429 Too Many Requests` with a `Retry-After` header in seconds; when the service as a whole is busy, `503` with `Retry-After`. Please wait that long rather than retrying at once.
- Responses carry `Cache-Control`; please honour it.

## Terms of use

- **Attribution is required.** Any display of data from the API must link to escortfox.com, using each item's `url`.
- Bulk copying, mirroring, scraping or reselling the data is not allowed, nor is using it to build or seed another directory.
- The limits above are part of the terms. Working around them (rotating addresses, parallel clients) is a breach.