TOLL

What software pays for, recorded every six hours.

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

digital twin sync derived

iot.halowerk.comSearchderived

POST https://iot.halowerk.com/v1/digital-twin-sync

passlisted in Coinbase#1 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-30 06:13 UTC · method · pinnable · sweep daily-2026-10-30
Uptime, 7 / 30 / 90 days
100% / 100% / 100%
as of 2026-10-30 06:13 UTC · method · pinnable · 6 of 6 in 7d, 28 of 28 in 30d, 46 of 46 in 90d
Calls, trailing 30 days
6
as of 2026-10-13 14:08 UTC · method · pinnable
Unique payers, trailing 30 days
6
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

122 observations, 8 of them a change

How has the volume on this endpoint moved?

-01234567610 Sep11 Sep12 Sep13 Sep14 Sep15 Sep16 Sep17 Sep18 Sep19 Sep20 Sep21 Sep22 Sep23 Sep24 Sep25 Sep26 Sep27 Sep28 Sep29 Sep30 Sep1 Oct2 Oct3 Oct4 Oct5 Oct6 Oct7 Oct8 Oct9 Oct10 Oct11 Oct12 Oct13 Oct
Calls counted in the trailing 30 days on this endpoint, at every snapshot since 2026-09-10. Each point is a trailing-30-day sum as the registry published it, not a daily rate. The axis is truncated to the range of the data with a break at its foot.

In words

At iot.halowerk.com, digital twin sync takes POST requests, is listed in the Coinbase registry, and falls under search by TOLL's rules.

digital twin sync is priced at 0.004 USDC on Base.

The request to digital twin sync is a json body with the fields local_changes and remote_changes.

digital twin sync declares nothing about its output; validate flags that as advisory, not a verdict.

digital twin sync answered the sweep of 2026-10-30 with a valid 402, as at every sweep since 2026-09-11.

digital twin sync shares iot.halowerk.com with 9 other listed endpoints and is 1st by calls.

digital twin sync takes 19% of the calls counted across iot.halowerk.com.

The registry's counters give digital twin sync 6 calls and 6 unique payers over 30 days, every call from a different payer.

The last call to digital twin sync came 5 days before the snapshot, 2026-10-08.

Closest in price to digital twin sync within search: search at twitter.use.x402atlas.com and search at api.you.com.

digital twin sync is priced above 21% of comparable listings in search.

Within search, 81% of endpoints with counters have fewer calls.

The wallet paid by digital twin sync is the payee of 1,941 endpoints across 79 hosts.

The price of digital twin sync is declared by 72 other listings in search 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-30 06:13 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-30 06:13 UTCpass0daily-2026-10-30
2026-10-29 05:55 UTCpass0daily-2026-10-29
2026-10-28 06:19 UTCpass0daily-2026-10-28
2026-10-27 06:13 UTCpass0daily-2026-10-27
2026-10-26 11:33 UTCpass0daily-2026-10-26
2026-10-24 20:55 UTCpass1daily-2026-10-24
2026-10-23 06:05 UTCpass1daily-2026-10-23
2026-10-22 04:19 UTCpass1daily-2026-10-22
2026-10-21 07:43 UTCpass1daily-2026-10-21
2026-10-20 07:37 UTCpass1daily-2026-10-20
2026-10-19 05:48 UTCpass1daily-2026-10-19
2026-10-18 08:02 UTCpass1daily-2026-10-18
2026-10-17 18:03 UTCpass1daily-2026-10-17
2026-10-16 04:17 UTCpass1daily-2026-10-16
2026-10-15 05:50 UTCpass1daily-2026-10-15
2026-10-14 04:15 UTCpass1daily-2026-10-14
2026-10-13 08:40 UTCpass1daily-2026-10-13
2026-10-12 06:05 UTCpass1daily-2026-10-12
2026-10-11 04:28 UTCpass1daily-2026-10-11
2026-10-10 09:40 UTCpass1daily-2026-10-10
2026-10-09 04:25 UTCpass1daily-2026-10-09
2026-10-08 06:02 UTCpass1daily-2026-10-08
2026-10-07 04:35 UTCpass1daily-2026-10-07
2026-10-06 06:06 UTCpass1daily-2026-10-06
2026-10-05 05:56 UTCpass1daily-2026-10-05
2026-10-04 08:47 UTCpass1daily-2026-10-04
2026-10-03 04:08 UTCpass1daily-2026-10-03
2026-10-02 13:18 UTCpass1daily-2026-10-02
2026-10-01 06:33 UTCpass1daily-2026-10-01
2026-09-30 05:50 UTCpass1daily-2026-09-30
2026-09-29 18:11 UTCpass1daily-2026-09-29
2026-09-28 04:03 UTCpass1daily-2026-09-28
2026-09-25 19:46 UTCpass1daily-2026-09-25
2026-09-23 05:28 UTCpass1daily-2026-09-23
2026-09-22 05:37 UTCpass1daily-2026-09-22
2026-09-21 06:01 UTCpass1daily-2026-09-21
2026-09-20 18:40 UTCpass1daily-2026-09-20
2026-09-19 04:02 UTCpass1daily-2026-09-19
2026-09-18 08:57 UTCpass1daily-2026-09-18
2026-09-17 04:01 UTCpass1daily-2026-09-17
2026-09-16 04:02 UTCpass1daily-2026-09-16
2026-09-15 04:00 UTCpass1daily-2026-09-15
2026-09-14 03:59 UTCpass1daily-2026-09-14
2026-09-13 03:59 UTCpass1daily-2026-09-13
2026-09-12 06:14 UTCpass1daily-2026-09-12
2026-09-11 09:39 UTCpass1daily-2026-09-11

Registry presence

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

  1. 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": {
      "local_changes": [
        {
          "field": "temperature_setpoint",
          "value": 21.5,
          "version": 8
        },
        {
          "field": "mode",
          "value": "eco",
          "version": 4
        }
      ],
      "remote_changes": [
        {
          "field": "temperature_setpoint",
          "value": 22,
          "version": 7
        },
        {
          "field": "mode",
          "value": "comfort",
          "version": 4
        }
      ]
    },
    "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, "digital twin sync on iot.halowerk.com", snapshot of 2026-10-13 14:08 UTC. https://tollindex.com/e/iot-halowerk-com-v1-digital-twin-sync-131451/at/2026-10-13T14-08Z. Accessed [access date].

BibTeX

@misc{toll-e-iot-halowerk-com-v1-digital-twin-sync-131451-2026-10-13T14-08Z,
  author = {TOLL},
  title = {digital twin sync on iot.halowerk.com},
  howpublished = {\url{https://tollindex.com/e/iot-halowerk-com-v1-digital-twin-sync-131451/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 digital twin sync, 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 13145107ed6e7b12557f158e49926ba6ae5ff632650c92fd2d7cfc3749a6aa83 from wallet 0x2880EdfFF13100677Bf97A3CBdF3Bc34771C4E5E

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

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