TOLL

What software pays for, recorded every six hours.

Snapshot
2026-10-13 14:08 UTC
Sweep
daily-2026-10-28 · finished 2026-10-28 13:07 UTC
Listed
32,435

mesh route derived

iot.halowerk.comCommunicationsderived

POST https://iot.halowerk.com/v1/mesh-route

passlisted in Coinbase#6 by calls of 10 on this host

0.004 USDC

per call, as the listing declares it on eip155:8453

Compare with anotherEvery figure as JSONCite this page

the price, as of 2026-10-13 14:08 UTC · method · pinnable

Validation state
pass
as of 2026-10-28 08:41 UTC · method · pinnable · sweep daily-2026-10-28
Uptime, 7 / 30 / 90 days
100% / 100% / 100%
as of 2026-10-28 08:41 UTC · method · pinnable · 4 of 4 in 7d, 22 of 22 in 30d, 36 of 36 in 90d
Calls, trailing 30 days
2
as of 2026-10-13 14:08 UTC · method · pinnable
Unique payers, trailing 30 days
2
as of 2026-10-13 14:08 UTC · method · pinnable
Last called
2026-10-08 06:12 UTC
as of 2026-10-13 14:08 UTC · method · pinnable
First observed by TOLLderived
2026-09-10
as of 2026-09-10 19:08 UTC · method · pinnable · observation began 10 September 2026; listings that predate it show that date
Pricederived
0.004 USDC
as of 2026-10-13 14:08 UTC · method · pinnable · on eip155:8453
Networks
1
as of 2026-10-13 14:08 UTC · method · pinnable

Counters

105 observations, 2 of them a change, fewer than the 3 a trace needs

How big is this endpoint among the ones like it?

1 call100,000this endpoint
Calls counted in the trailing thirty days across the 935 endpoints in Communications that carry counters, binned on a logarithmic scale because the range runs over five orders of magnitude. The marked bin is this endpoint, at 2: 309 in the category are counted higher and 625 lower.

No trace is drawn of this endpoint’s own volume. Its counters have changed 2 times across 105 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.

In words

iot.halowerk.com serves mesh route, a POST endpoint that TOLL places in communications, listed in the Coinbase registry.

Per call, mesh route declares 0.004 USDC on Base.

mesh route takes a json body with the fields goal, links, nodes and start.

mesh route declares nothing about its output; validate flags that as advisory, not a verdict.

mesh route answered the sweep of 2026-10-28 with a valid 402, as at every sweep since 2026-09-11.

mesh route is one of 10 listed endpoints on iot.halowerk.com, tied 6th by calls with 4 others among them.

mesh route takes 6% of the calls counted across iot.halowerk.com.

The registry's counters give mesh route 2 calls and 2 unique payers over 30 days, every call from a different payer.

mesh route was last called 5 days before the snapshot.

Closest in price to mesh route within communications: users tweets at glim.sh and tools validate email at api.qocgpiywhm.com.

Among comparable prices in communications, mesh route sits above 14% of them.

1,941 listed endpoints across 79 hosts pay to the same wallet.

mesh route dropped out of the registry at the pull of 2026-10-01 and was listed again on 2026-10-07.

The price of mesh route is declared by 35 other listings in communications too.

Payment options as declared

the payment options, as of 2026-10-13 14:08 UTC · method · pinnable

Every payment option declared on this listing
registrynetworkassetamountschemepay to
Coinbaseeip155:8453USDC0.004 USDCexact0x2880Ed…1C4E5E

Preflight checks at the last sweep

the checks, as of 2026-10-28 08:41 UTC · method · pinnableendpoint answered HTTP 402

No named check failed.

Validation history, 90 days

Every sweep that observed this endpoint, newest first.

