TOLL

What software pays for, recorded every six hours.

Snapshot
2026-10-13 14:08 UTC
Sweep
daily-2026-10-29 · finished 2026-10-29 12:42 UTC
Listed
32,435

data protocol fees derived

vape-x402.vapex402.workers.devMarket dataderived

GET https://vape-x402.vapex402.workers.dev/data/protocol_fees

faillisted in Coinbase#7 by calls of 15 on this host

0.01 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
fail
as of 2026-10-29 05:34 UTC · method · pinnable · sweep daily-2026-10-29
Uptime, 7 / 30 / 90 days
83% / 97% / 98%
as of 2026-10-29 05:34 UTC · method · pinnable · 5 of 6 in 7d, 28 of 29 in 30d, 42 of 43 in 90d
Calls, trailing 30 days
7
as of 2026-10-13 14:08 UTC · method · pinnable
Unique payers, trailing 30 days
3
as of 2026-10-13 14:08 UTC · method · pinnable
Last called
2026-10-07 04:03 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.01 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

116 observations, 13 of them a change

How has the volume on this endpoint moved?

-010710 Sep11 Sep12 Sep13 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

On 2026-10-29 it answered HTTP 500 rather than 402; TOLL records that as a failure.

vape-x402.vapex402.workers.dev serves data protocol fees, a GET endpoint that TOLL places in market data, listed in the Coinbase registry.

Per call, data protocol fees declares 0.01 USDC on Base.

data protocol fees takes the query parameter slug.

Its example response has the fields logo, name, slug, fees_24h and revenue_24h.

data protocol fees drew 7 calls from 3 unique payers in the trailing 30 days.

The last call to data protocol fees came 6 days before the snapshot, 2026-10-07.

data protocol fees is one of 15 listed endpoints on vape-x402.vapex402.workers.dev, tied 7th by calls with 4 others among them.

data protocol fees takes 6% of the calls counted across vape-x402.vapex402.workers.dev.

Among comparable prices in market data, data protocol fees sits above 40% of them.

Closest in price to data protocol fees within market data: address current balance at api.nansen.ai and token safety at api.deepnets.ai.

The wallet paid by data protocol fees is the payee of 18 endpoints on one host.

data protocol fees out-counts 86% of the 8,872 endpoints in market data that carry counters.

The seller's tags on data protocol fees are fees, revenue and protocol.

data protocol fees dropped out of the registry at the pull of 2026-09-13 and was listed again on 2026-09-15.

The price of data protocol fees is declared by 2,674 other listings in market data 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.01 USDCexact0x8aAB9a…0Cce15

Preflight checks at the last sweep

the checks, as of 2026-10-29 05:34 UTC · method · pinnableendpoint answered HTTP 500

  • returns_402 · an unauthenticated request gets HTTP 402

Validation history, 90 days

Every sweep that observed this endpoint, newest first.

Validation observations over the last 90 days
observed, UTCstatefailed checkssweep
2026-10-29 05:34 UTCfail1daily-2026-10-29
2026-10-28 05:57 UTCpass0daily-2026-10-28
2026-10-27 05:53 UTCpass0daily-2026-10-27
2026-10-26 05:49 UTCpass0daily-2026-10-26
2026-10-24 20:36 UTCpass0daily-2026-10-24
2026-10-23 05:43 UTCpass0daily-2026-10-23
2026-10-22 03:58 UTCpass0daily-2026-10-22
2026-10-21 07:23 UTCpass0daily-2026-10-21
2026-10-20 07:18 UTCpass0daily-2026-10-20
2026-10-19 05:25 UTCpass0daily-2026-10-19
2026-10-18 07:43 UTCpass0daily-2026-10-18
2026-10-17 17:40 UTCpass0daily-2026-10-17
2026-10-16 03:57 UTCpass0daily-2026-10-16
2026-10-15 05:30 UTCpass0daily-2026-10-15
2026-10-14 03:57 UTCpass0daily-2026-10-14
2026-10-13 08:19 UTCpass0daily-2026-10-13
2026-10-12 05:40 UTCpass0daily-2026-10-12
2026-10-11 03:59 UTCpass0daily-2026-10-11
2026-10-10 09:05 UTCpass0daily-2026-10-10
2026-10-09 04:00 UTCpass0daily-2026-10-09
2026-10-08 05:33 UTCpass0daily-2026-10-08
2026-10-07 04:04 UTCpass0daily-2026-10-07
2026-10-06 05:39 UTCpass0daily-2026-10-06
2026-10-05 05:19 UTCpass0daily-2026-10-05
2026-10-04 08:30 UTCpass0daily-2026-10-04
2026-10-03 03:54 UTCpass0daily-2026-10-03
2026-10-02 13:04 UTCpass0daily-2026-10-02
2026-10-01 06:20 UTCpass0daily-2026-10-01
2026-09-30 05:39 UTCpass0daily-2026-09-30
2026-09-29 17:59 UTCpass0daily-2026-09-29
2026-09-28 03:53 UTCpass0daily-2026-09-28
2026-09-25 19:35 UTCpass0daily-2026-09-25
2026-09-23 05:18 UTCpass0daily-2026-09-23
2026-09-22 05:27 UTCpass0daily-2026-09-22
2026-09-21 05:51 UTCpass0daily-2026-09-21
2026-09-20 18:30 UTCpass0daily-2026-09-20
2026-09-19 03:53 UTCpass0daily-2026-09-19
2026-09-18 08:44 UTCpass0daily-2026-09-18
2026-09-17 03:52 UTCpass0daily-2026-09-17
2026-09-16 03:52 UTCpass0daily-2026-09-16
2026-09-13 03:51 UTCpass0daily-2026-09-13
2026-09-12 06:06 UTCpass0daily-2026-09-12
2026-09-11 09:30 UTCpass0daily-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-07 04:03 UTC · method · live

The input and output block
{
  "input": {
    "type": "http",
    "method": "GET",
    "queryParams": {
      "slug": "aave"
    }
  },
  "output": {
    "type": "json",
    "example": {
      "logo": "https://...",
      "name": "AAVE",
      "slug": "aave",
      "fees_24h": 500000,
      "revenue_24h": 90000
    }
  }
}
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, "data protocol fees on vape-x402.vapex402.workers.dev", snapshot of 2026-10-13 14:08 UTC. https://tollindex.com/e/vape-x402-vapex402-workers-dev-data-protocol-fees-06a551/at/2026-10-13T14-08Z. Accessed [access date].

BibTeX

@misc{toll-e-vape-x402-vapex402-workers-dev-data-protocol-fees-06a551-2026-10-13T14-08Z,
  author = {TOLL},
  title = {data protocol fees on vape-x402.vapex402.workers.dev},
  howpublished = {\url{https://tollindex.com/e/vape-x402-vapex402-workers-dev-data-protocol-fees-06a551/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 data protocol fees, 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 06a5515f7212b65da45c4f8a9a1704a93ead10c11993ec4a829867b8e640ab28 from wallet 0x8aAB9a6d28e9AbA2a15a613C90F24f352f0Cce15

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

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