elevation derived

api.geoprimitives.devMarket data derived

GET https://api.geoprimitives.dev/v1/elevation

passabsent from every registry#3 by calls of 3 on this host

0.005 USDC

per call, as the listing declares it on eip155:8453

Compare with another Every figure as JSON Cite this page

the price, as of 2026-09-20 16:04 UTC · method

Validation state: pass; as of 2026-09-19 05:00 UTC · method · sweep daily-2026-09-19
Uptime, 7 / 30 / 90 days: — / — / 100%; as of 2026-09-19 05:00 UTC · method · 0 of 0 in 7d, 0 of 0 in 30d, 9 of 9 in 90d
Calls, trailing 30 days: 3; as of 2026-09-20 16:04 UTC · method
Unique payers, trailing 30 days: 1; as of 2026-09-20 16:04 UTC · method
Last called: 2026-08-21 18:10 UTC; as of 2026-09-20 16:04 UTC · method
First observed by TOLLderived: 2026-09-10; as of 2026-09-10 19:08 UTC · method · observation began 10 September 2026; listings that predate it show that date
Pricederived: 0.005 USDC; as of 2026-09-20 16:04 UTC · method · on eip155:8453
Networks: 1; as of 2026-09-20 16:04 UTC · method

Counters

48 observations, 1 of them a change, fewer than the 3 a trace needs

How big is this endpoint among the ones like it?

Calls counted in the trailing thirty days across the 10,493 endpoints in Market data that carry counters, binned on a logarithmic scale because the range runs over five orders of magnitude. The marked bin is this endpoint, at 3: 3,745 in the category are counted higher and 6,747 lower.

No trace is drawn of this endpoint’s own volume. Its counters have changed 1 time across 48 observations, and 3 changes are the fewest this site will draw a trace through, because two points and a guess are not a series. Every observation is in the JSON.

In words

TOLL files elevation under market data: a GET endpoint on api.geoprimitives.dev, listed in neither registry at the last pull.

On Base, elevation asks 0.005 USDC per call.

The request to elevation is the query parameters lat and lon.

A response from elevation, as declared, includes notes, query, units, sample, source, coverage and 2 others.

elevation answered the sweep of 2026-09-19 with a valid 402, as at every sweep since 2026-09-11.

elevation shares api.geoprimitives.dev with 2 other listed endpoints and is tied 3rd by calls with 1 other.

elevation drew 3 calls from one payer in the trailing 30 days.

The last call to elevation came 72 days before the snapshot, 2026-08-21.

Closest in price to elevation within market data: pump check at agent.pocket.network and deepstate book at api.onesource.io.

elevation is priced above 31% of comparable listings in market data.

Across market data, 10,493 endpoints carry counters and elevation out-counts 52% of them.

The wallet paid by elevation is the payee of 21 endpoints on one host.

The seller's tags on elevation are elevation, dem, 3dep and alaska.

elevation was missing from the Coinbase registry at the pull of 2026-09-20, confirmed at the pull of 2026-09-21; that is registry presence, not liveness.

The price of elevation is declared by 1,062 other listings in market data too.

Where the sentences above compare this endpoint with others, the comparison is against the index as it stands now, live; the figures above are final.

Payment options as declared

the payment options, as of 2026-09-20 16:04 UTC · method

Every payment option declared on this listing
registry	network	asset	amount	scheme	pay to
Coinbase	eip155:8453	USDC	0.005 USDC	exact	0x76A51b…968FCe

Preflight checks at the last sweep

the checks, as of 2026-09-19 05:00 UTC · methodendpoint answered HTTP 402

No named check failed.

Validation history, 90 days

Every sweep that observed this endpoint, newest first.

Validation observations over the last 90 days
observed, UTC	state	sweep
2026-09-19 05:00 UTC	pass	daily-2026-09-19
2026-09-18 12:12 UTC	pass	daily-2026-09-18
2026-09-17 04:56 UTC	pass	daily-2026-09-17
2026-09-16 04:57 UTC	pass	daily-2026-09-16
2026-09-15 04:52 UTC	pass	daily-2026-09-15
2026-09-14 04:47 UTC	pass	daily-2026-09-14
2026-09-13 04:44 UTC	pass	daily-2026-09-13
2026-09-12 07:02 UTC	pass	daily-2026-09-12
2026-09-11 10:39 UTC	pass	daily-2026-09-11

