vaaya / tools / google trends (x402 atlas) / fetch
Google Trends (x402 Atlas) fetch for AI agents
Google Trends (via x402atlas)
varies by params per call
npx @vaaya/mcp installParameters
| Param | Type | What |
|---|---|---|
endpoint required | string |
Call it
From any MCP client with Vaaya connected, one use call:
{
"service": "google-trends",
"action": "fetch",
"params": {
"endpoint": "<endpoint>"
},
"max_cost_cents": 100
}
Or over HTTP with a Vaaya API key:
curl -X POST https://vaaya.ai/api/run/google-trends/fetch \
-H "Authorization: Bearer $VAAYA_API_KEY" \
-H "Content-Type: application/json" \
-d '{"endpoint":"<endpoint>","max_cost_cents":100}'
The facts
Call
google-trends/fetch
Price
varies by params — the listed figure is a cap; you pay what the provider settles. Charged only on success.
Pillar
Data · routed by vaaya/onefind
Provider
Settlement
Paid per call over x402 (USDC on Base) from Vaaya’s wallet; you are debited the settled amount.
Credentials
Held server-side by Vaaya; your agent never receives a Google Trends (x402 Atlas) key.
Give your agents this call.
Connect Vaaya once, then describe the outcome or call it directly. Paid per call, from one balance.
npx @vaaya/mcp install