passlisted in Coinbase#1 by calls of 8 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
- 3
- Unique payers, trailing 30 days
- 3
- Last called
- 2026-10-08 05:40 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.003 USDC
- Networks
- 1
How has the volume on this endpoint moved?
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-10-30 with a valid 402, as at every sweep since 2026-09-11.
locode resolve shares fracht.halowerk.com with 7 other listed endpoints and is tied 1st by calls with 5 others.
locode resolve takes 14% of the calls counted across fracht.halowerk.com.
The registry's counters give locode resolve 3 calls and 3 unique payers over 30 days, every call from a different payer.
The last call to locode resolve came 5 days before the snapshot, 2026-10-08.
Closest in price to locode resolve within the "other" category: x402 test at sandbox.node4all.com and stats at uptime.cyberwarex.com.
locode resolve is priced above 20% of comparable listings in the "other" category.
locode resolve out-counts 46% of the 3,825 endpoints in the "other" category that carry counters.
The wallet paid by locode resolve is the payee of 1,941 endpoints across 79 hosts.
The price of locode resolve is declared by 264 other listings in the "other" category too.
the payment options, as of 2026-10-13 14:08 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.003 USDC | exact | 0x2880Ed…1C4E5E |
the checks, as of 2026-10-30 10:03 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-10-30 10:03 UTC | pass | 0 | daily-2026-10-30 |
| 2026-10-29 09:42 UTC | pass | 0 | daily-2026-10-29 |
| 2026-10-28 10:04 UTC | pass | 0 | daily-2026-10-28 |
| 2026-10-27 09:46 UTC | pass | 0 | daily-2026-10-27 |
| 2026-10-26 16:10 UTC | pass | 0 | daily-2026-10-26 |
| 2026-10-23 10:04 UTC | pass | 1 | daily-2026-10-23 |
| 2026-10-21 12:31 UTC | pass | 1 | daily-2026-10-21 |
| 2026-10-20 12:13 UTC | pass | 1 | daily-2026-10-20 |
| 2026-10-19 09:50 UTC | pass | 1 | daily-2026-10-19 |
| 2026-10-18 11:38 UTC | pass | 1 | daily-2026-10-18 |
| 2026-10-16 07:47 UTC | pass | 1 | daily-2026-10-16 |
| 2026-10-15 09:38 UTC | pass | 1 | daily-2026-10-15 |
| 2026-10-14 07:36 UTC | pass | 1 | daily-2026-10-14 |
| 2026-10-13 12:23 UTC | pass | 1 | daily-2026-10-13 |
| 2026-10-12 09:48 UTC | pass | 1 | daily-2026-10-12 |
| 2026-10-11 08:26 UTC | pass | 1 | daily-2026-10-11 |
| 2026-10-10 16:35 UTC | pass | 1 | daily-2026-10-10 |
| 2026-10-09 09:34 UTC | pass | 1 | daily-2026-10-09 |
| 2026-10-08 10:58 UTC | pass | 1 | daily-2026-10-08 |
| 2026-10-07 10:25 UTC | pass | 1 | daily-2026-10-07 |
| 2026-10-06 11:07 UTC | pass | 1 | daily-2026-10-06 |
| 2026-10-05 09:53 UTC | pass | 1 | daily-2026-10-05 |
| 2026-10-04 12:03 UTC | pass | 1 | daily-2026-10-04 |
| 2026-10-03 06:35 UTC | pass | 1 | daily-2026-10-03 |
| 2026-10-02 15:47 UTC | pass | 1 | daily-2026-10-02 |
| 2026-10-01 08:35 UTC | pass | 1 | daily-2026-10-01 |
| 2026-09-30 07:58 UTC | pass | 1 | daily-2026-09-30 |
| 2026-09-29 20:10 UTC | pass | 1 | daily-2026-09-29 |
| 2026-09-28 17:14 UTC | pass | 1 | daily-2026-09-28 |
| 2026-09-23 07:11 UTC | pass | 1 | daily-2026-09-23 |
| 2026-09-22 07:24 UTC | pass | 1 | daily-2026-09-22 |
| 2026-09-21 07:46 UTC | pass | 1 | daily-2026-09-21 |
| 2026-09-19 05:47 UTC | pass | 1 | daily-2026-09-19 |
| 2026-09-18 14:21 UTC | pass | 1 | daily-2026-09-18 |
| 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-10-08 05:40 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-10-13 14:08 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-10-13 14:08 UTC. https://tollindex.com/e/fracht-halowerk-com-v1-locode-resolve-96bf14/at/2026-10-13T14-08Z. Accessed [access date].
BibTeX
@misc{toll-e-fracht-halowerk-com-v1-locode-resolve-96bf14-2026-10-13T14-08Z,
author = {TOLL},
title = {locode resolve on fracht.halowerk.com},
howpublished = {\url{https://tollindex.com/e/fracht-halowerk-com-v1-locode-resolve-96bf14/at/2026-10-13T14-08Z}},
year = {2026},
month = {10},
note = {Pinned view of the snapshot of 2026-10-13 14:08 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.