elevation profile derived

api.geoprimitives.devInference derived

POST https://api.geoprimitives.dev/v1/elevation/profile

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

0.01 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-20 18:59 UTC · method · sweep daily-2026-09-20
Uptime, 7 / 30 / 90 days: — / — / 100%; as of 2026-09-20 18:59 UTC · method · 0 of 0 in 7d, 0 of 0 in 30d, 10 of 10 in 90d
Calls, trailing 30 days: 1; 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 17:25 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.01 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 3,584 endpoints in Inference that carry counters, binned on a logarithmic scale because the range runs over five orders of magnitude. The marked bin is this endpoint, at 1: 2,378 in the category are counted higher and 1,205 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 profile under inference: a POST endpoint on api.geoprimitives.dev, listed in neither registry at the last pull.

On Base, elevation profile asks 0.01 USDC per call.

Its declared inputs are a json body with the fields samples and coordinates.

elevation profile returns json; the example shows notes, stats, units, source, samples, coverage and 2 others.

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

elevation profile shares api.geoprimitives.dev with 2 other listed endpoints and is 4th by calls.

elevation profile drew a single call from a single payer in the trailing 30 days.

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

Closest in price to elevation profile within inference: geo at ip402.xyz and council at council.cyberwarex.com.

elevation profile is priced above 42% of comparable listings in inference.

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

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

elevation profile 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 profile is declared by 779 other listings in inference 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.01 USDC	exact	0x76A51b…968FCe

Preflight checks at the last sweep

the checks, as of 2026-09-20 18:59 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-20 18:59 UTC	pass	daily-2026-09-20
2026-09-19 04:21 UTC	pass	daily-2026-09-19
2026-09-18 10:08 UTC	pass	daily-2026-09-18
2026-09-17 04:19 UTC	pass	daily-2026-09-17
2026-09-16 04:20 UTC	pass	daily-2026-09-16
2026-09-15 04:17 UTC	pass	daily-2026-09-15
2026-09-14 04:15 UTC	pass	daily-2026-09-14
2026-09-13 04:14 UTC	pass	daily-2026-09-13
2026-09-12 06:30 UTC	pass	daily-2026-09-12
2026-09-11 09:59 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 17:25 UTC · method

The input and output block

{
  "input": {
    "body": {
      "samples": 5,
      "coordinates": [
        [
          -149.8997,
          61.2181
        ],
        [
          -149.8397,
          61.2081
        ]
      ]
    },
    "type": "http",
    "method": "POST",
    "bodyType": "json"
  },
  "output": {
    "type": "json",
    "example": {
      "notes": [],
      "stats": {
        "maxMetres": 37.525,
        "minMetres": 30.598,
        "gainMetres": 9.733,
        "lossMetres": 5.204,
        "voidSamples": 0
      },
      "units": "metres",
      "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": null,
        "verticalDatum": "NAVD88",
        "horizontalDatum": "NAD83",
        "pixelArcSeconds": 2,
        "usgsPublishedRange": [
          "2013",
          "20260611"
        ]
      },
      "samples": [
        {
          "lat": 61.2181,
          "lon": -149.8997,
          "elevation": 31.763,
          "distanceMetres": 0
        },
        {
          "lat": 61.2156025,
          "lon": -149.8846964,
          "elevation": 34.569,
          "distanceMetres": 852.95
        },
        {
          "lat": 61.2131033,
          "lon": -149.8696952,
          "elevation": 30.598,
          "distanceMetres": 1705.89
        },
        {
          "lat": 61.2106025,
          "lon": -149.8546964,
          "elevation": 37.525,
          "distanceMetres": 2558.84
        },
        {
          "lat": 61.2081,
          "lon": -149.8397,
          "elevation": 36.292,
          "distanceMetres": 3411.78
        }
      ],
      "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"
        ]
      },
      "geometry": "Samples are spaced equally by geodesic distance (GRS 80) along the polyline; each lies on the great circle of its segment.",
      "tilesRead": 3,
      "sampleCount": 5,
      "lengthMetres": 3411.78,
      "interpolation": "bilinear",
      "spacingMetres": 852.95,
      "verticalDatum": "NAVD88"
    }
  }
}

