Skip to content

Who's calling Agenstry?

Every search, skill lookup, MCP lookup, route decision and compose call leaves a row in our call log, with the caller's inferred host (Claude Desktop, OpenAI Responses API, Cursor, n8n…), API surface, and country. Free + public because the answer is positioning, not private signal. Connect your AI →

75,669
unique visitors
22
search queries
103
API calls
30-day window · 870,376 total events logged (166,942 page views + 359 search impressions + 103 API hits)

By AI host (caller_kind)

Inferred from User-Agent · see full label reference →
Other crawler 691,525 (79.5%)
Web browser 170,282 (19.6%)
Python (httpx) 4,774 (0.5%)
Unknown (no UA) 1,381 (0.2%)
ChatGPT (browse) 1,154 (0.1%)
curl 1,037 (0.1%)
Agenstry peer 57 (0.0%)
Claude (browse) 46 (0.0%)
Perplexity (browse) 34 (0.0%)
ClaudeBot (training crawler) 30 (0.0%)
Amazonbot 13 (0.0%)
Twitter / X link preview 8 (0.0%)
BaiduSpider 6 (0.0%)
Go http.Client 6 (0.0%)
Python (requests) 6 (0.0%)

By API surface

rest 680,485
web 189,788
a2a 103

By country (top 25)

US 287
PL 41
AU 28
CH 27
NZ 25
DE 24
JP 23
BR 20
IN 18
ES 17
ID 12
BE 11
GB 11
MY 10
IT 9
KR 9
SG 6
CN 5
SE 4
NL 3
RU 3
FR 2
AT 1
EC 1
FI 1

Most-searched skills (30d)

Aggregated from /a2a · /mcp · /api/v1/skills · web search

supply_gaps 8
get_agent 3
index_stats 2
money_flows 2
trends_summary 2
flows_summary 1
get_agent_full 1
hello 1
hospitality.hotel.reservations 1
keyword_search_summary 1
similar_agents 1

What's behind this page

Every API surface (/a2a · /mcp · /api/v1/skills · /api/search · /api/route · /api/compose · the managed-runtime /agents/{domain}/a2a + /try proxy) routes its audit log through one helper at app/call_log.py. The helper extracts the caller's User-Agent (mapped to one of ~25 known hosts), IP-derived country code (via Cloudflare's CF-IPCountry header), referer hostname, and (when an A2A peer agent is calling) the peer's identity from the message metadata or X-Agent-Caller header. The row goes into agent_call_logs fire-and-forget so observability never adds latency to the hot path.

What stays private to owners: per-API-key breakdown on the agent dashboard. What's public: this page + per-skill / per-MCP usage badges on /skills and the MCP browser.