Google Trends interest over time for a keyword
Google Trends interest over time for a keyword. Returns Google Trends search interest as a dated series indexed 0-100: weekly points across the default past 12 months, daily points for 30- and 90-day windows, and windows from the past hour back to 2004, with…
by api.kadec0.xyz · discovered, not yet claimed by its owner · updated 2026-10-12
Mirrored from Coinbase's public x402 Bazaar. The description is the provider's own text and has not been reviewed here; the payment requirements are copied as published.
What it does
Google Trends interest over time for a keyword. Returns Google Trends search interest as a dated series indexed 0-100: weekly points across the default past 12 months, daily points for 30- and 90-day windows, and windows from the past hour back to 2004, with optional country targeting. For keyword trend analysis, search demand seasonality, and SEO keyword research.
Tags: google-trends · trends · keyword-research · seo · search-volume · bazaar
Call contract
- Method
- GET
- Input
- query parameters
- Output
- json
- Last paid call
- 2026-10-12
{
"geo": "US",
"keyword": "bitcoin"
}{
"count": 1,
"items": [
{
"dataSource": "primary",
"geo": "US",
"granularity": "week",
"keyword": "bitcoin",
"points": 53,
"queriedAt": "2026-09-02T19:38:34Z",
"series": [
{
"date": "2025-08-31",
"dateTo": "2025-09-06",
"partial": false,
"value": 26
},
{
"date": "2026-08-30",
"dateTo": "2026-09-02",
"partial": true,
"value": 21
}
],
"stale": false,
"timeframe": "past_12_months",
"type": "google_trend"
}
]
}Use with an agent
- Discover. Agents find this listing with
GET https://bazaar.saylorinnovations.com/discovery/search?query=…, the MCP toolsearch_resources, or/discovery/resources. - Inspect. Fetch
/resources/26293.jsonfor the price and payment options. - Pay. Call
GET https://api.kadec0.xyz/v1/trend. The provider answers402with its payment requirements. An x402 client signs one of the options below and retries withPAYMENT-SIGNATURE. - Execute. The provider returns
200with the data. Agent Bazaar is not in the request path and never sees your payment.
For humans
You don't need an account or an API key; you need a wallet holding a small amount of USDC on Base, and an x402-capable client (see the examples below). Call the endpoint unpaid first to see exactly what it asks for.
Pricing & payment
- Price
- $0.05 / request
- Protocol
- x402 v2
- Auth
- No account or API key. Pay per request.
- Networks
- Base
- Demand
- 425 calls · 3 unique payers in 30d (public x402 Bazaar data)
x402 payment requirements
| Scheme | Network | Asset | Amount | Pay to | Timeout |
|---|---|---|---|---|---|
| exact | Base eip155:8453 | USDC | $0.05 | 0x4df66B6c140778fe0717880A7c6dDE5Ea53AcDeA | 300s |
accepts[] (raw JSON)
[
{
"scheme": "exact",
"network": "eip155:8453",
"payTo": "0x4df66B6c140778fe0717880A7c6dDE5Ea53AcDeA",
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"amount": "50000",
"amountUsd": 0.05,
"maxTimeoutSeconds": 300
}
]Schemas
Output schema (JSON Schema)
{
"properties": {
"example": {
"type": "object"
},
"type": {
"type": "string"
}
},
"required": [
"type"
],
"type": "object"
}Example shape — generated from the schema, not a captured live response
{
"example": {},
"type": "string"
}Examples
curl "https://api.kadec0.xyz/v1/trend"
# -> 402 Payment Required, accepts[] lists how to pay
# retry with a PAYMENT-SIGNATURE (or PAYMENT header) once paidconst res = await fetch("https://api.kadec0.xyz/v1/trend");
if (res.status === 402) {
const { accepts } = await res.json();
// pay one of accepts[] via an x402 client, then retry with the payment header
}import httpx
res = httpx.get("https://api.kadec0.xyz/v1/trend")
if res.status_code == 402:
accepts = res.json()["accepts"]
# pay one of accepts[] via an x402 client, then retry with the payment headerDetails
- Provider
- api.kadec0.xyz
- Endpoint
- https://api.kadec0.xyz/v1/trend
- Machine-readable
/resources/26293.json