# rapidlasso GmbH - LAStools LiDAR processing

**Canonical:** https://apis.io/providers/rapidlasso-gmbh-lastools-lidar-processing/  
**Website:** https://rapidlasso.de/  
**APIs profiled:** 0

rapidlasso GmbH provides LAStools, a suite of efficient LiDAR processing tools for point cloud data. The company offers high-performance software for filtering, classification, tiling, and visualization of massive LiDAR datasets, serving industries such as surveying, forestry, and autonomous vehicle mapping. Their tools are widely used for extracting accurate terrain models and feature extraction from raw LiDAR point clouds.

## Kin Score — 17.3 / 100 (emerging)

Scored 2026-10-31 under rubric 0.25.0.

| Facet | Score |
|---|---|
| Discoverability | 46.4 |
| Contract Quality | 0.0 |
| Contract Governance | 0.0 |
| Operational Transparency | 21.1 |
| Developer Ergonomics | 14.3 |
| Access Clarity | 42.1 |

Regulatory layer — **Horizontal (data, software, accessibility, platform)**: 5.9 (matched via fallback).

## Agent readiness — 0.0 (human-only)

| Dimension | Value |
|---|---|
| Spec Presence | no |
| Agentic Access | no |
| Reversibility Documented | no |
| MCP Server | no |
| Auth Clarity | no |
| Idempotency | no |
| Error Semantics | no |
| OpenAPI Examples | no |
| Rate Limit Signal | no |
| Event Surface Described | no |
| Agent Skills | no |
| Well Known Catalog | no |
| Consent Identity | no |
| Agent Card | no |
| Dry Run Mode | no |
| Delegated Identity | no |
| Protected Resource Metadata | no |
| Dynamic Client Registration | no |
| Agentic Commerce | no |
| Pagination Ratio | na |
| Operation Distinctiveness | na |

## Security (1)

- **Rapidlasso Gmbh Lastools Lidar Processing Domain Security** — TLSv1.3 · DMARC

## Plans (1)

- **Rapidlasso Gmbh Lastools Lidar Processing Plans Pricing**

## Tags

Company, LiDAR, Geospatial, PointCloud, Surveying

---

Profiled by [API Evangelist](https://apievangelist.com) and published on [APIs.io](https://apis.io/providers/rapidlasso-gmbh-lastools-lidar-processing/). Scores are computed from the provider's own public artifacts under a published rubric.
