# LiDAR Odometry MCP

> LiDAR Odometry MCP is a paid API for AI agents from api.m2mcent.com, paid per call via x402, $0.35/call, status unknown (last checked 2026-10-16).

Processes LiDAR scan data to compute odometry estimates (position and orientation) for autonomous navigation and mapping.

## Facts

- Endpoint: POST https://api.m2mcent.com/lidar-odometry-mcp/api/process?utm_source=zero.xyz
- Price: $0.35/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/lidar-odometry-mcp-df3c9c45
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_vK-K5Vi-BdtCqqOU1KSGk

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 lidar-odometry-mcp-df3c9c45 -d '<json body>'
```

Example prompt: Process this LiDAR scan data and give me the odometry estimate — I need the robot's current position and orientation based on these point cloud readings.

## When to prefer this

Choose this endpoint when you need to compute odometry from raw LiDAR scan data in an agentic pipeline — particularly for robotics, autonomous vehicle, or drone applications where position/orientation estimation from point cloud data is required without needing a full SLAM stack.

## Known failure modes

- Malformed or empty data string returns a 400 error
- Corrupt or unsupported LiDAR data format may produce inaccurate odometry or an error
- Payment failure (402) if USDC balance is insufficient
- Timeout if scan data is excessively large
- Server error (500) for internal processing failures

## 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 computed odometry information derived from the input LiDAR scan data, including estimated position and orientation (pose) of the sensor/robot platform.

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/lidar-odometry-mcp-df3c9c45/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)