# M2MCent Zod Schema Enforcer MCP

> M2MCent Zod Schema Enforcer MCP is a paid API for AI agents from api.m2mcent.com, paid per call via x402, $0.3/call, status unknown (last checked 2026-10-14).

Validates and enforces Zod schema constraints against input data via a monetized MCP node, returning a transaction hash on success.

## Facts

- Endpoint: POST https://api.m2mcent.com/zod-schema-enforcer-mcp/api/process?utm_source=zero.xyz
- Price: $0.3/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/m2mcent-zod-schema-enforcer-mcp-401bdb46
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_kVFrZ9xpWGcL4sLFb2Z0z

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-zod-schema-enforcer-mcp-401bdb46 -d '<json body>'
```

Example prompt: Can you run this JSON string through the Zod schema enforcer to check if it's valid: '{"name":"Alice","age":30}'?

## When to prefer this

Choose this endpoint when you need a remote, pay-per-use Zod schema validation step within an agentic workflow and want to offload schema enforcement to a monetized MCP node rather than running validation locally. Particularly useful when token context savings matter or when integrating with the M2MCent x402 payment rail.

## Known failure modes

- Invalid or malformed input data string causes validation failure with success: false
- Network timeout on the MCP node endpoint
- Payment settlement failure via x402 protocol resulting in 402 response
- Schema enforcement rejects data that doesn't conform, returning error details

## 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 transaction hash (txHash) and a boolean success flag indicating whether the input data passed Zod schema enforcement.

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/m2mcent-zod-schema-enforcer-mcp-401bdb46/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)