passabsent from every registry#2 by calls of 6 on this host
0.0045 USDC
per call, as the listing declares it on eip155:
Compare with anotherEvery figure as JSONCite this page
the price, as of 2026-09-14 12:43 UTC · method
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- — / 100% / 100%
- Calls, trailing 30 days
- 2
- Unique payers, trailing 30 days
- 1
- Last called
- 2026-08-15 21:07 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.0045 USDC
- Networks
- 1
How big is this endpoint among the ones like it?
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.
fittings.sh serves hazard active events, a GET endpoint that TOLL places in the "other" category, listed in neither registry at the last pull.
On Base, hazard active events asks 0.0045 USDC per call.
hazard active events takes the query parameters limit, status and category.
The daily sweep got a valid payment challenge from hazard active events on 2026-09-14, as at every sweep since 2026-09-11.
With 6 endpoints listed on fittings.sh, hazard active events is tied 2nd by calls with 1 other.
Of the calls counted across fittings.sh, hazard active events takes 22%.
Over 30 days: 2 calls, one payer.
The most recent call was 52 days before the snapshot.
hazard active events sits nearest in price to ping (www.api-xpay.com) and aviation airport status (api.x402node.dev) among listings in the "other" category.
hazard active events is priced above 33% of comparable listings in the "other" category.
The wallet paid by hazard active events is the payee of 145 endpoints on one host.
The seller's own tags are hazard.
The listing for hazard active events fails only advisory checks about output metadata; the verdict is unaffected.
hazard active events 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.
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.
the payment options, as of 2026-09-14 12:43 UTC · method
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.0045 USDC | upto | 0xe02544…d98638 |
the checks, as of 2026-09-14 04:12 UTC · methodendpoint answered HTTP 402
bazaar.info.output· advisory, does not affect the verdict · output metadata is present (advisory)
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-09-14 04:12 UTC | pass | 1 | daily-2026-09-14 |
| 2026-09-13 04:12 UTC | pass | 1 | daily-2026-09-13 |
| 2026-09-12 06:27 UTC | pass | 1 | daily-2026-09-12 |
| 2026-09-11 09:55 UTC | pass | 1 | daily-2026-09-11 |
Presence in a registry, not liveness of the service (method). Newest first.
- absence from Coinbase confirmed, rule v1
- absent from Coinbase at this pull
- listed in Coinbase
From the registry record, not validated by TOLL.the declared schema, as of 2026-08-15 21:07 UTC · method
The input and output block
{
"input": {
"type": "http",
"method": "GET",
"queryParams": {
"limit": 5,
"status": "open",
"category": "wildfires"
}
},
"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, "hazard active events on fittings.sh". https://tollindex.com/e/fittings-sh-v1-hazard-active-events-2748b9. Accessed [access date].
BibTeX
@misc{toll-e-fittings-sh-v1-hazard-active-events-2748b9-2026-10-07,
author = {TOLL},
title = {hazard active events on fittings.sh},
howpublished = {\url{https://tollindex.com/e/fittings-sh-v1-hazard-active-events-2748b9}},
year = {2026},
month = {10},
note = {Frozen at its last observation, 2026-10-07 05:57 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.