# M2MCent IoT Biometric Router MCP Node

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

Executes a payload against a monetized IoT biometric router MCP node, returning a boolean report result via x402 micropayment settlement.

## Facts

- Endpoint: POST https://api.m2mcent.com/iot-biometric-router-mcp-238/api/execute?utm_source=zero.xyz
- Price: $0.42741/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/m2mcent-iot-biometric-router-mcp-node-95b86012
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_bW12B9Jgo1WeatJtf23Qi

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-biometric-router-mcp-node-95b86012 -d '<json body>'
```

Example prompt: Send this biometric sensor payload to the M2MCent IoT biometric router MCP node and give me back the execution report result.

## When to prefer this

Choose this endpoint when you need to execute a task specifically on the IoT biometric router MCP node within the M2MCent network, and you require gasless USDC micropayment settlement via x402 on Base L2. It is suited for agents operating in IoT biometric pipelines that need lightweight boolean confirmation of execution.

## Known failure modes

- Payment failure — insufficient USDC balance or x402 settlement rejection results in 402 Payment Required
- Invalid payload format — missing or malformed 'payload' string returns a 400 error
- Node unavailability — the specific MCP node subdomain may be offline, returning 503
- Ambiguous boolean result — the 'report' field provides no detail beyond true/false, making error diagnosis difficult
- Timeout — remote MCP node execution may exceed response time limits

## 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

A JSON object containing a single boolean field 'report' indicating whether the execution succeeded or produced a positive result.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/m2mcent-iot-biometric-router-mcp-node-95b86012/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)