passabsent from every registrycounted above 97% of Compute
0.005 USDC
per call, as the listing declares it on eip155:
Compare with anotherEvery figure as JSONCite this page
the price, as of 2026-09-15 11:42 UTC · method
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- — / — / 100%
- Calls, trailing 30 days
- 17
- Unique payers, trailing 30 days
- 2
- Last called
- 2026-08-16 12:49 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.005 USDC
- Networks
- 2
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 27 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.
aeml-x402.zeabur.app serves gauge history, a GET endpoint that TOLL places in compute, listed in neither registry at the last pull.
A call to gauge history costs 0.005 USDC on Base, as declared.
gauge history takes the query parameters entity and signal_id.
For gauge history the listing declares 2 accepts on Base and Solana, to 2 different wallets.
gauge history declares json output without an example.
On 2026-09-15 it returned a valid 402 challenge, as at every sweep since 2026-09-11.
gauge history is the only listed endpoint on aeml-x402.zeabur.app.
The registry's counters give gauge history 17 calls and 2 unique payers over 30 days, about 9 calls per payer.
gauge history was last called 58 days before the snapshot.
Closest in price to gauge history within compute: md at url2md.io and media info at agent402.tools.
Among comparable prices in compute, gauge history sits above 38% of them.
Across compute, 1,852 endpoints carry counters and gauge history out-counts 97% of them.
Its payee wallet receives for 120 listed endpoints across 2 hosts.
The seller's tags on gauge history are gauge, history, no-data-no-charge and descriptive-only.
gauge history was missing from the Coinbase registry at the pull of 2026-09-15, confirmed at the pull of 2026-09-15; that is registry presence, not liveness.
The price of gauge history is declared by 201 other listings in compute 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.
the payment options, as of 2026-09-15 11:42 UTC · method
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.005 USDC | exact | 0x2d16a2…c4c6c3 |
| Coinbase | solana: | USDC | 0.005 USDC | exact | 8qEn3Y3G…rQAY3n |
the checks, as of 2026-09-15 06:37 UTC · methodendpoint answered HTTP 402
bazaar.info.output.example· advisory, does not affect the verdict · an output example is provided (advisory)
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-09-15 06:37 UTC | pass | 1 | daily-2026-09-15 |
| 2026-09-14 06:05 UTC | pass | 1 | daily-2026-09-14 |
| 2026-09-13 05:57 UTC | pass | 1 | daily-2026-09-13 |
| 2026-09-12 08:14 UTC | pass | 1 | daily-2026-09-12 |
| 2026-09-11 12:41 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-16 12:49 UTC · method
The input and output block
{
"input": {
"type": "http",
"method": "GET",
"example": {
"entity": "07010000",
"signal_id": "hydrology.river-level"
},
"queryParams": {
"entity": "required - monitored object id, paired with signal_id; free list at GET /gauge/catalog?signal_id=<signal_id> -> signals[",
"signal_id": "required - signal id (genus.species); free list at GET /gauge/catalog (paged; ?all=1 for every line)"
},
"exampleRequest": "/gauge/history?signal_id=hydrology.river-level&entity=07010000"
},
"output": {
"type": "json"
}
}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, "gauge history on aeml-x402.zeabur.app". https://tollindex.com/e/aeml-x402-zeabur-app-gauge-history-d14da0. Accessed [access date].
BibTeX
@misc{toll-e-aeml-x402-zeabur-app-gauge-history-d14da0-2026-10-13,
author = {TOLL},
title = {gauge history on aeml-x402.zeabur.app},
howpublished = {\url{https://tollindex.com/e/aeml-x402-zeabur-app-gauge-history-d14da0}},
year = {2026},
month = {10},
note = {Frozen at its last observation, 2026-10-13 14:08 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.