Registry presence

Presence in a registry, not liveness of the service (method). Newest first.

2026-09-21 04:53 UTCabsence from Coinbase confirmed, rule v1
2026-09-20 20:47 UTCabsent from Coinbase at this pull
2026-09-10 19:08 UTClisted in Coinbase

Declared input and output, as listed

From the registry record, not validated by TOLL.the declared schema, as of 2026-08-21 18:10 UTC · method

The input and output block

{
  "input": {
    "type": "http",
    "method": "GET",
    "queryParams": {
      "lat": 61.2181,
      "lon": -149.8997
    }
  },
  "output": {
    "type": "json",
    "example": {
      "notes": [],
      "query": {
        "lat": 61.2181,
        "lon": -149.8997
      },
      "units": "metres",
      "sample": {
        "block": "n62w150",
        "pixelMetres": {
          "eastWest": 29.9,
          "northSouth": 61.9
        },
        "neighboursUsed": 4,
        "neighboursVoid": 0
      },
      "source": {
        "url": "https://prd-tnm.s3.amazonaws.com/StagedProducts/Elevation/2/TIFF/current/",
        "units": "metres",
        "rights": "Public domain (US government work, 17 U.S.C. 105)",
        "dataset": "3D Elevation Program (3DEP) seamless DEM",
        "product": "2 arc-second",
        "publisher": "US Geological Survey",
        "usgsPublished": "20170501",
        "verticalDatum": "NAVD88",
        "horizontalDatum": "NAD83",
        "pixelArcSeconds": 2,
        "usgsPublishedRange": [
          "2013",
          "20260611"
        ]
      },
      "coverage": {
        "blocks": 439,
        "reason": "Coverage is the state of Alaska, whole, from the USGS 3DEP seamless 2 arc-second DEM: every 1-degree block that holds Alaskan ground as the Census TIGER county boundaries draw it, 439 blocks. The conterminous United States and Hawaii are not answered yet. USGS publishes them at 1 arc-second through the same pipeline; they are a 47 GB upload rather than a design change and will arrive as a coverage extension with no change to this interface. Canada is not answered, and the pixels USGS ships over Yukon and British Columbia were not stored: they come from Natural Resources Canada under a licence with an attribution clause, and this catalog carries public-domain data only. A coordinate outside the coverage is quoted like any other and then refused with outside_coverage; a refusal does not settle, so nothing is charged for it.",
        "region": "Alaska",
        "answered": [
          "Alaska"
        ],
        "notAnswered": [
          "conterminous United States",
          "Hawaii",
          "territories",
          "Canada",
          "the rest of the world"
        ]
      },
      "elevation": 31.763,
      "interpolation": "bilinear",
      "verticalDatum": "NAVD88"
    }
  }
}

What the listing says

