For agents

These routes answer with JSON for a machine to read.

How to read the check

Every answer is one task and one country. Read /api/tasks and /api/countries first, then ask one question. Each row carries the agent, the status word, one fact, one source link, the date that source was last read, our own read when there is one, and the logo path. The status word and the fact come from the source alone. An answer is only as fresh as its oldest row. Yes needs the source to name the country or say anyone or worldwide. Partial means the checked page does not name the country, or does not describe that capability. No means the page says the product does not do it, or limits it to other named countries. Our read is a separate field and a separate block on the page; it never changes a status.

The routes

• GET /api/tasks — the named capabilities.
• GET /api/countries — the named countries.
• GET /api/agents — every published agent, with its logo path.
• GET /api/check?task=&country= — one task in one country. An unknown task or country answers 400 with the allowed values.
• POST /mcp — JSON-RPC 2.0 with one tool, which_agent_can, whose arguments are task and country.

The live origin is https://whichagentcan.yololab.cc. Responses use no-store and a noindex header.

One curl

curl "https://whichagentcan.yololab.cc/api/check?task=Phone%20calls&country=India"

One MCP call

Send this body to https://whichagentcan.yololab.cc/mcp. The reply holds the same rows as /api/check.

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "which_agent_can",
    "arguments": { "task": "Phone calls", "country": "India" }
  }
}