# X402-BROKER MCP Mesh Dispatch

> X402-BROKER MCP Mesh Dispatch is a paid API for AI agents from mcp-gateway.agentdiet.dev, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-22).

Routes and executes queries across 31,390+ MCP servers, x402 APIs, and A2A agents via a single unified mesh dispatch endpoint, settling in USDC on Base.

## Facts

- Endpoint: GET https://mcp-gateway.agentdiet.dev/v1/mesh/dispatch?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-22
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-broker-mcp-mesh-dispatch-f5b8b1fe
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_DowZp34Zl34SxEJrwpk8D

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability x402-broker-mcp-mesh-dispatch-f5b8b1fe
```

Example prompt: Search the MCP mesh for tools that can summarize a webpage — dispatch a GET query with 'summarize webpage' and return whatever the best matching server responds with.

## When to prefer this

Choose this endpoint when you need to discover and invoke capabilities across a large, heterogeneous network of MCP servers, x402 APIs, or A2A agents without knowing which specific server to call. It is ideal when building agent workflows that need broad API coverage without managing hundreds of individual integrations. Prefer it over direct API calls when you want unified routing, automatic micropayment settlement in USDC, and access to 31,000+ tools through a single dispatch interface.

## Known failure modes

- Query parameter missing or malformed — returns error if required 'input' object is absent
- No matching MCP server found for query — may return empty data or routing failure
- Payment settlement failure on Base — if USDC transaction fails, request is rejected
- Invalid method enum — only GET and POST are accepted
- Upstream MCP server timeout or unavailability — partial or error response returned

## How this service works

Deterministic B2A/A2A/MCP/x402/MPP/L402 execution and intelligence node at https://mcp-gateway.agentdiet.dev settling in USDC on Base.

## Output

Returns a JSON object with a 'data' field containing the dispatched server's response, a 'status' field (e.g. 'ok'), and an 'roi_proof' object showing compression ratio (e.g. 91.4%) as proof of efficiency of the mesh routing.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "POST"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {
      "query": {
       "type": "string"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {},
  "status": "ok",
  "roi_proof": {
   "compression_ratio_pct": 91.4
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-broker-mcp-mesh-dispatch-f5b8b1fe/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from mcp-gateway.agentdiet.dev](https://www.zero.xyz/host/mcp-gateway.agentdiet.dev/llms.txt)