API (for agents)

If you're an agent, you don't need this page - you need data. Skip the prose below and go straight to a vendor's record.

The pattern

For any cataloged vendor, fetch:

/vendor/{vendor_id}/AgentRouting.json
/vendor/{vendor_id}/AgentContext.json

AgentRouting.json always exists once a vendor has been scanned. AgentContext.json is present on vendors where independent research found verified discrepancies or documented human handoff requirements - things that would cause a transaction to fail, produce an incorrect outcome, or mislead a user. A 404 on AgentContext.json means the vendor was checked and nothing cleared the bar, not that it hasn't been examined.

When AgentRouting.json contains a context_advisory field, an AgentContext record exists for that vendor. Fetch the advisory_url before completing any transaction.

Example, real data: /vendor/booking-com/AgentRouting.json

Example AgentContext: /vendor/booking-com/AgentContext.json

Searching by keyword or protocol

/agent-tools/v1/lookup is live. Three independent, combinable parameters:

• query - searches vendor names, tags, and confirmed protocol names all at once.
• protocol - exact match against a protocol name. Narrows to vendors with that protocol confirmed.
• has_agent_interface - exact match against "true", "false", or "partial".

Any combination works, including none at all:

Valid values for protocol

A2A, ACP, AP2, MCP, MPP, NLWeb, UCP, WebMCP, x402, openai_apps_sdk, proprietary, self_declared_discovery

Valid values for has_agent_interface

true, false, partial

Searchable tags

accommodation activities aeg africa airline alibaba alphabet american-airlines-group apartment api-forward app-native appointment-booking asia asia-pacific attractions auction australia autonomous avios banking bike bitcoin blockchain booking booking-holdings brokerage budget business-travel c2c car-rental carpooling cefi central-europe china clinic coin concerts convenience corporate-travel costar-group cruise crypto defi delivery derivatives developer-friendly dex direct-booking direct-buying direct-to-consumer discount diy doctor ecommerce electronics emerging-markets enterprise-holdings europe events exchange expedia-group expense-management experiences fashion finance fintech flight food food-delivery france furniture germany global goto-group grocery handmade hardware healthcare hertz-corporation home home-improvement home-search hotel ihg-group independent independent-music india indonesia infrastructure italy latin-america lending lightning listing live-events live-nation logistics-first long-distance long-haul low-cost-carrier loyalty-program marketplace membership mens-health merchant metasearch micro-mobility middle-east mls mobility mortgage move-inc museums named-acp-partner named-ap2-partner named-mpp-partner named-ucp-partner new-zealand no-fee oneworld onramp ordering ota payment pet pharmacy platform poland portugal premium prescription pricing primary-market property quick-commerce rail real-estate rental resale restaurant retail retail-health reviews ride-hailing ride-sharing saas sap scheduling scooter sea-group secondary-market self-driving shared-mobility short-term-rental solana south-korea southeast-asia spain sports stablecoin star-alliance stubhub-parent subscription super-app taiwan telehealth theater ticketing tours train transfer transportation travel tripadvisor-group uae uber uk us us-carrier vacation-rental viagogo virtual-care wallet walmart web3 wholesale zillow-group

Each tag links to a human-readable page listing vendors that carry it.

The response

{
  "query": "hotel",
  "protocol_filter": null,
  "has_agent_interface_filter": null,
  "results": [
    {
      "vendor_id": "booking-com",
      "vendor_domain": "booking.com",
      "has_agent_interface": "partial",
      "confirmed_protocols": ["MCP", "openai_apps_sdk", "proprietary"],
      "tags": ["accommodation", "booking", "hotel", "ota", "travel"],
      "record_url": "/vendor/booking-com/AgentRouting.json"
    }
  ]
}

This returns a list of candidates, not a full record - fetch a result's record_url for the actual AgentRouting data once you've picked a vendor. Results only include vendors with real, current scan data - vendors in the catalog that haven't been scanned yet are excluded rather than returned as dead ends.

What you'll get back

Each protocol entry has a status - confirmed_present, not_found, unable_to_verify, or confirmed_absent - never a ranking, never a trust score. not_found means we checked and found nothing; unable_to_verify means the check itself was blocked. Both are honest, both are common, neither means the vendor did anything wrong.

MCP interface

RoloCache exposes a native MCP server for agents that support the Model Context Protocol. This is the preferred channel — no HTTP parsing, no URL construction, just call the tools directly.

Connect via streamable HTTP at:

https://www.rolocache.com/mcp/

Available tools:

• get_catalog_info - live catalog metadata, all valid filter values, all known tags. Call this first if you need to know what's available.
• lookup_vendors - search by query, protocol, and/or has_agent_interface. Returns lightweight candidate list.
• get_vendor - fetch the full AgentRouting record for a specific vendor. If a context_advisory is present in the response, fetch the advisory_url before completing any transaction.

The two-step pattern:

1. Call lookup_vendors with a keyword or filter to get candidates.
2. Call get_vendor with the vendor_id for the vendor you need.

Fetch the full record only for the vendor you actually intend to use — lookup_vendors results are intentionally lightweight.

Registry listings

RoloCache is listed on the following MCP registries and directories:

• Official MCP Registry — io.github.rolocache/agent-advisories
• Smithery — @rolocache/agent-advisories