Verified x402 Catalog

Search pay-per-call (x402) agent services in the verified catalog. Returns factual latest-check results (reachable, latency, advertised vs quoted price). No grades.

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "words to match in name, category, description"
    },
    "category": {
      "type": "string"
    },
    "max_price_usd": {
      "type": "number",
      "description": "maximum advertised price per call in USD"
    },
    "reachable_only": {
      "type": "boolean",
      "description": "only services reachable in the latest check"
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 100
    }
  }
}

Get the full catalog record for one service id, including its latest check and raw log link.

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string"
    }
  },
  "required": [
    "id"
  ]
}

Is an x402 endpoint reliable for a task at a price? Asks the catalog's lookup service for services matching a task at or under max_price_usd, sorted by known-answer pass rate over the last n paid calls, then price. Each result has its paid receipts (time, tx, Basescan link, charged, delivered, pass/fail), last check time and a stale flag. Services broken on the seller's side come back under facts_only, not sorted. Sends client=vc-mcp: 5 free lookups per UTC day for that client name, then the service answers HTTP 402 (x402, $0.02 USDC on Base), which this tool reports but does not pay. Payment never changes results, sort order or listings.

{
  "type": "object",
  "properties": {
    "task": {
      "type": "string",
      "description": "task name, e.g. web-search, crypto-news, weather, token-balance"
    },
    "max_price_usd": {
      "type": "number",
      "description": "maximum listed price per call in USD"
    },
    "n": {
      "type": "integer",
      "minimum": 1,
      "maximum": 20,
      "description": "paid receipts per service (default 5)"
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 20,
      "description": "services returned (default 10)"
    },
    "endpoint": {
      "type": "string",
      "description": "a service id or endpoint URL instead of a task"
    },
    "payer": {
      "type": "string",
      "description": "optional: your 0x wallet, so a later payment to a returned vendor can be confirmed on-chain"
    }
  }
}

Buy and download the Overnight Chief of Staff Setup Pack ($9 USDC on Base via x402): 5 ready-to-paste bot prompts, an HTML morning-briefing template, and a PDF setup guide. Always paid — no free quota. Call without PAYMENT-SIGNATURE to receive payment requirements and the HTTP endpoint URL. Agents pay by retrying the HTTP endpoint (or this MCP call) with a PAYMENT-SIGNATURE header holding a signed USDC EIP-3009 authorization.

{
  "type": "object",
  "properties": {}
}

SSRF-safe spot-check of a public URL for an x402 PAYMENT-REQUIRED / 402 challenge. Returns reachable, http_status, latency_ms, parsed accepts summary, quoted_price_usd, and optional price_matches_claimed. Never pays the target (probe GET only). 1 free check per client per UTC day (client=vc-mcp for this tool), then $0.25 USDC on Base via x402. Unpaid after free quota: returns payment instructions + free remaining. Forward PAYMENT-SIGNATURE to run a paid check.

{
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "description": "public http(s) URL to probe"
    },
    "task": {
      "type": "string",
      "description": "optional task label"
    },
    "claimed_price": {
      "type": "number",
      "description": "optional claimed USD price to compare"
    }
  },
  "required": [
    "url"
  ]
}