# M2MCent Metaverse Biometric Aggregator MCP Node

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

Executes a prompt-based query against a monetized MCP node specializing in metaverse biometric aggregation, returning a summary response.

## Facts

- Endpoint: POST https://api.m2mcent.com/metaverse-biometric-aggregator-mcp-672/api/execute?utm_source=zero.xyz
- Price: $0.534308/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-22
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/m2mcent-metaverse-biometric-aggregator-mcp-node-7001537f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_j7_zwGm2N3R0kt3euZOWl

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-metaverse-biometric-aggregator-mcp-node-7001537f -d '<json body>'
```

Example prompt: Run the metaverse biometric aggregator MCP node with this prompt: 'aggregate heartrate and movement data from active metaverse session users in the last 24 hours.'

## When to prefer this

Choose this endpoint when you specifically need to interact with a monetized MCP node focused on metaverse biometric aggregation and are operating within the x402 USDC micropayment ecosystem on Base L2. Prefer this over generic REST APIs when your workflow requires gasless USDC settlements per call and integration with the M2MCent MCP node network.

## Known failure modes

- Payment failure via x402 protocol — USDC balance insufficient or Base L2 transaction not confirmed
- Prompt field missing or empty — validation error returned
- Node unavailable or subdomain unreachable — connection timeout
- Ambiguous or unsupported prompt content — undefined behavior given sparse schema
- Summary boolean returns false indicating no matching data or processing failure

## 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 with a 'summary' boolean field indicating whether the biometric aggregation prompt was processed successfully. The minimal schema provides limited structured output; the boolean likely signals success or presence of relevant data.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/m2mcent-metaverse-biometric-aggregator-mcp-node-7001537f/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)