Validation observations over the last 90 days
observed, UTCstatefailed checkssweep
2026-10-28 08:41 UTCpass0daily-2026-10-28
2026-10-27 08:26 UTCpass0daily-2026-10-27
2026-10-26 13:44 UTCpass0daily-2026-10-26
2026-10-23 08:32 UTCpass1daily-2026-10-23
2026-10-21 11:06 UTCpass1daily-2026-10-21
2026-10-20 10:42 UTCpass1daily-2026-10-20
2026-10-19 08:16 UTCpass1daily-2026-10-19
2026-10-18 10:18 UTCpass1daily-2026-10-18
2026-10-17 20:32 UTCpass1daily-2026-10-17
2026-10-16 06:29 UTCpass1daily-2026-10-16
2026-10-15 08:13 UTCpass1daily-2026-10-15
2026-10-14 06:19 UTCpass1daily-2026-10-14
2026-10-13 11:00 UTCpass1daily-2026-10-13
2026-10-12 08:22 UTCpass1daily-2026-10-12
2026-10-11 07:08 UTCpass1daily-2026-10-11
2026-10-10 15:10 UTCpass1daily-2026-10-10
2026-10-09 07:42 UTCpass1daily-2026-10-09
2026-10-08 09:09 UTCpass1daily-2026-10-08
2026-10-07 08:30 UTCpass1daily-2026-10-07
2026-10-01 07:49 UTCpass1daily-2026-10-01
2026-09-30 07:09 UTCpass1daily-2026-09-30
2026-09-29 19:26 UTCpass1daily-2026-09-29
2026-09-28 06:13 UTCpass1daily-2026-09-28
2026-09-25 20:57 UTCpass1daily-2026-09-25
2026-09-23 06:33 UTCpass1daily-2026-09-23
2026-09-22 06:44 UTCpass1daily-2026-09-22
2026-09-21 07:06 UTCpass1daily-2026-09-21
2026-09-19 05:07 UTCpass1daily-2026-09-19
2026-09-18 12:22 UTCpass1daily-2026-09-18
2026-09-17 05:03 UTCpass1daily-2026-09-17
2026-09-16 05:03 UTCpass1daily-2026-09-16
2026-09-15 05:02 UTCpass1daily-2026-09-15
2026-09-14 04:53 UTCpass1daily-2026-09-14
2026-09-13 04:52 UTCpass1daily-2026-09-13
2026-09-12 07:08 UTCpass1daily-2026-09-12
2026-09-11 10:47 UTCpass1daily-2026-09-11

Registry presence

Presence in a registry, not liveness of the service (method). Newest first.

  1. back in Coinbase
  2. absence from Coinbase confirmed, rule v1
  3. absent from Coinbase at this pull
  4. listed in Coinbase

Declared input and output, as listed

From the registry record, not validated by TOLL.the declared schema, as of 2026-10-08 06:12 UTC · method · live

The input and output block
{
  "input": {
    "body": {
      "goal": "sensor",
      "links": [
        {
          "to": "relay-a",
          "cost": 1,
          "from": "gateway"
        },
        {
          "to": "sensor",
          "cost": 2,
          "from": "relay-a"
        },
        {
          "to": "relay-b",
          "cost": 2,
          "from": "gateway"
        },
        {
          "to": "sensor",
          "cost": 4,
          "from": "relay-b"
        }
      ],
      "nodes": [
        "gateway",
        "relay-a",
        "relay-b",
        "sensor"
      ],
      "start": "gateway"
    },
    "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, "mesh route on iot.halowerk.com", snapshot of 2026-10-13 14:08 UTC. https://tollindex.com/e/iot-halowerk-com-v1-mesh-route-661bf1/at/2026-10-13T14-08Z. Accessed [access date].

BibTeX

@misc{toll-e-iot-halowerk-com-v1-mesh-route-661bf1-2026-10-13T14-08Z,
  author = {TOLL},
  title = {mesh route on iot.halowerk.com},
  howpublished = {\url{https://tollindex.com/e/iot-halowerk-com-v1-mesh-route-661bf1/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].}
}

Reports and replies about this endpoint

None yet. Anything submitted through the form below is published here with its outcome.

Report an error about mesh route, or reply as the named seller

No account, no token. Published unedited with its outcome, upheld or not. Do not include personal data.

Kind

Published as typed. Optional.

10 to 4,000 characters.

Verify with the payee wallet (optional, EVM)

Sign this message with the wallet named on the page and paste the signature; it is checked, stored, never published. TOLL reply about endpoint 661bf118bd460d704bddcca92661ebb1402c597decce20568c78a5169741eb88 from wallet 0x2880EdfFF13100677Bf97A3CBdF3Bc34771C4E5E

The 0x address named as payee on this page, 42 characters.

The hex signature of the message above, starting 0x.