TOLL

What software pays for, recorded every six hours.

Snapshot
2026-09-15 16:57 UTC
Sweep
daily-2026-09-15 · finished 2026-09-15 07:10 UTC
Listed
16,167

spatial point in polygon derived

fittings.shOtherderived

POST https://fittings.sh/v1/spatial/point-in-polygon

failabsent from every registry#1 by calls of 9 on this host

0.005 USDC

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

Compare with anotherEvery figure as JSONCite this page

the price, as of 2026-09-14 12:43 UTC · method

Validation state
fail
as of 2026-09-14 06:35 UTC · method · sweep daily-2026-09-14
Uptime, 7 / 30 / 90 days
50% / 50% / 50%
as of 2026-09-14 06:35 UTC · method · 2 of 4 in 7d, 2 of 4 in 30d, 2 of 4 in 90d
Calls, trailing 30 days
2
as of 2026-09-14 12:43 UTC · method
Unique payers, trailing 30 days
1
as of 2026-09-14 12:43 UTC · method
Last called
2026-08-15 21:04 UTC
as of 2026-09-14 12:43 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-14 12:43 UTC · method · on eip155:8453
Networks
1
as of 2026-09-14 12:43 UTC · method

Counters

24 observations, 2 of them a change, fewer than the 3 a trace needs

How big is this endpoint among the ones like it?

1 call100,000this endpoint
Calls counted in the trailing thirty days across the 2,777 endpoints in Other that carry counters, binned on a logarithmic scale because the range runs over five orders of magnitude. The marked bin is this endpoint, at 2: 652 in the category are counted higher and 2,124 lower.

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

On 2026-09-14 it did not answer at all; TOLL records that as a failure.

fittings.sh serves spatial point in polygon, a POST endpoint that TOLL places in the "other" category, listed in neither registry at the last pull.

Per call, spatial point in polygon declares 0.005 USDC on Base.

The request to spatial point in polygon is a json body with the fields point and polygon.

One payer accounts for all 2 calls to spatial point in polygon over 30 days.

Its last counted call came 31 days before the snapshot.

spatial point in polygon is one of 9 listed endpoints on fittings.sh, tied 1st by calls with 2 others among them.

spatial point in polygon takes 18% of the calls counted across fittings.sh.

Among comparable prices in the "other" category, spatial point in polygon sits above 58% of them.

Closest in price to spatial point in polygon within the "other" category: aviation airport status at api.x402node.dev and phone intelligence at x402.orthogonal.com.

The wallet paid by spatial point in polygon is the payee of 145 endpoints on one host.

The seller's tags on spatial point in polygon are spatial.

spatial point in polygon was missing from the Coinbase registry at the pull of 2026-09-14, confirmed at the pull of 2026-09-15; that is registry presence, not liveness.

The price of spatial point in polygon is declared by 142 other listings in the "other" category 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-14 12:43 UTC · method

Every payment option declared on this listing
registrynetworkassetamountschemepay to
Coinbaseeip155:8453USDC0.005 USDCupto0xe02544…d98638

Preflight checks at the last sweep

the checks, as of 2026-09-14 06:35 UTC · methodendpoint answered HTTP none

  • endpoint_reachable · the endpoint answered at all

Validation history, 90 days

Every sweep that observed this endpoint, newest first.

Validation observations over the last 90 days
observed, UTCstatefailed checkssweep
2026-09-14 06:35 UTCfail1daily-2026-09-14
2026-09-13 06:24 UTCpass1daily-2026-09-13
2026-09-12 13:57 UTCpass1daily-2026-09-12
2026-09-11 14:54 UTCfail1daily-2026-09-11

Registry presence

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

  1. absence from Coinbase confirmed, rule v1
  2. absent from Coinbase at this pull
  3. listed in Coinbase

Declared input and output, as listed

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

The input and output block
{
  "input": {
    "body": {
      "point": {
        "lat": 38.8977,
        "lon": -77.0365
      },
      "polygon": {
        "type": "Polygon",
        "coordinates": [
          [
            [
              -77.12,
              38.79
            ],
            [
              -76.91,
              38.79
            ],
            [
              -76.91,
              39
            ],
            [
              -77.12,
              39
            ],
            [
              -77.12,
              38.79
            ]
          ]
        ]
      }
    },
    "type": "http",
    "method": "POST",
    "bodyType": "json"
  },
  "output": null
}
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, "spatial point in polygon on fittings.sh". https://tollindex.com/e/fittings-sh-v1-spatial-point-in-polygon-fe42d8. Accessed [access date].

BibTeX

@misc{toll-e-fittings-sh-v1-spatial-point-in-polygon-fe42d8-2026-09-15,
  author = {TOLL},
  title = {spatial point in polygon on fittings.sh},
  howpublished = {\url{https://tollindex.com/e/fittings-sh-v1-spatial-point-in-polygon-fe42d8}},
  year = {2026},
  month = {9},
  note = {Frozen at its last observation, 2026-09-15 16:57 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 spatial point in polygon, or reply as the named seller

No account, no token. Published unedited with its outcome, upheld or not. Do not include personal data.

Kind

Published as typed. Optional.

10 to 4,000 characters.

Verify with the payee wallet (optional, EVM)

Sign this message with the wallet named on the page and paste the signature; it is checked, stored, never published. TOLL reply about endpoint fe42d8edaa4efed7d37d6d3856c1ef26e030029d459a9eb7d75515bba22a41aa from wallet 0xe025442C0d6dC17aD2b9eB888B3565bdFCd98638

The 0x address named as payee on this page, 42 characters.

The hex signature of the message above, starting 0x.