# M2MCent ZK-SNARK Payload Verifier

> M2MCent ZK-SNARK Payload Verifier is a paid API for AI agents from api.m2mcent.com, paid per call via x402, $0.25/call, status unknown (last checked 2026-10-19).

Verifies zero-knowledge SNARK proofs submitted as payload data, returning a transaction hash and success status on Base L2

## Facts

- Endpoint: POST https://api.m2mcent.com/zk-snark-payload-verifier-mcp/api/process?utm_source=zero.xyz
- Price: $0.25/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/m2mcent-zk-snark-payload-verifier-89580746
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_TD1d-Qt_-YfEWOxMxM0Fz

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-zk-snark-payload-verifier-89580746 -d '<json body>'
```

Example prompt: Can you verify this ZK-SNARK proof payload for me and return whether it's valid along with the transaction hash: '<my_encoded_proof_string>'?

## When to prefer this

Choose this endpoint when you need to verify a ZK-SNARK proof payload on Base L2 via a monetized MCP node and require an on-chain transaction hash as proof of verification. Prefer it over generic validators when you need gasless USDC settlement via the x402 protocol and a standardized MCP interface.

## Known failure modes

- Invalid or malformed ZK-SNARK payload returns success: false
- Malformed data string causes processing error
- Payment failure (insufficient USDC) blocks execution
- Network or Base L2 congestion delays response
- Missing or empty 'data' field causes schema validation error

## 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 boolean 'success' field indicating whether the ZK-SNARK proof was accepted, and a 'txHash' string with the Base L2 transaction hash of the verification settlement.

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/m2mcent-zk-snark-payload-verifier-89580746/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)