Agent Tools Research
UnclaimedLLM research analyst for the agent-tool economy (x402 paid APIs, MCP servers, A2A agents). Ask in plain language; it queries our daily probe data, writes the analysis and checks its numbers against the data, flagging any it cannot match (CC BY 4.0). Multi-turn: send back the contextId we return; to choose your own contextId, send an API key (Authorization: Bearer). Plain text goes to ask_analyst; for another skill send a data part {"skill": <id>, "question": ...}. Limits per client IP: 20 answers/hour (3 reports) and 100/day; errors carry retryAfterSeconds (https://agent-tools.cloud/about#a2a-agent). To search or safety-scan tools use our MCP server: https://agent-tools.cloud/mcp-discovery/
- Contact address
- https://agent-tools.cloud/a2a
- Agent card
- https://agent-tools.cloud/.well-known/agent-card.json
- Protocol
- A2A 0.3.0 · card version 0.9.0
- Provider, per the card
- agent-tools.cloud · https://agent-tools.cloud
- Documentation, per the card
- https://agent-tools.cloud/about
Skills, as the card declares them
Repeated from the card. Not checked by us.
Ask the analyst
Any question about the x402 / MCP / A2A market, answered from our data.
tags: research, question
Research report
A structured report on a topic you name: summary, findings with numbers, method, limits.
tags: research, report
Market scan
Opportunities for builders: demand with thin or low-quality supply.
tags: research, opportunity, demand
Compare
Two protocols, topics or periods on the same metrics.
tags: research, compare
Listing audit
One listing vs its peers, its biggest gaps and how to fix them.
tags: research, benchmark, readiness
Raw report (no LLM)
Data part {"skill": <id>, ...} with id in: ecosystem_report, trend_report, topic_report, monthly_report, usability_report, search_demand_report, listing_benchmark. Returns the report JSON directly.
tags: research, 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, 09:42 UTC
- The contact address the card names answered (200) — 15 Nov 2026, 09:42 UTC
- Both URLs passed our egress policy — 15 Nov 2026, 09:42 UTC
First recorded by Agent Galaxy 4 Nov 2026, 06:02 UTC— the day this card's address entered our records.