Destination Command Center · Developers

One coordinate in. Dense public context out.

Latitude and longitude are the canonical DCC location key. If you know a coordinate, you do not need to know which public weather, alert, earth, water, air-quality, event, or local source covers it. DCC selects the geographically applicable sources and returns one predictable location object.

Canonical contract

dcc-location-v2

Human: /location/{lat}/{lng}

JSON: /api/location/{lat}/{lng}

Precision: 5 decimal places

Human page

https://destinationcommandcenter.com/location/39.66540/-105.20570Open example →

Machine endpoint

https://destinationcommandcenter.com/api/location/39.66540/-105.20570Open JSON →

Ordered response modules

Read the modules object first. DCC returns only what mapped sources can support for that coordinate.

identity

Coordinate, timezone, elevation and canonical identity

now

Current weather and air-quality conditions

conditions

12-hour weather/air outlook and three-day context

hazards

Official alerts, recent earthquakes and NASA natural events

water

Nearby NOAA river/flood gauges when applicable

official

Official NWS forecast/zone context when applicable

events

Configured nearby event feeds when available

machineFeeds

Additional geographically mapped public machine feeds

Current core public sources

Open-Meteo weather

Open-Meteo / Copernicus CAMS air quality

U.S. National Weather Service forecasts + alerts

U.S. Geological Survey earthquakes

NASA EONET natural events

NOAA National Water Prediction Service gauges

Each response includes per-source availability and checked timestamps. DCC uses source-specific revalidation plus a short shared response cache so repeated agent reads do not hammer public upstream services.

OCTO Core API & Booking Distribution

5% Fixed DCC Share

DCC provides an authorized distribution layer built on the Open Connectivity for Tour Operators (OCTO) standard. AI agents and applications query live operator availability and execute two-phase booking holds with explicit expirationMinutes. Operators retain merchant-of-record status and direct fulfillment authority.

GET /api/octo/participants

Registry of authorized operators, booking systems, and tech partners.

POST /api/octo/availability

Real-time availability check against upstream operator reservation systems.

POST /api/octo/hold

Two-phase reservation hold reserving seats for a 15-minute checkout window.

POST /api/octo/confirm

Confirm held reservation, generate digital voucher, and record 5% settlement.

Machine discovery

Agent contract/agent.jsonWell-known agent contract/.well-known/agent.jsonLLM instructions/llms.txtOpenAPI schema/openapi.jsonOCTO Participant Registry/api/octo/participantsAuthorized Operators/operators

How to interpret a response

DCC aggregates time-sensitive public-source observations. Use provider names, timestamps, freshness fields, and source links when available. A missing module means DCC does not currently have a mapped usable source for that coordinate; it does not prove that the real-world condition or service is absent. Machine coordinate reads do not require reverse geocoding; a human-readable place name is optional.