Back to A2A agents

EscortFox

https://escortfox.com/.well-known/agent-card.json
● healthy

Read-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.

Transport
JSONRPC
Protocol
1.0
Price
—

A2A readiness

B · 81/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here B, 87.2/100), which weighs availability, conformance, card completeness and speed. How the two differ

Valid Agent Card 10/10 Parseable Agent Card with the required fields.
Live JSON-RPC 25/25 Endpoint answers A2A JSON-RPC (605 ms).
Protocol version 10/10 Declares A2A 1.0 with supportedInterfaces[] (v1 card shape).
JWS signature 0/10 Card is unsigned.
Uptime (30 days) 15/15 3/3 probes succeeded; final after 5 probes in 30 days.
Skill declaration 10/10 Declares 7 skill(s) with structured metadata.
Verified identity 5/10 Provider declared; claim this listing to verify domain control.
Freshness + modern flags 4/5 seen in a source within 7 days.
Security declaration 2/5 Explicitly declares no authentication (public).
Responsiveness: Responsive (605 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).
Measured 2026-11-11.
Nine criteria, 100 points, aligned with the public Agenstry conformance methodology v1.1. Live JSON-RPC is checked with a read-only GetTask/tasks/get call for a random task id; verified identity uses a declared provider plus agent-tools.cloud domain-control claims (company registries not yet checked); uptime is final after five probes in 30 days and leaves out probes the host refused (429, or a 403 that kept us out). Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 6,312 reachable A2A agents in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness
Higher than 95% of peers
This listing 81 · peer median 54
Latency
Faster than 23% of peers
This listing 659 ms · peer median 398 ms

Where it loses the most points, and how to win them back

  • JWS signature −10 — Sign the Agent Card (JWS).
    Now: Card is unsigned.
  • Verified identity −5 — Claim the listing and prove control of its domain.
    Now: Provider declared; claim this listing to verify domain control.
  • Security declaration −3 — State how to authenticate (an auth scheme, or that none is needed).
    Now: Explicitly declares no authentication (public).

How many agent tools actually work · All statistics

Adoption signals

Public signals from outside this directory, shown for context. They do not change search order or grades.

Site rank (Tranco)
#629,800 of the top 1M
escortfox.com · list of 2026-11-11

Skills

How to call

A2A endpoint (JSONRPC)
https://escortfox.com/a2a
Agent card
https://escortfox.com/.well-known/agent-card.json
Documentation
https://escortfox.com/developers
Homepage
https://escortfox.com

Listed in

Directories this entry was found in.

agenstry since 2026-10-31 a2a-registry since 2026-10-31