What the listing says

Send a polyline as an array of [longitude, latitude] positions and it answers with elevations sampled at equal geodesic spacing along it, from the USGS 3D Elevation Program seamless DEM, plus the cumulative gain and loss and the minimum and maximum. One call for a whole route rather than one call per point: 2000 samples cost what two cost. COVERAGE is the state of Alaska, whole, and nothing else yet; see GET /v1/elevation for the full statement, which this route shares and repeats under `coverage` on every response. Every sample is checked against the coverage before a tile is read, and a profile with any sample outside Alaska is refused with outside_coverage naming the sample. That check reads coordinates, so it runs after payment like the rest of the handler; the refusal does not settle and nothing is charged, but it costs a signature and a second round trip. Canada is not served even where USGS publishes pixels over it, for the licensing reason stated there. SAMPLING: samples are placed at equal geodesic distance (GRS 80) along the polyline, each on the great circle of its segment, the first at the first position and the last at the last. Omit `samples` to sample every 60 m, the native pixel height, up to 2000; pass it to choose the count. Each sample is bilinear over the four pixel centres around it by default, or `nearest` for the raster's own values; the response names the method. The source is the 2 arc-second product USGS publishes for Alaska, about 62 m north to south, so asking for spacing much under 60 m buys interpolation rather than information. VOIDS inside the line: gaps in the USGS footprint, the Canadian side of the border and water beyond the county limit are void. A sample whose window is entirely void is null in the list and counted in `stats.voidSamples`; gain and loss are summed over consecutive non-null samples so a crossing of void water is not a descent to zero and back. Inshore water is 0 in some USGS blocks rather than void, so a line across a bay may read 0 m there, which is the source's value; see GET /v1/elevation. A profile that is void throughout is refused with no_data and not charged. SOURCE, VINTAGE, DATUMS AND ACCURACY are those of GET /v1/elevation: USGS 3DEP, public domain, NAVD88 metres, NAD83 horizontal read as WGS 84, IFSAR-derived in Alaska with metre-level vertical accuracy on open ground. Gain and loss over a 2 arc-second surface are an estimate of the terrain's, not of a track's: fine structure narrower than a pixel is not in the data. Limits: 500 positions in the polyline, 2000 samples, 1000 km of length, 512 elevation tiles read per call (about 2000 km of profile at the coarsest sampling; a 100 km profile at native spacing reads about 40), and a 1 MiB body. All are checked before a tile is read.

the record, 2026-08-21 17:25 UTC · method

As declared

POST
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 Inference

counted above0%

of 3,584 that carry counters

cheaper than42%

of 3,587 with a comparable price

3,681 endpoints are in this category. 779 declare exactly this price.

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

Nearest on price

chat completionsapi.gondola-ai.com0.01 USDCpass
geoip402.xyz0.01 USDCpass
councilcouncil.cyberwarex.com0.01 USDCpass
chat completionsagent402.tools0.01 USDCpass
decodeapi.vindexapi.dev0.01 USDCpass

Same category, nearest declared price, one per payee wallet (method). the list, 2026-11-01 05: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 profile on api.geoprimitives.dev". https://tollindex.com/e/api-geoprimitives-dev-v1-elevation-profile-2bc2fe. Accessed [access date].

BibTeX

@misc{toll-e-api-geoprimitives-dev-v1-elevation-profile-2bc2fe-2026-11-01,
  author = {TOLL},
  title = {elevation profile on api.geoprimitives.dev},
  howpublished = {\url{https://tollindex.com/e/api-geoprimitives-dev-v1-elevation-profile-2bc2fe}},
  year = {2026},
  month = {11},
  note = {Frozen at its last observation, 2026-11-01 05: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 profile, or reply as the named seller