Google Trends interest over time for one keyword: a dated 0-100 series for a country or…
Google Trends interest over time for one keyword: a dated 0-100 series for a country or worldwide, past 7 days to 5 years, in one $0.045 GET. Use when you need search-interest trends, seasonality or demand direction for a keyword. Daily points for short windo…
by keywords.duoleads.com · discovered, not yet claimed by its owner · updated 2026-10-13
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 one keyword: a dated 0-100 series for a country or worldwide, past 7 days to 5 years, in one $0.045 GET. Use when you need search-interest trends, seasonality or demand direction for a keyword. Daily points for short windows, weekly for 12 months. A live call takes up to about 30 s. Bad input is free; upstream errors are not charged.
Tags: google-trends · interest-over-time · keyword-research · search-trends · search-volume · bazaar
Call contract
- Method
- GET
- Input
- query parameters
- Output
- json
- Last paid call
- 2026-10-13
{
"country": "us",
"keyword": "seo tools",
"timeframe": "past_12_months"
}{
"country": "US",
"dataAsOf": "2026-10-11T19:24:11Z",
"granularity": "week",
"keyword": "seo tools",
"market": {
"country": "US",
"locationCode": 2840,
"locationName": "United States"
},
"queried_at": "2026-10-11T19:24:11Z",
"request_id": "01KEXAMPLE0000000000000000",
"see_also": {
"endpoint": "https://keywords.duoleads.com/v1/related-queries",
"params": [
"keyword",
"country",
"timeframe"
],
"reason": "Want the top and rising searches related to this keyword? Call related-queries with the same parameters."
},
"series": [
{
"date": "2025-10-05",
"value": 62
},
{
"date": "2025-10-12",
"value": 45
},
{
"date": "2025-10-19",
"value": 41
},
{
"date": "2026-10-11",
"partial": true,
"value": 11
}
],
"source": "Google Trends (via DataForSEO)",
"timeframe": "past_12_months",
"units": "value: Google Trends interest, 0-100 relative to the peak of the period (100 = peak, 0 = too little data); partial: the period is not complete yet"
}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/57607.jsonfor the price and payment options. - Pay. Call
GET https://keywords.duoleads.com/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.045 / request
- Protocol
- x402 v2
- Auth
- No account or API key. Pay per request.
- Networks
- Base
- Demand
- 1 calls · 1 unique payers in 30d (public x402 Bazaar data)
x402 payment requirements
| Scheme | Network | Asset | Amount | Pay to | Timeout |
|---|---|---|---|---|---|
| exact | Base eip155:8453 | USDC | $0.045 | 0xCD673f7e1daD254347AEab6be0DEFe8b9C6b3A39 | 120s |
accepts[] (raw JSON)
[
{
"scheme": "exact",
"network": "eip155:8453",
"payTo": "0xCD673f7e1daD254347AEab6be0DEFe8b9C6b3A39",
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"amount": "45000",
"amountUsd": 0.045,
"maxTimeoutSeconds": 120
}
]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://keywords.duoleads.com/v1/trend"
# -> 402 Payment Required, accepts[] lists how to pay
# retry with a PAYMENT-SIGNATURE (or PAYMENT header) once paidconst res = await fetch("https://keywords.duoleads.com/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://keywords.duoleads.com/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
- keywords.duoleads.com
- Endpoint
- https://keywords.duoleads.com/v1/trend
- Machine-readable
/resources/57607.json