# LiDAR LAS/LAZ File Parser

> LiDAR LAS/LAZ File Parser is a paid API for AI agents from api.m2mcent.com, paid per call via x402, $0.35/call, status unknown (last checked 2026-09-15).

Parses and processes LiDAR point cloud data from LAS and LAZ file formats, extracting structured information from raw scan data.

## Facts

- Endpoint: POST https://api.m2mcent.com/lidar-las-laz-parser-mcp/api/process
- Price: $0.35/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/lidar-las-laz-file-parser-59e037f2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_NeUSSO8_fCNP_w78A0UV8

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-las-laz-file-parser-59e037f2 -d '<json body>'
```

Example prompt: Can you parse this LAS/LAZ LiDAR file data and extract the point cloud records, coordinates, intensity values, and header metadata from it?

## When to prefer this

Choose this endpoint when you need to programmatically parse raw LAS or LAZ LiDAR point cloud files and extract structured point data, coordinates, or header metadata — especially in automated GIS, surveying, or remote sensing pipelines where LiDAR data ingestion is required.

## Known failure modes

- Invalid or corrupt LAS/LAZ binary data returns a parse error
- Data field contains non-LiDAR or unsupported format content, resulting in failure
- Excessively large point cloud data may time out or be rejected
- Missing or malformed data field returns a 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

Returns structured data extracted from the LAS/LAZ file, including point cloud records with XYZ coordinates, intensity values, classification codes, return counts, and file header metadata such as point count and bounding box.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "payload": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/lidar-las-laz-file-parser-59e037f2/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)