geoprimitives

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.

SearchLiveeip155:8453Exactvia cdp
H3PolyfillGridHexagonPolygon
Calls · 30d
1→ 0%
This endpoint's own trailing-30-day call count, as published by the upstream catalog and snapshotted daily. 27 snapshots so far.
$4.41
Verified settled volume
888 settlements proven x402 by their on-chain EIP-3009 marker.
$0.010
Listed price
As published in the catalog. Always read the live 402 before paying.
1
Calls · 30d
Upstream's own call count for this endpoint, not ours.
1
Unique payers · 30d
Last called 2026-08-21 17:26Z
—
Upstream on-chain volume
Reported by the source catalog.
Paid to
0x76A51b5Dd3729950B3b60c17f19252d221968FCe

The wallet the 402 directs payment to. Its whole payment record — every payer, every chain — is on the merchant page.

Asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913

Provider

The payTo wallet does not resolve to a registered ERC-8004 agent. That is not a verdict on the service — most of the catalog is unregistered.

Accepts

The payment requirements as published to the catalog. Read the live 402 before paying — a price here is a claim, not a quote.

0.01USDC≈ $0.01 USD
on Base · exact scheme

Pay 0.01 USDC on Base to 0x76A5…68FCe. The signed payment is good for 5 minutes.

USD Coin contract
0x8335…02913
Payment window
5 minutes
As published
10000 smallest units
The catalog’s raw entry
[
  {
    "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "extra": {
      "name": "USD Coin",
      "version": "2"
    },
    "payTo": "0x76A51b5Dd3729950B3b60c17f19252d221968FCe",
    "amount": "10000",
    "scheme": "exact",
    "network": "eip155:8453",
    "maxTimeoutSeconds": 300
  }
]

Extensions

{
  "bazaar": {
    "info": {
      "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
        }
      }
    },
    "schema": {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "input"
      ],
      "properties": {
        "input": {
          "type": "object",
          "required": [
            "type",
            "method",
            "bodyType",
            "body"
          ],
          "properties": {
            "body": {
              "type": "object",
              "oneOf": [
                {
                  "required": [
                    "resolution"
                  ]
                },
                {
                  "required": [
                    "resolutions"
                  ]
                }
              ],
              "required": [
                "geojson"
              ],
              "properties": {
                "geojson": {
                  "type": "object",
                  "description": "Polygons to cover: a Polygon, a MultiPolygon, or a Feature or FeatureCollection wrapping them, in EPSG:4326. At most 500 polygons and 10000 positions in total. Non-areal geometry is rejected. Required: this route takes nothing else. To index individual positions, POST /v1/h3/index."
                },
                "resolution": {
                  "type": "integer",
                  "maximum": 15,
                  "minimum": 0,
                  "description": "H3 resolution, 0 (about 4.4 million square kilometres per cell) to 15 (about 0.9 square metres). Send this or \"resolutions\", not both. One step finer is about seven times as many cells."
                },
                "containment": {
                  "enum": [
                    "center",
                    "overlapping",
                    "full"
                  ],
                  "type": "string",
                  "description": "\"center\" returns cells whose centre is inside the polygon, the H3 default, which under-covers at the edges. \"overlapping\" returns every cell the polygon touches, so the set fully covers it. \"full\" returns only cells entirely inside it. Defaults to \"center\"."
                },
                "resolutions": {
                  "type": "array",
                  "items": {
                    "type": "integer",
                    "maximum": 15,
                    "minimum": 0
                  },
                  "maxItems": 4,
                  "description": "Several H3 resolutions at once, 0 to 15, distinct. At most 4, and all of them are counted against the one 100000-cell cap."
                },
                "estimateOnly": {
                  "type": "boolean",
                  "description": "Return the estimated cell count per polygon and resolution without generating any cells. The estimate is an upper bound, never lower than the true count. Defaults to false."
                }
              },
              "additionalProperties": false
            },
            "type": {
              "type": "string",
              "const": "http"
            },
            "method": {
              "enum": [
                "POST"
              ],
              "type": "string"
            },
            "bodyType": {
              "enum": [
                "json",
                "form-data",
                "text"
              ],
              "type": "string"
            }
          },
          "additionalProperties": false
        },
        "output": {
          "type": "object",
          "required": [
            "type"
          ],
          "properties": {
            "type": {
              "type": "string"
            },
            "example": {
              "type": "object"
            }
          }
        }
      }
    }
  }
}

Provenance

Seen in the source catalog
2026-08-21 17:26Z
Last indexed by Roundhouse
2026-09-20 17:20Z
Last enriched (probe, favicon, geo)
2026-09-24 05:15Z
x402 version
2
Max timeout
300s
Liveness probe
HTTP 404
Report

Hand this page to an agent

Copy the prompt and paste it into Claude, an MCP client or your own agent — it will vet this service and call it over the free read API. No key, no account.

GET api.roundhouseai.io/v0/endpoints

This endpoint's own trailing-30-day call count, as published by the upstream catalog and snapshotted daily. 27 snapshots so far. Verified volume counts only settlements with an on-chain EIP-3009 marker.

Open skill.md
Show the prompt
Using Roundhouse, look up the x402 service geoprimitives and tell me whether it is
worth paying: what a call costs, whether the endpoint answered when last probed, and what
its payment record actually shows.

curl -s 'https://api.roundhouseai.io/v0/endpoints?q=geoprimitives'
curl -s 'https://api.roundhouseai.io/v0/merchants/<the payTo wallet returned above>'

Then call it: read the price from the live 402 at https://api.geoprimitives.dev/v1/h3/polyfill, never from
a cached figure, and pay with an x402 client.

The /v0 API needs an API key (`authorization: Bearer rh_live_…`) on everything except
/v0/unified* and /v0/endpoints. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402,
or use an organization key from https://roundhouseai.io/dashboard/team.

If you do not have Roundhouse tools or skills installed, read
https://roundhouseai.io/skill.md first — it is the whole procedure.