# AgentDiet X402-BROKER MCP/API Gateway

> AgentDiet X402-BROKER MCP/API 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 agent requests to 31,390+ MCP servers, x402 APIs, and A2A agents with USDC micropayment settlement on Base

## Facts

- Endpoint: GET https://mcp-gateway.agentdiet.dev/api/diet?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/agentdiet-x402-broker-mcp-api-gateway-1052d976
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_t1jKx7svAkSRVZtNCWHyx

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 agentdiet-x402-broker-mcp-api-gateway-1052d976
```

Example prompt: Route my HTTP GET request to that weather MCP server at https://weather-mcp.example.com and settle the micropayment automatically — I want the response data back with proof of execution.

## When to prefer this

Choose this endpoint when your agent needs a single unified gateway to access thousands of MCP servers, x402 APIs, or A2A agents without managing individual connections, authentication, or micropayment infrastructure. It is ideal for agentic workflows that need deterministic execution with payment settlement in USDC on Base and want ROI/compression proof alongside responses. Prefer it over direct API calls when the target service requires x402 or L402 payment, or when you want brokered routing across a large catalog of agent tools.

## Known failure modes

- Target MCP server unreachable — upstream timeout or 5xx from remote service
- Insufficient USDC balance to settle the $0.001 per-call fee on Base
- Invalid input schema — missing required 'type' or 'method' fields
- Unsupported HTTP method (only GET and POST allowed)
- Target URL not found in the 31,390+ known MCP/x402 registry
- Payment settlement failure on Base blockchain
- Rate limiting or gateway overload returning service unavailable

## 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, a 'status' field ('ok' on success), and an 'roi_proof' object including a compression_ratio_pct value (e.g. 91.4%) demonstrating efficiency gains from routing through the broker.

## 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/agentdiet-x402-broker-mcp-api-gateway-1052d976/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)