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

debris collision derived

space.halowerk.comOtherderived

POST https://space.halowerk.com/v1/debris-collision

passlisted in Coinbase#2 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-11-01 13:19 UTC · method · pinnable

Validation state
pass
as of 2026-10-30 11:12 UTC · method · pinnable · sweep daily-2026-10-30
Uptime, 7 / 30 / 90 days
100% / 100% / 100%
as of 2026-10-30 11:12 UTC · method · pinnable · 4 of 4 in 7d, 23 of 23 in 30d, 37 of 37 in 90d
Calls, trailing 30 days
3
as of 2026-11-01 13:19 UTC · method · pinnable
Unique payers, trailing 30 days
3
as of 2026-11-01 13:19 UTC · method · pinnable
Last called
2026-10-08 06:13 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.004 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

124 observations, 7 of them a change

How has the volume on this endpoint moved?

1234310 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 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

TOLL files debris collision under the "other" category: a POST endpoint on space.halowerk.com, listed in the Coinbase registry.

Per call, debris collision declares 0.004 USDC on Base.

debris collision takes a json body with the fields horizon_seconds, primary_radius_m, secondary_radius_m, primary_position_km, primary_velocity_km_s, secondary_position_km and 1 other.

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

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

debris collision is one of 10 listed endpoints on space.halowerk.com, tied 2nd by calls with 3 others among them.

debris collision takes 12% of the calls counted across space.halowerk.com.

The registry's counters give debris collision 3 calls and 3 unique payers over 30 days, every call from a different payer.

debris collision was last called 24 days before the snapshot.

Closest in price to debris collision within the "other" category: fetch at nanoparse.app and aviation airport status at api.x402node.dev.

debris collision is priced above 34% of comparable listings in the "other" category.

debris collision out-counts 60% of the 4,399 endpoints in the "other" category that carry counters.

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

The price of debris collision is declared by 136 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.004 USDCexact0x2880Ed…1C4E5E

Preflight checks at the last sweep

the checks, as of 2026-10-30 11:12 UTC · method · pinnableendpoint answered HTTP 402

  • bazaar.info.output · advisory, does not affect the verdict · output metadata is present (advisory)

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 11:12 UTCpass1daily-2026-10-30
2026-10-29 10:48 UTCpass1daily-2026-10-29
2026-10-28 11:12 UTCpass1daily-2026-10-28
2026-10-27 10:50 UTCpass1daily-2026-10-27
2026-10-23 11:16 UTCpass1daily-2026-10-23
2026-10-21 20:32 UTCpass1daily-2026-10-21
2026-10-19 11:02 UTCpass1daily-2026-10-19
2026-10-18 19:07 UTCpass1daily-2026-10-18
2026-10-16 08:51 UTCpass1daily-2026-10-16
2026-10-15 10:48 UTCpass1daily-2026-10-15
2026-10-14 08:38 UTCpass1daily-2026-10-14
2026-10-13 13:31 UTCpass1daily-2026-10-13
2026-10-12 10:55 UTCpass1daily-2026-10-12
2026-10-11 09:37 UTCpass1daily-2026-10-11
2026-10-10 17:46 UTCpass1daily-2026-10-10
2026-10-09 10:59 UTCpass1daily-2026-10-09
2026-10-08 12:34 UTCpass1daily-2026-10-08
2026-10-07 11:48 UTCpass1daily-2026-10-07
2026-10-06 12:30 UTCpass1daily-2026-10-06
2026-10-05 11:06 UTCpass1daily-2026-10-05
2026-10-04 13:51 UTCpass1daily-2026-10-04
2026-10-03 07:18 UTCpass1daily-2026-10-03
2026-10-02 16:26 UTCpass1daily-2026-10-02
2026-10-01 09:11 UTCpass1daily-2026-10-01
2026-09-30 08:38 UTCpass1daily-2026-09-30
2026-09-29 20:45 UTCpass1daily-2026-09-29
2026-09-23 07:41 UTCpass1daily-2026-09-23
2026-09-22 07:55 UTCpass1daily-2026-09-22
2026-09-21 08:17 UTCpass1daily-2026-09-21
2026-09-19 06:16 UTCpass1daily-2026-09-19
2026-09-17 06:07 UTCpass1daily-2026-09-17
2026-09-16 06:06 UTCpass1daily-2026-09-16
2026-09-15 06:22 UTCpass1daily-2026-09-15
2026-09-14 05:52 UTCpass1daily-2026-09-14
2026-09-13 05:45 UTCpass1daily-2026-09-13
2026-09-12 08:02 UTCpass1daily-2026-09-12
2026-09-11 11:59 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:13 UTC · method · live

The input and output block
{
  "input": {
    "body": {
      "horizon_seconds": 1800,
      "primary_radius_m": 5,
      "secondary_radius_m": 2,
      "primary_position_km": {
        "x": 7000,
        "y": 0,
        "z": 0
      },
      "primary_velocity_km_s": {
        "x": 0,
        "y": 7.5,
        "z": 0
      },
      "secondary_position_km": {
        "x": 7000.08,
        "y": -1.2,
        "z": 0.03
      },
      "secondary_velocity_km_s": {
        "x": -0.0001,
        "y": 7.501,
        "z": 0
      }
    },
    "type": "http",
    "method": "POST",
    "bodyType": "json"
  },
  "output": null
}
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, "debris collision on space.halowerk.com", snapshot of 2026-11-01 13:19 UTC. https://tollindex.com/e/space-halowerk-com-v1-debris-collision-bccdc6/at/2026-11-01T13-19Z. Accessed [access date].

BibTeX

@misc{toll-e-space-halowerk-com-v1-debris-collision-bccdc6-2026-11-01T13-19Z,
  author = {TOLL},
  title = {debris collision on space.halowerk.com},
  howpublished = {\url{https://tollindex.com/e/space-halowerk-com-v1-debris-collision-bccdc6/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 debris collision, 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 bccdc6f69b1bef701f6242d55eeeb430974e8d68d69572325d72e8916ed5a4f1 from wallet 0x2880EdfFF13100677Bf97A3CBdF3Bc34771C4E5E

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

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