# M2MCent Supply Chain Yield Router MCP Node

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

Executes a supply-chain yield routing operation via a monetized remote MCP node on the M2MCent network, settling payment gaslessly in USDC over Base L2 via the x402 V2 protocol.

## Facts

- Endpoint: POST https://api.m2mcent.com/supply-chain-yield-router-mcp-580/api/execute?utm_source=zero.xyz
- Price: $1.399872/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/m2mcent-supply-chain-yield-router-mcp-node-b9a17824
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_TW0zhwoVBo1HJdC7hOEz7

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-yield-router-mcp-node-b9a17824 -d '<json body>'
```

Example prompt: Run my supply chain yield routing job through M2MCent's MCP node — here's the payload I need processed: '{"shipment_id":"SC-4821","yield_target":0.92,"route":"warehouse-A-to-hub-B"}'.

## When to prefer this

Choose this endpoint when you need to execute a supply-chain yield routing task through a monetized remote MCP node that settles fees gaslessly in USDC on Base L2. It is appropriate when your workflow accepts a single string payload and only requires a boolean success confirmation in return. Prefer alternatives if you need rich structured output, detailed error diagnostics, or a free-tier operation without per-call USDC fees.

## Known failure modes

- Insufficient USDC balance causes payment failure and a 402 response
- Malformed or missing 'payload' field results in a validation error
- Node unavailability on the M2MCent network returns a non-200 status
- x402 protocol settlement timeout leads to execution not being confirmed
- Invalid JSON string in payload may cause silent processing failure with status: false

## 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 single boolean 'status' field indicating whether the supply chain yield routing execution succeeded (true) or failed (false). No additional detail or data payload is returned.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

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

## More

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