passlisted in Coinbase#1 by calls of 7 on this host
0.003 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
- 2
- Unique payers, trailing 30 days
- 2
- Last called
- 2026-09-14 20:02 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.003 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 34 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.
locode resolve, a POST endpoint on fracht.halowerk.com, appears in the Coinbase registry; TOLL's taxonomy puts it in the "other" category.
locode resolve is priced at 0.003 USDC on Base.
Requests carry a json body with the fields locode, source and records.
locode resolve declares nothing about its output; validate flags that as advisory, not a verdict.
locode resolve answered the sweep of 2026-09-17 with a valid 402, as at every sweep since 2026-09-11.
locode resolve shares fracht.halowerk.com with 6 other listed endpoints and is 1st by calls.
locode resolve takes 25% of the calls counted across fracht.halowerk.com.
The registry's counters give locode resolve 2 calls and 2 unique payers over 30 days, every call from a different payer.
The last call to locode resolve came 2 days before the snapshot, 2026-09-14.
Closest in price to locode resolve within the "other" category: brokenkeyremapperlink at brokenkey-api-link-tau.vercel.app and convert weight at weight402endpoint.vercel.app.
locode resolve is priced above 51% of comparable listings in the "other" category.
The wallet paid by locode resolve is the payee of 1,553 endpoints across 67 hosts.
The price of locode resolve is declared by 80 other listings in the "other" category too.
the payment options, as of 2026-09-17 04:51 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.003 USDC | exact | 0x2880Ed…1C4E5E |
the checks, as of 2026-09-17 05:39 UTC · method · pinnableendpoint 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-17 05:39 UTC | pass | 1 | daily-2026-09-17 |
| 2026-09-16 05:38 UTC | pass | 1 | daily-2026-09-16 |
| 2026-09-15 05:55 UTC | pass | 1 | daily-2026-09-15 |
| 2026-09-14 05:27 UTC | pass | 1 | daily-2026-09-14 |
| 2026-09-13 05:22 UTC | pass | 1 | daily-2026-09-13 |
| 2026-09-12 07:39 UTC | pass | 1 | daily-2026-09-12 |
| 2026-09-11 11:28 UTC | pass | 1 | daily-2026-09-11 |
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-14 20:02 UTC · method · live
The input and output block
{
"input": {
"body": {
"locode": "DEHAM",
"source": {
"url": "https://unece.org/trade/uncefact/unlocode",
"title": "UN/LOCODE",
"published_at": "2026-07-01T00:00:00Z"
},
"records": [
{
"name": "Hamburg",
"locode": "DEHAM",
"functions": "12345---",
"coordinates": "5333N 01000E",
"subdivision": "HH"
}
]
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": null
}Cite this page
The pinned URL below renders this page from the snapshot of 2026-09-17 04:51 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "locode resolve on fracht.halowerk.com", snapshot of 2026-09-17 04:51 UTC. https://tollindex.com/e/fracht-halowerk-com-v1-locode-resolve-96bf14/at/2026-09-17T04-51Z. Accessed [access date].
BibTeX
@misc{toll-e-fracht-halowerk-com-v1-locode-resolve-96bf14-2026-09-17T04-51Z,
author = {TOLL},
title = {locode resolve on fracht.halowerk.com},
howpublished = {\url{https://tollindex.com/e/fracht-halowerk-com-v1-locode-resolve-96bf14/at/2026-09-17T04-51Z}},
year = {2026},
month = {9},
note = {Pinned view of the snapshot of 2026-09-17 04:51 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.