TOLL

What software pays for, recorded every six hours.

Snapshot
2026-11-01 13:19 UTC
Sweep
daily-2026-10-30 · finished 2026-10-30 13:00 UTC
Listed
29,006

fleet anomaly derived

iot.halowerk.comOtherderived

POST https://iot.halowerk.com/v1/fleet-anomaly

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

0.003 USDC

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

Compare with anotherEvery figure as JSONCite this page

the price, as of 2026-11-01 13:19 UTC · method · pinnable

Validation state
pass
as of 2026-10-30 08:09 UTC · method · pinnable · sweep daily-2026-10-30
Uptime, 7 / 30 / 90 days
100% / 100% / 100%
as of 2026-10-30 08:09 UTC · method · pinnable · 5 of 5 in 7d, 22 of 22 in 30d, 39 of 39 in 90d
Calls, trailing 30 days
14
as of 2026-11-01 13:19 UTC · method · pinnable
Unique payers, trailing 30 days
8
as of 2026-11-01 13:19 UTC · method · pinnable
Last called
2026-11-01 07:51 UTC
as of 2026-11-01 13:19 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.003 USDC
as of 2026-11-01 13:19 UTC · method · pinnable · on eip155:8453
Networks
1
as of 2026-11-01 13:19 UTC · method · pinnable

Counters

107 observations, 4 of them a change

How has the volume on this endpoint moved?

-0101410 Sep11 Sep12 Sep13 Sep14 Sep15 Sep16 Sep17 Sep18 Sep19 Sep20 Sep21 Sep22 Sep23 Sep24 Sep25 Sep26 Sep27 Sep28 Sep29 Sep30 Sep1 Oct7 Oct8 Oct9 Oct10 Oct11 Oct12 Oct13 Oct1 Nov
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

fleet anomaly, a POST endpoint on iot.halowerk.com, appears in the Coinbase registry; TOLL's taxonomy puts it in the "other" category.

fleet anomaly is priced at 0.003 USDC on Base.

Requests carry a json body with the fields readings and threshold.

fleet anomaly returns json; the example shows mad, median, method, scores, threshold, flagged_devices and 1 other.

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

fleet anomaly shares iot.halowerk.com with 9 other listed endpoints and is tied 2nd by calls with 1 other.

fleet anomaly takes 11% of the calls counted across iot.halowerk.com.

The registry's counters give fleet anomaly 14 calls and 8 unique payers over 30 days.

fleet anomaly was last called on the day of the snapshot.

Closest in price to fleet anomaly within the "other" category: calendar business days at kaisha-api.hp-vladic.workers.dev and vat at toolvend.dev.

fleet anomaly is priced above 28% of comparable listings in the "other" category.

fleet anomaly out-counts 95% of the 4,399 endpoints in the "other" category that carry counters.

The wallet paid by fleet anomaly is the payee of 2,245 endpoints across 100 hosts.

The seller's tags on fleet anomaly are iot, fleet and anomaly.

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

The price of fleet anomaly is declared by 272 other listings in the "other" category too.

Payment options as declared

the payment options, as of 2026-11-01 13:19 UTC · method · pinnable

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

Preflight checks at the last sweep

