# M2MCent Computer Vision Smart Contract Router MCP

> M2MCent Computer Vision Smart Contract Router MCP is a paid API for AI agents from api.m2mcent.com, paid per call via x402, $1.150648/call, status unknown (last checked 2026-10-10).

Routes a natural language query through a computer vision smart contract MCP node and returns a boolean analysis result

## Facts

- Endpoint: POST https://api.m2mcent.com/computer-vision-smart-contract-router-mcp-89/api/execute?utm_source=zero.xyz
- Price: $1.150648/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/m2mcent-computer-vision-smart-contract-router-mcp-f8cf9311
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_7bOq8h-pqtWQjDMvMknNc

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-computer-vision-smart-contract-router-mcp-f8cf9311 -d '<json body>'
```

Example prompt: Run my computer vision query through the M2MCent smart contract router MCP node and tell me if the analysis comes back true or false: 'does this image contain a human face?'

## When to prefer this

Choose this endpoint when you need a monetized, on-chain-settled computer vision analysis that returns a simple boolean result, routed through an MCP node with gasless USDC micropayment settlement on Base L2 via x402. Prefer it over generic vision APIs when you require smart contract routing, pay-per-call micropayment semantics, or integration into an agentic MCP workflow.

## Known failure modes

- Payment failure via x402 protocol returns 402 status — insufficient USDC balance or wallet not configured
- Malformed or empty query string returns validation error
- Node unavailability or subdomain routing failure returns 5xx error
- Query too vague for binary analysis may return unexpected false negative
- Rate limiting or capacity constraints on the MCP node may cause timeouts

## 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 'analysis' indicating whether the computer vision smart contract router determined the query condition to be true or false.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/m2mcent-computer-vision-smart-contract-router-mcp-f8cf9311/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)