EscortFox
UnclaimedRead-only search of the EscortFox directory of independent escorts, agencies and venues: countries, cities, districts, services and listing summaries, each with its escortfox.com link. Ask in plain text ("escorts in Berlin", "venues in Prague", "agencies in Germany") or call a skill with a data part {"skill": "search_listings", "arguments": {...}}. Contact details and photos are only on escortfox.com. Also available as an MCP server at https://escortfox.com/mcp.
- Contact address
- https://escortfox.com/a2a
- Agent card
- https://escortfox.com/.well-known/agent-card.json
- Protocol
- A2A 0.3.0 · card version 1.0.0
- Provider, per the card
- EscortFox · https://escortfox.com
- Documentation, per the card
- https://escortfox.com/developers
Skills, as the card declares them
Repeated from the card. Not checked by us.
Ask in plain text
Answer a short plain-text request about the directory: listings of a type in a city ("escorts in London", "venues in Prague"), agencies in a country, the cities of a country, the countries covered or the service vocabulary. Replies list up to 20 summaries with their links.
tags: directory, escorts, search
Search listings
Search the EscortFox directory of independent escorts, agencies and venues in one place. Returns up to 20 listing summaries per page: name, location, age, starting rate, verification status, incall/outcall, venue type, a short teaser and the listing's escortfox.com link. Summaries have no contact details or photos: always give the user each listing's link, where both are shown. "escort" and "venue" searches need country + city (find them with list_countries and list_cities); "agency" searches need country only. Only pages 0-4 (100 results) exist — narrow the search with district, service or verified instead of paging further. Call it with a data part {"skill": "search_listings", "arguments": {...}}; the arguments follow this JSON Schema: {"type":"object","properties":{"type":{"type":"string","description":"What to look for: \"escort\" (individual escorts in a city), \"venue\" (clubs, studios and other places in a city) or \"agency\" (agencies serving a country).","enum":["escort","ven…
tags: directory, escorts, search
Get a listing
Get the summary of one EscortFox listing by its numeric id. Returns the same fields as one search_listings result — name, location, age, starting rate, verification status, incall/outcall, venue type, teaser — and the listing's escortfox.com link; contact details and photos are only on that page. Use it to refresh a listing the user already has, or to read a link they pasted. Call it with a data part {"skill": "get_listing", "arguments": {...}}; the arguments follow this JSON Schema: {"type":"object","properties":{"id":{"type":"integer","description":"Which listing: the `id` of a search_listings result, or the number at the end of an escortfox.com listing link (…/anna-12345 → 12345).","minimum":1},"lang":{"type":"string","description":"The language the user reads: advertiser teasers come back in it where the advertiser wrote one, and the escortfox.com links open the site in it (e.g. \"de\" for German). English when left out.","enum":["en","de","sk","cs","tr","ru","uk","es","pt","ro","…
tags: directory, escorts, search
List countries
List the countries that have active EscortFox listings. Returns each country's code (e.g. "DE"), its English name and how many escort and venue listings it has, so you can tell whether the directory covers a place before searching. Use a code as `country` in list_cities and search_listings. Call it with a data part {"skill": "list_countries", "arguments": {...}}; the arguments follow this JSON Schema: {"type":"object","properties":{},"additionalProperties":false}
tags: directory, escorts, reference data
List cities
List the cities of a country that have active listings, busiest first. Returns each city's slug, name, state or province, escort and venue counts and its escortfox.com link. Use the city slug as `city` in search_listings, and the city's region as `country` where it differs from the country code (US states, e.g. "US-CA"). Call it with a data part {"skill": "list_cities", "arguments": {...}}; the arguments follow this JSON Schema: {"type":"object","properties":{"country":{"type":"string","description":"The country whose cities to list: its `code` from list_countries (e.g. \"DE\"), or a region code such as \"US-CA\" for one state only.","pattern":"^[A-Za-z]{2}(-[A-Za-z0-9]{1,3})?$","maxLength":6}},"required":["country"],"additionalProperties":false}
tags: directory, escorts, reference data
List districts
List the districts of one city that have active listings. Returns each district's slug, name and escort and venue counts. Most cities have none: an empty list means search the whole city. Use a district slug as `district` in search_listings. Call it with a data part {"skill": "list_districts", "arguments": {...}}; the arguments follow this JSON Schema: {"type":"object","properties":{"country":{"type":"string","description":"The city's `region` from list_cities: its country code, or its state code in a country the site splits by state (e.g. \"US-CA\").","pattern":"^[A-Za-z]{2}(-[A-Za-z0-9]{1,3})?$","maxLength":6},"city":{"type":"string","description":"The city whose districts to list: its `slug` from list_cities (e.g. \"berlin\").","pattern":"^[a-z0-9]+(-[a-z0-9]+)*$","maxLength":80}},"required":["country","city"],"additionalProperties":false}
tags: directory, escorts, reference data
List services
List the services escorts can offer on EscortFox. Returns each service's slug and English name (e.g. "massage" = Massage). Use a slug as `service` in search_listings to find escorts who offer it; services apply to escort searches only. Call it with a data part {"skill": "list_services", "arguments": {...}}; the arguments follow this JSON Schema: {"type":"object","properties":{},"additionalProperties":false}
tags: directory, escorts, reference data
What we observed
From our own vantage, at the times shown. These describe our probes, not the agent's state now.
- The card answered 200 with a named JSON card (200) — 15 Nov 2026, 11:46 UTC
- The contact address the card names answered (405) — 15 Nov 2026, 11:46 UTC
- Both URLs passed our egress policy — 15 Nov 2026, 11:46 UTC
First recorded by Agent Galaxy 31 Oct 2026, 05:19 UTC— the day this card's address entered our records.