the checks, as of 2026-10-30 08:09 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 08:09 UTCpass0daily-2026-10-30
2026-10-29 07:50 UTCpass0daily-2026-10-29
2026-10-28 08:12 UTCpass0daily-2026-10-28
2026-10-27 08:00 UTCpass0daily-2026-10-27
2026-10-26 13:18 UTCpass0daily-2026-10-26
2026-10-23 08:02 UTCpass1daily-2026-10-23
2026-10-22 06:19 UTCpass1daily-2026-10-22
2026-10-21 10:38 UTCpass1daily-2026-10-21
2026-10-20 10:13 UTCpass1daily-2026-10-20
2026-10-19 07:47 UTCpass1daily-2026-10-19
2026-10-18 09:52 UTCpass1daily-2026-10-18
2026-10-17 20:00 UTCpass1daily-2026-10-17
2026-10-16 06:03 UTCpass1daily-2026-10-16
2026-10-15 07:45 UTCpass1daily-2026-10-15
2026-10-14 05:54 UTCpass1daily-2026-10-14
2026-10-13 10:34 UTCpass1daily-2026-10-13
2026-10-12 07:55 UTCpass1daily-2026-10-12
2026-10-11 06:30 UTCpass1daily-2026-10-11
2026-10-10 14:38 UTCpass1daily-2026-10-10
2026-10-09 07:06 UTCpass1daily-2026-10-09
2026-10-08 08:35 UTCpass1daily-2026-10-08
2026-10-07 07:51 UTCpass1daily-2026-10-07
2026-10-01 07:34 UTCpass1daily-2026-10-01
2026-09-30 06:52 UTCpass1daily-2026-09-30
2026-09-29 19:11 UTCpass1daily-2026-09-29
2026-09-28 05:58 UTCpass1daily-2026-09-28
2026-09-25 20:43 UTCpass1daily-2026-09-25
2026-09-23 06:19 UTCpass1daily-2026-09-23
2026-09-22 06:30 UTCpass1daily-2026-09-22
2026-09-21 06:52 UTCpass1daily-2026-09-21
2026-09-19 04:54 UTCpass1daily-2026-09-19
2026-09-18 10:55 UTCpass1daily-2026-09-18
2026-09-17 04:49 UTCpass1daily-2026-09-17
2026-09-16 04:51 UTCpass1daily-2026-09-16
2026-09-15 04:47 UTCpass1daily-2026-09-15
2026-09-14 04:42 UTCpass1daily-2026-09-14
2026-09-13 04:40 UTCpass1daily-2026-09-13
2026-09-12 06:57 UTCpass1daily-2026-09-12
2026-09-11 10:33 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-11-01 07:51 UTC · method · live

The input and output block
{
  "input": {
    "body": {
      "readings": [
        {
          "value": 10.1,
          "device_id": "pump-1"
        },
        {
          "value": 9.9,
          "device_id": "pump-2"
        },
        {
          "value": 10.2,
          "device_id": "pump-3"
        },
        {
          "value": 18.5,
          "device_id": "pump-4"
        }
      ],
      "threshold": 3.5
    },
    "type": "http",
    "method": "POST",
    "bodyType": "json"
  },
  "output": {
    "type": "json",
    "example": {
      "mad": 0.15,
      "median": 10.15,
      "method": "median absolute deviation robust z-score",
      "scores": [
        {
          "value": 10.1,
          "flagged": false,
          "robust_z": -0.22483,
          "device_id": "pump-1",
          "direction": "low"
        },
        {
          "value": 9.9,
          "flagged": false,
          "robust_z": -1.12415,
          "device_id": "pump-2",
          "direction": "low"
        },
        {
          "value": 10.2,
          "flagged": false,
          "robust_z": 0.22483,
          "device_id": "pump-3",
          "direction": "high"
        },
        {
          "value": 18.5,
          "flagged": true,
          "robust_z": 37.546596,
          "device_id": "pump-4",
          "direction": "high"
        }
      ],
      "threshold": 3.5,
      "flagged_devices": [
        "pump-4"
      ],
      "zero_mad_policy": "not_applied"
    }
  }
}
Cite this page

The pinned URL below renders this page from the snapshot of 2026-11-01 13:19 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).

Plain text

TOLL, "fleet anomaly on iot.halowerk.com", snapshot of 2026-11-01 13:19 UTC. https://tollindex.com/e/iot-halowerk-com-v1-fleet-anomaly-554ab5/at/2026-11-01T13-19Z. Accessed [access date].

BibTeX

@misc{toll-e-iot-halowerk-com-v1-fleet-anomaly-554ab5-2026-11-01T13-19Z,
  author = {TOLL},
  title = {fleet anomaly on iot.halowerk.com},
  howpublished = {\url{https://tollindex.com/e/iot-halowerk-com-v1-fleet-anomaly-554ab5/at/2026-11-01T13-19Z}},
  year = {2026},
  month = {11},
  note = {Pinned view of the snapshot of 2026-11-01 13:19 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 fleet anomaly, 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 554ab581ed8c89b7cbc10934127314ed766f62d923db0c63bc4aaa9e4947684c from wallet 0x2880EdfFF13100677Bf97A3CBdF3Bc34771C4E5E

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

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