# NB-IoT Cellular MCP

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

Processes NB-IoT (Narrowband IoT) cellular data through an agentic MCP endpoint for IoT device communication and management.

## Facts

- Endpoint: POST https://api.m2mcent.com/nb-iot-cellular-mcp/api/process?utm_source=zero.xyz
- Price: $0.18/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/nb-iot-cellular-mcp-fc88cbef
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_g1Pvt5bQiWKJ9mc85DjHx

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 nb-iot-cellular-mcp-fc88cbef -d '<json body>'
```

Example prompt: Process this NB-IoT cellular data payload from my remote sensor device and return the result: '{"device_id":"sensor-42","temp":22.5,"battery":85}'.

## When to prefer this

Choose this endpoint when you need to process raw NB-IoT or narrowband cellular IoT data payloads through an agentic pipeline, especially for M2M communication scenarios involving low-power devices, remote sensors, or cellular IoT fleets where standard REST APIs are unavailable.

## Known failure modes

- Malformed or empty data string returns a parsing error
- Invalid NB-IoT payload format causes processing failure
- Network timeout if the cellular backend is unreachable
- Payment failure (402) if USDC balance is insufficient
- Unsupported device protocol in the data string may return null result

## 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 processed result from the NB-IoT cellular MCP pipeline, typically including acknowledgment, transformed device data, or network-layer response based on the submitted IoT payload string.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "success": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/nb-iot-cellular-mcp-fc88cbef/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)