passlisted in Coinbase#1 by calls of 100 on this host
0.001 USDC
per call, as the listing declares it on eip155:
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- 100% / 100% / 100%
- Calls, trailing 30 days
- 1
- Unique payers, trailing 30 days
- 1
- Last called
- 2026-09-13 15:52 UTC
- First observed by TOLLderived
- 2026-09-13
- Pricederived
- 0.001 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 1 time across 9 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.
TOLL first observed it on 2026-09-13.
blockierer api antwort, a POST endpoint on tempo.halowerk.com, appears in the Coinbase registry; TOLL's taxonomy puts it in the "other" category.
blockierer api antwort is priced at 0.001 USDC on Base.
The request to blockierer api antwort is a json body with the field ziel.
blockierer api antwort answered the sweep of 2026-09-16 with a valid 402, as at every sweep since 2026-09-13.
A response from blockierer api antwort, as declared, includes meta, einheit and blockierer_anzahl.
Of tempo.halowerk.com's 100 listings, blockierer api antwort ranks tied 1st by calls with 99 others.
1% of the host's counted calls go to it.
blockierer api antwort drew a single call from a single payer in the trailing 30 days.
The last call to blockierer api antwort came 3 days before the snapshot, 2026-09-13.
Closest in price to blockierer api antwort within the "other" category: ping at www.api-xpay.com and ping at api.basefeed.io.
blockierer api antwort is the cheapest of 2,769 comparable listings in the "other" category; none asks less.
The wallet paid by blockierer api antwort is the payee of 1,553 endpoints across 67 hosts.
The price of blockierer api antwort is declared by 1,267 other listings in the "other" category too.
the payment options, as of 2026-09-16 04:48 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.001 USDC | exact | 0x2880Ed…1C4E5E |
the checks, as of 2026-09-16 04:39 UTC · method · pinnableendpoint answered HTTP 402
No named check failed.
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-09-16 04:39 UTC | pass | 0 | daily-2026-09-16 |
| 2026-09-15 04:36 UTC | pass | 0 | daily-2026-09-15 |
| 2026-09-14 04:32 UTC | pass | 0 | daily-2026-09-14 |
| 2026-09-13 16:18 UTC | pass | 0 | new-2026-09-13T16-16-08-434Z |
Presence in a registry, not liveness of the service (method). Newest first.
- listed in Coinbase
From the registry record, not validated by TOLL.the declared schema, as of 2026-09-13 15:52 UTC · method · live
The input and output block
{
"input": {
"body": {
"ziel": "https://example.com/"
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"meta": {
"hinweis": "Messwert erst nach Ausführung",
"methode": "Beispiel, keine Live-Messung",
"partial": true,
"objektart": "api-antwort"
},
"einheit": "Anzahl",
"blockierer_anzahl": null
}
}
}Cite this page
The pinned URL below renders this page from the snapshot of 2026-09-16 04:48 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "blockierer api antwort on tempo.halowerk.com", snapshot of 2026-09-16 04:48 UTC. https://tollindex.com/e/tempo-halowerk-com-v1-pruef-tempo-blockierer-api-antwort-466035/at/2026-09-16T04-48Z. Accessed [access date].
BibTeX
@misc{toll-e-tempo-halowerk-com-v1-pruef-tempo-blockierer-api-antwort-466035-2026-09-16T04-48Z,
author = {TOLL},
title = {blockierer api antwort on tempo.halowerk.com},
howpublished = {\url{https://tollindex.com/e/tempo-halowerk-com-v1-pruef-tempo-blockierer-api-antwort-466035/at/2026-09-16T04-48Z}},
year = {2026},
month = {9},
note = {Pinned view of the snapshot of 2026-09-16 04:48 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.