# M2MCent IoT Supply Route Aggregator MCP Node

> M2MCent IoT Supply Route Aggregator MCP Node is a paid API for AI agents from api.m2mcent.com, paid per call via x402, $1.071092/call, status unknown (last checked 2026-10-22).

Executes IoT supply route aggregation queries via a monetized MCP node with gasless USDC micropayment settlement on Base L2

## Facts

- Endpoint: POST https://api.m2mcent.com/iot-supply-route-aggregator-mcp-808/api/execute?utm_source=zero.xyz
- Price: $1.071092/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-22
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/m2mcent-iot-supply-route-aggregator-mcp-node-5d6d042c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_s649ac1DHw3Rr4KLNJR5k

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 m2mcent-iot-supply-route-aggregator-mcp-node-5d6d042c -d '<json body>'
```

Example prompt: Can you query the IoT supply route aggregator to find the best available supply chain routes for my logistics network?

## When to prefer this

Choose this endpoint when you need IoT supply route aggregation specifically and are operating within the M2MCent x402 monetized MCP ecosystem with USDC payment capability on Base L2. It is suitable for agents that already have x402 payment infrastructure configured and need supply chain routing data from IoT-connected nodes without large token context overhead.

## Known failure modes

- Payment failure: insufficient USDC balance for $1.07 micropayment via x402 protocol
- Invalid prompt: missing or malformed required 'prompt' field returns validation error
- Node unavailability: the specific MCP node (808) may be offline or unresponsive
- Response schema mismatch: 'url' returned as boolean rather than a URL string may indicate a stub or misconfigured node
- Rate limiting: repeated calls to the same node may trigger throttling

## How this service works

The premier global index of 1,069 monetized MCP nodes across 205 specialized subdomains. Gasless USDC runtime settlements via x402 V2 Spec on Base L2. Save 95% token context.

## Output

Returns a JSON object with a 'url' field (boolean) indicating the result of the supply route aggregation query execution. The response schema is minimal and may represent a redirect URL or availability flag for the aggregated route data.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "prompt"
 ],
 "properties": {
  "prompt": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "url"
 ],
 "properties": {
  "url": {
   "type": "boolean"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/m2mcent-iot-supply-route-aggregator-mcp-node-5d6d042c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.m2mcent.com](https://www.zero.xyz/host/api.m2mcent.com/llms.txt)