# X402-BROKER MCP Gateway

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

Routes and executes HTTP requests across 31,390+ MCP servers, x402 APIs, and A2A agents with micropayment settlement in USDC on Base

## Facts

- Endpoint: GET https://mcp-gateway.agentdiet.dev/api?utm_source=zero.xyz
- Price: $0.001/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-gateway-616bc82f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_vtLL4GGcQM0GxghU9c7Pg

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-gateway-616bc82f
```

Example prompt: Route this GET request through the MCP gateway to fetch data from a tool at that URL — handle the x402 micropayment settlement automatically and return the result.

## When to prefer this

Choose this endpoint when you need a single unified gateway to reach any of 31,390+ MCP servers, x402 APIs, or A2A agents without managing individual connections or payment channels. It is especially useful when your agent needs to dynamically discover and call tools across multiple AI protocols (MCP, x402, L402, MPP, A2A) and wants automatic USDC micropayment handling on Base. Prefer this over direct API calls when you want protocol abstraction and unified billing.

## Known failure modes

- Insufficient USDC balance for micropayment settlement — payment rejected
- Invalid or unreachable target URL — connection timeout or DNS failure
- Unsupported HTTP method supplied (only GET/POST allowed)
- Target MCP server or x402 API returns an error — propagated in response
- Missing required 'input' field or malformed request schema — 400 validation error
- Network congestion on Base causing settlement delay

## 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 proxied response payload, a 'status' field ('ok' on success), and a 'roi_proof' object including a compression_ratio_pct value indicating efficiency of the call.

## 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": {
      "url": {
       "type": "string"
      },
      "mode": {
       "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-gateway-616bc82f/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)