google trends fetch derived
vaaya.aiMarket dataderived
POST https://vaaya.ai/api/run/google-trends/fetch
passlisted in Coinbase#47 by calls of 82 on this host
0.05 USDC
per call, as the listing declares it on eip155:
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- 100% / 100% / 93%
- Calls, trailing 30 days
- 2
- Unique payers, trailing 30 days
- 2
- Last called
- 2026-10-06 22:03 UTC
- First observed by TOLLderived
- 2026-09-24
- Pricederived
- 0.05 USDC
- Networks
- 1
How big is this endpoint among the ones like it?
No trace is drawn of this endpoint’s own volume. Its counters have changed 2 times across 61 observations, and 3 changes are the fewest this site will draw a trace through, because two points and a guess are not a series. Every observation is in the JSON.
Among the 82 endpoints on vaaya.ai, google trends fetch is tied 47th by calls with 16 others.
The request to google trends fetch is a json body with the field endpoint.
google trends fetch returns json; the example shows ok, data and charged_cents.
The registry's counters give google trends fetch 2 calls and 2 unique payers over 30 days, every call from a different payer.
google trends fetch was last called 7 days before the snapshot.
The declared price is 0.05 USDC on Base.
google trends fetch is a POST endpoint at vaaya.ai, listed in the Coinbase registry and filed by TOLL under market data.
google trends fetch answered the sweep of 2026-10-28 with a valid 402, passing 28 of 30 sweeps since 2026-09-25.
Closest in price to google trends fetch within market data: smart money netflow at api.nansen.ai and analyze at svm402.com.
google trends fetch is priced above 86% of comparable listings in market data.
The wallet paid by google trends fetch is the payee of 102 endpoints on one host.
Seller tags: google-trends, ai-agents and pay-per-call.
The price of google trends fetch is declared by 581 other listings in market data too.
the payment options, as of 2026-10-13 14:08 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.05 USDC | exact | 0x7c655d…806C40 |
the checks, as of 2026-10-28 09:17 UTC · method · pinnableendpoint answered HTTP 402
No named check failed.
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-10-28 09:17 UTC | pass | 0 | daily-2026-10-28 |
| 2026-10-27 09:01 UTC | pass | 0 | daily-2026-10-27 |
| 2026-10-26 15:30 UTC | pass | 0 | daily-2026-10-26 |
| 2026-10-23 09:12 UTC | pass | 0 | daily-2026-10-23 |
| 2026-10-21 11:44 UTC | pass | 0 | daily-2026-10-21 |
| 2026-10-20 11:19 UTC | pass | 0 | daily-2026-10-20 |
| 2026-10-19 08:57 UTC | pass | 0 | daily-2026-10-19 |
| 2026-10-18 10:52 UTC | pass | 0 | daily-2026-10-18 |
| 2026-10-17 21:15 UTC | pass | 0 | daily-2026-10-17 |
| 2026-10-16 07:03 UTC | pass | 0 | daily-2026-10-16 |
| 2026-10-15 08:50 UTC | pass | 0 | daily-2026-10-15 |
| 2026-10-14 06:53 UTC | pass | 0 | daily-2026-10-14 |
| 2026-10-13 11:37 UTC | pass | 0 | daily-2026-10-13 |
| 2026-10-12 08:58 UTC | pass | 0 | daily-2026-10-12 |
| 2026-10-11 07:42 UTC | pass | 0 | daily-2026-10-11 |
| 2026-10-10 15:48 UTC | pass | 0 | daily-2026-10-10 |
| 2026-10-09 08:29 UTC | pass | 0 | daily-2026-10-09 |
| 2026-10-08 09:58 UTC | pass | 0 | daily-2026-10-08 |
| 2026-10-07 09:19 UTC | pass | 0 | daily-2026-10-07 |
| 2026-10-06 10:09 UTC | pass | 0 | daily-2026-10-06 |
| 2026-10-05 09:04 UTC | pass | 0 | daily-2026-10-05 |
| 2026-10-04 11:23 UTC | pass | 0 | daily-2026-10-04 |
| 2026-10-03 06:05 UTC | pass | 0 | daily-2026-10-03 |
| 2026-10-02 15:18 UTC | pass | 0 | daily-2026-10-02 |
| 2026-10-01 08:09 UTC | pass | 0 | daily-2026-10-01 |
| 2026-09-30 07:30 UTC | pass | 0 | daily-2026-09-30 |
| 2026-09-29 19:45 UTC | pass | 0 | daily-2026-09-29 |
| 2026-09-28 07:11 UTC | pass | 0 | daily-2026-09-28 |
| 2026-09-25 21:15 UTC | malformed | 1 | daily-2026-09-25 |
| 2026-09-25 19:21 UTC | malformed | 1 | new-after-daily-2026-09-24 |
Presence in a registry, not liveness of the service (method). Newest first.
- listed in Coinbase
From the registry record, not validated by TOLL.the declared schema, as of 2026-10-06 22:03 UTC · method · live
The input and output block
{
"input": {
"body": {
"endpoint": "/trend"
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"ok": true,
"data": {},
"charged_cents": 5
}
}
}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, "google trends fetch on vaaya.ai", snapshot of 2026-10-13 14:08 UTC. https://tollindex.com/e/vaaya-ai-api-run-google-trends-fetch-7b138c/at/2026-10-13T14-08Z. Accessed [access date].
BibTeX
@misc{toll-e-vaaya-ai-api-run-google-trends-fetch-7b138c-2026-10-13T14-08Z,
author = {TOLL},
title = {google trends fetch on vaaya.ai},
howpublished = {\url{https://tollindex.com/e/vaaya-ai-api-run-google-trends-fetch-7b138c/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].}
}None yet. Anything submitted through the form below is published here with its outcome.