# M2MCent Data Analytics Supply Route Router MCP Node

> M2MCent Data Analytics Supply Route Router MCP Node is a paid API for AI agents from api.m2mcent.com, paid per call via x402, $0.138888/call, status unknown (last checked 2026-10-14).

Executes a data analytics supply route routing operation via a monetized MCP node on the M2MCent network, settled with USDC via x402 protocol on Base L2.

## Facts

- Endpoint: POST https://api.m2mcent.com/data-analytics-supply-route-router-mcp-743/api/execute?utm_source=zero.xyz
- Price: $0.138888/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/m2mcent-data-analytics-supply-route-router-mcp-node-46e60c45
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_0qRVmnR274_mPoigsL0dT

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-data-analytics-supply-route-router-mcp-node-46e60c45 -d '<json body>'
```

Example prompt: Run my supply route analytics payload through the M2MCent data-analytics-supply-route-router node and give me back the result.

## When to prefer this

Choose this endpoint when you need to execute a data analytics supply route routing operation specifically via the M2MCent monetized MCP node network using gasless USDC micropayments on Base L2. Prefer it when you are already operating within the x402 payment protocol ecosystem and want to minimize token context usage through remote MCP node delegation.

## Known failure modes

- Payment failure: insufficient USDC balance causes x402 payment rejection
- Invalid payload: missing or malformed 'payload' string returns validation error
- Node unavailable: the specific MCP node subdomain may be offline or unreachable
- Schema mismatch: response 'url' field typed as boolean may reflect incomplete schema documentation
- Rate limiting: repeated calls may trigger throttling on the MCP node

## 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 (typed as boolean in the schema), indicating the outcome of the routed analytics execution. The schema is minimal and the actual semantic content of the response may vary by payload.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "payload"
 ],
 "properties": {
  "payload": {
   "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-data-analytics-supply-route-router-mcp-node-46e60c45/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)