API Reference

The API surface is hosted at api.truetopo.com. Below are the main endpoint patterns and responses.

Gazetteer API

Search the geographic names database (e.g. GNIS).

Endpoint: GET /api/gazetteer/search

Query: q — search term (e.g. place name).

Example:

GET /api/gazetteer/search?q=Denali

Example response:

{
  "name": "Denali",
  "type": "Mountain",
  "lat": 63.0695,
  "lon": -151.0074
}

(Actual response shape may include feature_id, state, county, etc., depending on implementation.)

---

Map tile API

Vector tiles are served by dataset and zoom/x/y.

Pattern: /tiles/{dataset}/{z}/{x}/{y}.pbf

Datasets (examples): gazetteer, hydrology, land, trails, mining, wildlife.

Example:

GET /tiles/trails/10/162/384.pbf

Tiles are typically served from R2 (e.g. tiles.truetopo.com or a Worker in front of R2).

---

Intelligence API (access routes)

Returns legal access routes: ANCSA 17(b) easements, RS 2477 trails, and other public rights-of-way.

Endpoint: GET /api/access/routes

Example response (conceptual):

{
  "routes": [
    {
      "id": "...",
      "type": "17b",
      "geometry": { ... },
      "attributes": { ... }
    }
  ]
}

This is where the platform becomes powerful for land access planning: one call for legal routes in an area.

---

Base URL

• Production: https://api.truetopo.com
• Docs and status: See api.truetopo.com for current availability and versioning.