# M2MCent Supply Chain Metadata Router MCP Node

> M2MCent Supply Chain Metadata Router MCP Node is a paid API for AI agents from api.m2mcent.com, paid per call via x402, $0.226275/call, status unknown (last checked 2026-10-12).

Executes a supply-chain metadata routing operation via a monetized MCP node in the M2MCent network, returning a boolean analysis result.

## Facts

- Endpoint: POST https://api.m2mcent.com/supply-chain-metadata-router-mcp-460/api/execute?utm_source=zero.xyz
- Price: $0.226275/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/m2mcent-supply-chain-metadata-router-mcp-node-2eee4bfd
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_cmsTHxL-1xoLy9CpQBUkB

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-supply-chain-metadata-router-mcp-node-2eee4bfd -d '<json body>'
```

Example prompt: Can you route this supply chain metadata payload through the M2MCent supply chain metadata router and tell me whether the analysis comes back true or false? Here's the payload: '{"shipment_id":"SC-9921","origin":"Shanghai","destination":"Los Angeles","status":"in_transit"}'

## When to prefer this

Choose this endpoint when you need to route supply chain metadata through M2MCent's monetized MCP node network and receive a quick boolean analysis result, especially if you are already operating within the x402 USDC micropayment ecosystem on Base L2. It is distinct from general-purpose analytics APIs because it combines automated payment settlement with specialized MCP node routing.

## Known failure modes

- Payment failure: insufficient USDC balance or x402 payment not accepted
- Invalid payload: missing or malformed 'payload' string field returns validation error
- Network timeout: remote MCP node unavailable or slow to respond
- Unexpected boolean ambiguity: result may not reflect complex routing logic clearly
- Node unavailability: specific subdomain MCP node may be offline in the 205-node network

## 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 containing a single boolean field 'analysis' indicating the outcome of the supply chain metadata routing computation — true or false.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/m2mcent-supply-chain-metadata-router-mcp-node-2eee4bfd/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)