# NOCLIP Geospatial Platform

NOCLIP provides normalized, provenance-bearing geospatial data through https://api.noclip.org and an interactive Earth client at https://noclip.org.

## Agent entry points

- Owner onboarding and one-time API-key reveal: https://noclip.org/?panel=agents
- Human agent-access guide: https://noclip.org/docs#agent-access
- Machine-readable agent contract template: https://noclip.org/docs/agent-contract.json
- Live data/product/source catalog: https://api.noclip.org/v1/data/catalog
- Governed OpenAPI YAML: https://api.noclip.org/docs/openapi
- Interactive API reference: https://api.noclip.org/docs

## Authentication

The account owner provisions a dedicated least-privilege key in Account > Agents. Send it only as `Authorization: Bearer nk_...`. Never place it in a URL, logs, public prompts, source control, or user-visible output. The secret is shown once; rotation invalidates the previous key.

The automatically generated key has `data:read`, `scene:observe`, and `scene:control`. Discover geospatial products from `/v1/data/catalog`. For a live account-owned Earth view, list `/agent/interface/sessions` and use its bounded device class/name/display/tag metadata to select the device the owner actually requested; never substitute most-recent activity for an explicit desktop, phone, or VR target. Create a ten-minute `/agent/interface/observations` lease, poll its renderer-backed viewshed/feed controls, send only a documented bounded command when needed, and delete the observation when done. `state.surfaceLatLon` can be an in-progress logical destination; `state.renderedSurfaceLatLon` and `state.cameraTransition` describe the physical camera. A `fly_to` succeeds only after the command is complete with `toolResult.arrived=true` at the rendered destination. For iterative surface navigation, first require `state.agentInterface.capabilities.controlIntents` to include `step_camera`; absence means that Earth client must be reloaded, not probed. Then send one `step_camera` command at a time (W/S = ±forward metres, D/A = ±right metres, plus bounded vertical/yaw/pitch), wait for completion and a newer observation/frame, inspect, then decide the next step. Scene images are opt-in, 320x180, and capped to one frame per five seconds.

## Query and evidence rules

- Prefer bounded bbox, radius, time-window, and result-limit queries.
- Preserve source/provider attribution, event time, retrieval time, confidence, precision, geometry, and caveats.
- Never invent coordinates for non-geospatial records or describe modeled/statistical products as direct observations.
- On HTTP 429, stop and honor `Retry-After` and rate reset headers. Do not parallel-retry.
- NOCLIP holdings can raise the account ceiling, but API-key, client/edge, operation, provider, concurrency, and global safety limits still apply.