TOLL

What software pays for, recorded every six hours.

Snapshot
2026-09-15 21:20 UTC
Sweep
daily-2026-09-15 · finished 2026-09-15 07:10 UTC
Listed
16,178

tikhub fetch derived

vaaya.aiMarket dataderived

POST https://vaaya.ai/api/run/tikhub/fetch

malformedlisted in Coinbase#2 by calls of 66 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-09-15 21:20 UTC · method · pinnable

Validation state
malformed
as of 2026-09-15 06:34 UTC · method · pinnable · sweep daily-2026-09-15
Uptime, 7 / 30 / 90 days
0% / 0% / 0%
as of 2026-09-15 06:34 UTC · method · pinnable · 0 of 5 in 7d, 0 of 5 in 30d, 0 of 5 in 90d
Calls, trailing 30 days
122
as of 2026-09-15 21:20 UTC · method · pinnable
Unique payers, trailing 30 days
7
as of 2026-09-15 21:20 UTC · method · pinnable
Last called
2026-09-15 16:57 UTC
as of 2026-09-15 21:20 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-09-15 21:20 UTC · method · pinnable · on eip155:8453
Networks
1
as of 2026-09-15 21:20 UTC · method · pinnable

Counters

29 observations, 5 of them a change

How has the volume on this endpoint moved?

12013012210 Sep11 Sep12 Sep13 Sep14 Sep15 Sep
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

tikhub fetch answered the sweep of 2026-09-15 with a 402 that failed the required check bazaar.routeTemplate.matches_resource.

For tikhub fetch the failing check asks whether the declared route template matches the resource path.

tikhub fetch, a POST endpoint on vaaya.ai, appears in the Coinbase registry; TOLL's taxonomy puts it in market data.

On Base, tikhub fetch asks 0.01 USDC per call.

Callers of tikhub fetch supply a json body with the field endpoint.

Its example response has the fields ok, data and charged_cents.

tikhub fetch drew 122 calls from 7 unique payers in the trailing 30 days, about 17 calls per payer.

tikhub fetch was last called on the day of the snapshot.

Among the 66 endpoints on vaaya.ai, tikhub fetch is 2nd by calls.

It accounts for 14% of the calls counted across the host.

tikhub fetch is priced above 37% of comparable listings in market data.

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

The wallet paid by tikhub fetch is the payee of 69 endpoints on one host.

tikhub fetch out-counts 98% of the 5,288 endpoints in market data that carry counters.

Seller tags: tikhub, ai-agents and pay-per-call.

The price of tikhub fetch is declared by 1,313 other listings in market data too.

Payment options as declared

the payment options, as of 2026-09-15 21:20 UTC · method · pinnable

Every payment option declared on this listing
registrynetworkassetamountschemepay to
Coinbaseeip155:8453USDC0.01 USDCexact0x7c655d…806C40

Preflight checks at the last sweep

the checks, as of 2026-09-15 06:34 UTC · method · pinnableendpoint answered HTTP 402

  • bazaar.routeTemplate.matches_resource · the declared route template matches the resource path

Validation history, 90 days

Every sweep that observed this endpoint, newest first.

Validation observations over the last 90 days
observed, UTCstatefailed checkssweep
2026-09-15 06:34 UTCmalformed1daily-2026-09-15
2026-09-14 06:03 UTCmalformed1daily-2026-09-14
2026-09-13 05:55 UTCmalformed1daily-2026-09-13
2026-09-12 08:12 UTCmalformed1daily-2026-09-12
2026-09-11 12:19 UTCmalformed1daily-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-09-15 16:57 UTC · method · live

The input and output block
{
  "input": {
    "body": {
      "endpoint": "/api/v1/bilibili/app/fetch_bangumi_tab"
    },
    "type": "http",
    "method": "POST",
    "bodyType": "json",
    "pathParams": {}
  },
  "output": {
    "type": "json",
    "example": {
      "ok": true,
      "data": {},
      "charged_cents": 1
    }
  }
}
Cite this page

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

Plain text

TOLL, "tikhub fetch on vaaya.ai", snapshot of 2026-09-15 21:20 UTC. https://tollindex.com/e/vaaya-ai-api-run-tikhub-fetch-cd4a59/at/2026-09-15T21-20Z. Accessed [access date].

BibTeX

@misc{toll-e-vaaya-ai-api-run-tikhub-fetch-cd4a59-2026-09-15T21-20Z,
  author = {TOLL},
  title = {tikhub fetch on vaaya.ai},
  howpublished = {\url{https://tollindex.com/e/vaaya-ai-api-run-tikhub-fetch-cd4a59/at/2026-09-15T21-20Z}},
  year = {2026},
  month = {9},
  note = {Pinned view of the snapshot of 2026-09-15 21:20 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 tikhub fetch, 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 cd4a59cb8b0de9b20467166fc06ac8a242ac91c2a8f863e805f0c0583c5a84e5 from wallet 0x7c655d3d3944Bd27994dD81A036C3aFB19806C40

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

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