Give it a latitude and longitude and it answers with the ground elevation there in metres above NAVD88, read from the USGS 3D Elevation Program seamless DEM. Parameters go in the query string: this is a GET, there is no body. COVERAGE, stated up front because it is the first thing to check: the state of Alaska, whole, and nothing else yet. The coverage gate reads the coordinate, so it runs in the handler and after payment, not in front of the 402: a coordinate outside Alaska is quoted like any other and then refused with outside_coverage. A refusal does not settle, so nothing is charged, but it costs a signature and a second round trip to find out. Check the coverage against this description or the free catalog first. The conterminous United States and Hawaii are the next extension and arrive through the same pipeline with no change to this interface; every response repeats the coverage under `coverage` so an agent never infers it from an error. Canada is not served even where USGS publishes pixels over it: those come from Natural Resources Canada under a licence with an attribution clause, and this catalog carries public-domain data only, so they were not stored. SOURCE AND VINTAGE: USGS 3DEP seamless 2 arc-second product, the resolution USGS publishes for Alaska, a work of the United States government in the public domain (17 U.S.C. 105). A 2 arc-second pixel is about 62 m north to south and 20 to 30 m east to west at Alaskan latitudes; the response states the pixel size at your latitude. USGS republishes blocks as new lidar and IFSAR arrive, and the response carries the publication date of the block that answered you. Heights are orthometric, NAVD88, metres; horizontal positions are NAD83, which this endpoint reads as WGS 84 since the two differ by under two metres, a fraction of a pixel. INTERPOLATION: bilinear over the four pixel centres around the point by default, which is what GDAL and PROJ do for a continuous surface. Pass interpolation=nearest for the raster's own value at the pixel the point falls in, which is bit-identical to gdallocationinfo on the USGS file and the right choice when you want the source unblended. Checked against GDAL rather than against itself: of 200 coordinates drawn over the built blocks, the 150 inside the coverage agreed with `gdallocationinfo -r bilinear` on the USGS GeoTIFFs to 6.2e-4 m at worst, and interpolation=nearest agreed with plain `gdallocationinfo` to the millimetre this endpoint rounds to. The response always names the method used. VOIDS AND WATER: gaps in the USGS footprint and the Canadian side of the border are void, and so is open water beyond the three-mile county limit. A void pixel inside a bilinear window is dropped and the remaining weights renormalised, as gdalwarp treats nodata, and the response says how many of the four were used. A window that is entirely void is refused with no_data and not charged, never answered with zero. Inshore water is a different case and you should know it: USGS writes 0 over the sea in some blocks and nodata in others, so a coordinate in a harbour or a bay inside the county limit may answer 0 m, which is the source's value and not a measurement of anything. ACCURACY of the data itself is USGS's, not this endpoint's: the Alaska seamless layer is built from IFSAR at 5 m resampled to 2 arc-seconds, and USGS states its vertical accuracy per source project rather than for the seamless layer as a whole. Expect metre-level agreement with a survey on open terrain and worse under forest and on steep slopes. This endpoint adds nothing to that error beyond interpolation. Longitude and latitude are checked against EPSG:4326 bounds first. Reproject with POST /v1/transform if you are not already in WGS 84 or NAD83. For a line rather than a point use POST /v1/elevation/profile, which samples along a polyline in one call.

the record, 2026-08-21 18:10 UTC · method

As declared

GET
eip155:8453
USDC
exact

Every tag is a field on the listing, not a keyword TOLL assigned.

Who is paid

0x76A51b…968FCe

Takes payment for 21 endpoints on 1 host.

Among Market data

counted above52%

of 10,493 that carry counters

cheaper than31%

of 10,611 with a comparable price

10,722 endpoints are in this category. 1,062 declare exactly this price.

the comparison, 2026-11-01 21:59 UTC · method · live

Nearest on price

paymentwww.api-xpay.com0.005 USDCpass
pump checkagent.pocket.network0.005 USDCpass
deepstate bookapi.onesource.io0.005 USDCpass
stonk yield invokeapi.solenrich.com0.005 USDCpass
stockapi.tickersfeed.net0.003 USDCfail

Same category, nearest declared price, one per payee wallet (method). the list, 2026-11-01 21:59 UTC · method · live

Elsewhere in the record

Cite this page

This endpoint is delisted: the page is frozen at its last observation and its live URL is the stable one. Data reuse is under CC BY 4.0 (terms).

Plain text

TOLL, "elevation on api.geoprimitives.dev". https://tollindex.com/e/api-geoprimitives-dev-v1-elevation-5ce07f. Accessed [access date].

BibTeX

@misc{toll-e-api-geoprimitives-dev-v1-elevation-5ce07f-2026-11-01,
  author = {TOLL},
  title = {elevation on api.geoprimitives.dev},
  howpublished = {\url{https://tollindex.com/e/api-geoprimitives-dev-v1-elevation-5ce07f}},
  year = {2026},
  month = {11},
  note = {Frozen at its last observation, 2026-11-01 21:59 UTC. Accessed [access date].}
}

Reports and replies about this endpoint

None yet. Anything submitted through the form below is published here with its outcome.

Report an error about elevation, or reply as the named seller