h3 polyfill derived

api.geoprimitives.devCompute derived

POST https://api.geoprimitives.dev/v1/h3/polyfill

passlisted in Coinbase#7 by calls of 21 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-16 21:17 UTC · method · pinnable

Validation state: pass; as of 2026-09-16 05:48 UTC · method · pinnable · sweep daily-2026-09-16
Uptime, 7 / 30 / 90 days: 100% / 100% / 100%; as of 2026-09-16 05:48 UTC · method · pinnable · 6 of 6 in 7d, 6 of 6 in 30d, 6 of 6 in 90d
Calls, trailing 30 days: 1; as of 2026-09-16 21:17 UTC · method · pinnable
Unique payers, trailing 30 days: 1; as of 2026-09-16 21:17 UTC · method · pinnable
Last called: 2026-08-21 17:26 UTC; as of 2026-09-16 21:17 UTC · method · pinnable
First observed by TOLLderived: 2026-09-10; as of 2026-09-10 19:08 UTC · method · pinnable · observation began 10 September 2026; listings that predate it show that date
Pricederived: 0.01 USDC; as of 2026-09-16 21:17 UTC · method · pinnable · on eip155:8453
Networks: 1; as of 2026-09-16 21:17 UTC · method · pinnable

Counters

33 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 481 endpoints in Compute 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: 265 in the category are counted higher and 215 lower.

No trace is drawn of this endpoint’s own volume. Its counters have changed 1 time across 33 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

Among the 21 endpoints on api.geoprimitives.dev, h3 polyfill is tied 7th by calls with 14 others.

The request to h3 polyfill is a json body with the fields geojson and resolution.

h3 polyfill returns json; the example shows mode, notes, results, cellCount, containment, resolutions and 1 other.

h3 polyfill drew a single call from a single payer in the trailing 30 days.

The last call to h3 polyfill came 26 days before the snapshot, 2026-08-21.

The declared price is 0.01 USDC on Base.

TOLL files h3 polyfill under compute: a POST endpoint on api.geoprimitives.dev, listed in the Coinbase registry.

h3 polyfill answered the sweep of 2026-09-16 with a valid 402, as at every sweep since 2026-09-11.

Closest in price to h3 polyfill within compute: opportunities trending at api.demandex.dev and people match at x402.orthogonal.com.

Among comparable prices in compute, h3 polyfill sits above 43% of them.

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

The seller's tags on h3 polyfill are h3, polyfill, grid and hexagon.

74 other listings in compute declare exactly the same price.

Payment options as declared

the payment options, as of 2026-09-16 21:17 UTC · method · pinnable

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-16 05:48 UTC · method · pinnableendpoint 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-16 05:48 UTC	pass	daily-2026-09-16
2026-09-15 06:05 UTC	pass	daily-2026-09-15
2026-09-14 05:36 UTC	pass	daily-2026-09-14
2026-09-13 05:30 UTC	pass	daily-2026-09-13
2026-09-12 07:47 UTC	pass	daily-2026-09-12
2026-09-11 11:38 UTC	pass	daily-2026-09-11

Registry presence

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

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:26 UTC · method · live

The input and output block

{
  "input": {
    "body": {
      "geojson": {
        "type": "Polygon",
        "coordinates": [
          [
            [
              -122.43,
              37.77
            ],
            [
              -122.4,
              37.77
            ],
            [
              -122.4,
              37.79
            ],
            [
              -122.43,
              37.79
            ],
            [
              -122.43,
              37.77
            ]
          ]
        ]
      },
      "resolution": 8
    },
    "type": "http",
    "method": "POST",
    "bodyType": "json"
  },
  "output": {
    "type": "json",
    "example": {
      "mode": "polyfill",
      "notes": [],
      "results": [
        {
          "id": null,
          "cells": [
            "8828308283fffff",
            "882830828bfffff",
            "88283082b9fffff",
            "8828308281fffff",
            "8828308287fffff",
            "88283082e3fffff",
            "88283082abfffff",
            "88283082bdfffff",
            "8828308285fffff"
          ],
          "polygon": 0,
          "cellCount": 9,
          "resolution": 8,
          "estimatedCellCount": 15
        }
      ],
      "cellCount": 9,
      "containment": "center",
      "resolutions": [
        8
      ],
      "polygonCount": 1
    }
  }
}

What the listing says

Polyfill: turn a polygon into the set of H3 cells that cover it, so a spatial question becomes a set-membership question you can answer with a join. Send "geojson" as a Polygon, a MultiPolygon, or a Feature or FeatureCollection wrapping them, in EPSG:4326, plus exactly one of "resolution" or "resolutions". Choose the containment rule with "containment": "center" returns cells whose centre is inside the polygon, which is H3's default and under-covers at the edges; "overlapping" returns every cell the polygon touches, so the set fully covers it; "full" returns only cells entirely inside. Holes are respected, a MultiPolygon is treated as one polygon with its parts unioned and deduplicated, and feature ids are echoed so rows join back to your records. This route covers polygons and nothing else: a body carrying "points" is refused rather than served, and because "geojson" is required here that refusal happens before a price is quoted and costs you nothing. To index individual positions to their containing cell, POST /v1/h3/index instead, which is cheaper because it is a much smaller job. What you are paying for here, measured on this runtime: cell count grows about sevenfold per resolution step, so the cost has to be estimated before any cell is generated, which puts a floor of about 1.5 ms on even a city-block polyfill against about 0.003 ms for a one-point index call, and a polyfill at the 100000-cell cap is about 200 ms and 1.8 MB. Anything estimated above that cap is refused with the finest resolution that would have fitted, before a cell is generated; set "estimateOnly" to size a job for the price of the call and nothing else. Input is EPSG:4326, longitude then latitude, and non-areal geometry is refused by name. Limits: 500 polygons, 10000 polygon positions, 4 resolutions per call, 100000 cells per call, and a 1 MiB request body.

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

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 Compute

counted above0%

of 481 that carry counters

cheaper than43%

of 480 with a comparable price

481 endpoints are in this category. 74 declare exactly this price.

the comparison, 2026-09-16 21:17 UTC · method · live

Nearest on price

operationsagents.chain.link0.01 USDCfail
reposapi.gitbeacon.dev0.01 USDCpass
opportunities trendingapi.demandex.dev0.01 USDCpass
people matchx402.orthogonal.com0.01 USDCpass
route executeagent402.tools0.01 USDCpass

Same category, nearest declared price, one per payee wallet (method). the list, 2026-09-16 21:17 UTC · method · live

Elsewhere in the record

Cite this page

The pinned URL below renders this page from the snapshot of 2026-09-16 21:17 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).

Plain text

TOLL, "h3 polyfill on api.geoprimitives.dev", snapshot of 2026-09-16 21:17 UTC. https://tollindex.com/e/api-geoprimitives-dev-v1-h3-polyfill-a3efb0/at/2026-09-16T21-17Z. Accessed [access date].

BibTeX

@misc{toll-e-api-geoprimitives-dev-v1-h3-polyfill-a3efb0-2026-09-16T21-17Z,
  author = {TOLL},
  title = {h3 polyfill on api.geoprimitives.dev},
  howpublished = {\url{https://tollindex.com/e/api-geoprimitives-dev-v1-h3-polyfill-a3efb0/at/2026-09-16T21-17Z}},
  year = {2026},
  month = {9},
  note = {Pinned view of the snapshot of 2026-09-16 21:17 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 h3 polyfill, or reply as the named seller