Enter NOCLIP Earth
NOCLIPOpen Earth

PROGRAMMABLE EARTH / ONLINE

Earth is the interface.

NOCLIP is a shared 3D Earth for building overlays, connecting dynamic assets, and giving people or agents controlled access to the same scene.

Launch Earth Read the docs
EARTH / ACTIVE SCENE CONNECTED
VIEW
ORBIT → SURFACE
LAYERS
12 ACTIVE
STATE
OBSERVABLE
3D EARTH CLIENTVERSIONED OVERLAYSDYNAMIC ASSET APISCOPED AGENT CONTROL

PLATFORM

One scene. Three control surfaces.

The Earth client, REST API, and agent interface operate on the same overlay and scene state. Build once, then inspect and control it from the surface that fits the job.

SERVICEWHAT IT DOESAPI SURFACE

01Overlay workspace

Create private or public overlays, add typed layers, and page large item sets into the live scene.

/overlays

02Dynamic asset API

Attach versioned assets to data sources, keep metadata with the source, and update what Earth renders without rebuilding the client.

/data-sources/:id/assets

03Agent control

Open a scoped observation lease, issue allowlisted camera commands, and verify the resulting rendered state.

/agent/interface

01 / OVERLAYS

Compose the scene as data.

An overlay owns its visibility, layers, source bindings, and access. Use vector, raster, external-feed, or 3D-asset layers without flattening every source into one document.

  • Private, shared, and public visibility
  • Manifest and paged item reads for large layers
  • Revision-aware source and asset relationships
Overlay documentation
OVERLAY / OPERATIONS-01REV 12
VISIBILITYACCOUNTUPDATED14:32:08 UTC
01Incident perimeterVECTORLIVE
02Camera networkEXTERNAL FEED42 ITEMS
03Field model3D ASSETSREV 08
3 LAYERSSCHEMA VALID

02 / DYNAMIC ASSET API

Update assets without redeploying Earth.

Register an asset against a versioned data source and let the client resolve the active version at runtime. Keep format, attribution, bounds, and delivery metadata with the asset record.

  • Versioned source records and active asset selection
  • Raster, vector, 3D, and OGC feature delivery
  • Catalog metadata and provenance available to clients
API reference
POST /data-sources/:sourceId/assetsJSON
{
  "versionId": "ver_08",
  "assetType": "3d_assets",
  "remoteUrl": "https://…/scene/tileset.json",
  "metadata": {
    "bounds": [-123.1, 45.2, -122.1, 45.8],
    "attribution": "Operations source"
  }
}
201 CREATEDASSET / ACTIVE

03 / AGENT CONTROL

Control the view. Verify the result.

Agent access is owner-bound and scope-checked. An agent opens an observation lease, reads current scene evidence, sends an allowlisted intent, and checks rendered arrival before treating the action as complete.

  1. 01ObserveAcquire a time-bounded scene lease.
  2. 02ActSend a supported camera or scene command.
  3. 03VerifyRead fresh rendered state and completion evidence.
Agent access guide
AGENT / OBSERVATION LEASE ACTIVE

› POST /agent/interface/observations

scope: scene:observe · ttl: 10m

› POST /agent/interface/observations/obs_27/commands

{ "command": { "intent": "fly_to", "slots": { "lat": 45.52, "lon": -122.67 } } }

› GET /agent/interface/observations/obs_27

arrived: true · rendered pose verified

OWNER-BOUNDALLOWLISTEDOBSERVABLE

DEVELOPERS

Use the same world from code.

DATA CATALOGSources, products, caveats, and endpoint templatesAPI REFERENCEREST endpoints, schemas, and authenticationAGENT ACCESSObservation leases, scopes, commands, and verification
EARTH / ONLINEOpen the live scene.