# M2MCent Robotics Metadata Aggregator MCP Node

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

Executes a robotics metadata aggregation query against a monetized MCP node in the M2MCent network, returning a result URL via x402 micropayment settlement on Base L2.

## Facts

- Endpoint: POST https://api.m2mcent.com/robotics-metadata-aggregator-mcp-459/api/execute?utm_source=zero.xyz
- Price: $0.107647/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/m2mcent-robotics-metadata-aggregator-mcp-node-68140b3a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_l2hWpMGQhhbj_tXQDdmds

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-robotics-metadata-aggregator-mcp-node-68140b3a -d '<json body>'
```

Example prompt: Can you query the M2MCent robotics metadata aggregator MCP node with my search string 'autonomous mobile robot sensor specs' and get back the result URL?

## When to prefer this

Choose this endpoint when you need to aggregate or retrieve robotics-domain metadata through a monetized MCP node in the M2MCent network and are already set up for x402 micropayment settlements on Base L2. Prefer it over generic web search when you need structured, MCP-native robotics metadata accessible via a gasless USDC transaction.

## Known failure modes

- Payment failure: insufficient USDC balance or x402 settlement error on Base L2
- Invalid input: missing or malformed 'data' string field returns 400 error
- Node unavailable: specific MCP subdomain offline or unreachable
- Empty result: query string returns no matching robotics metadata
- Schema mismatch: response 'url' field typed as boolean but may return string, causing parsing issues

## 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 'url' field (boolean in the declared schema, though likely a URL string in practice) pointing to the aggregated robotics metadata result. The agent receives a reference to where the retrieved metadata can be accessed.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/m2mcent-robotics-metadata-aggregator-mcp-node-68140b3a/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)