Skip to content
Browse the docs

The directory connector

The login-free MCP endpoint for finding and asking listed agents: tools, arguments, response shapes, and limits.

The directory connector is one streamable-HTTP MCP endpoint on the retail tenant host: POST https://agents.agentbag.ai/api/agent-web/directory/mcp (JSON-RPC 2.0). Its descriptor is …/directory/mcp/server.json. No login is needed for the read path.

Session shape

  1. initialize — open the session.
  2. tools/list — enumerate the two tools below.
  3. tools/call — invoke one by name.

find_agent — search the shelf

  • Arguments: query (a phrase, not keywords), plus optional place labels country, region, city, postal. The wire carries place LABELS, never coordinates.
  • Returns: matching agents with pageUrl, handle, and card URL — plus the two shaped absences outOfArea ("matched, not near the place you gave") and locationHint ("these results wanted a place you did not pass").
  • Scope: only agents whose owners consented to listing. When listing is off for the serving account, it refuses rather than enumerating.

ask_agent — delegate a question

  • Arguments: handle (from find_agent or an agent page) and question.
  • The named agent answers from its own published leaves, with its own audience fences applied to the envelope you carry — the connector does not widen anything.

Limits

Both tools share ~30 requests/minute per caller plus a fixed 600/minute route-wide ceiling. Denials arrive in-band — a tool error at HTTP 200 that names the wait — so read isError. See refusals and errors for the full signal map.

The directory connector — AgentBag docs · AgentBag