80trust / 100

Related Topics

by Google Trends SEO Keyword Data in Markets & finance

x402 APIPassing, checked 4 h ago

Google Trends related topics for a keyword by country — top & rising topics for SEO content research, trend discovery and market analysis.

GET
https://google-trends.use.x402atlas.com/related-topics
Price
$0.03
per call in USDC
Uptime
100%
last 30 days
Response time
445 ms
700 ms slowest 5%
Last check
Passed
4 h ago, next any minute now

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed · Watch with other listings

How to call it

GET https://google-trends.use.x402atlas.com/related-topics

Each call costs $0.03 in USDC on Base, paid with the request over x402.

Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.

Example request

From the listing.

GET https://google-trends.use.x402atlas.com/related-topics?country=us&keyword=bitcoin

Parameters

ParameterTypeRequiredDescription
countrystringNoISO-3166 alpha-2 country code, e.g. US, GB, DE, JP (213 countries supported); case-insensitive; defaults to US Default: "US".
keywordstringYesConcise Google Trends seed term with meaningful search interest; not a question, instruction, or web-search request

Example response

The provider's example. We can't check it without paying.

{
  "country": "us",
  "keyword": "bitcoin",
  "queried_at": "2026-06-05T12:00:00Z",
  "rising": [
    {
      "term": "Spot ETF",
      "value": 180
    }
  ],
  "top": [
    {
      "term": "Cryptocurrency",
      "value": 100
    }
  ]
}

Call it from code

The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.03.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://google-trends.use.x402atlas.com/related-topics?country=us&keyword=bitcoin'

# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - 'https://google-trends.use.x402atlas.com/related-topics?country=us&keyword=bitcoin' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

// Pays at most $0.03 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.03" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);

// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.03 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fgoogle-trends.use.x402atlas.com%2Frelated-topics
const res = await pay("https://google-trends.use.x402atlas.com/related-topics?country=us&keyword=bitcoin");
console.log(res.status, await res.text());
Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client

# Pays at most $0.03 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.03"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.get("https://google-trends.use.x402atlas.com/related-topics?country=us&keyword=bitcoin")
    print(res.status_code, res.text)

Security scan

No findings

We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTimePrice
4 h agoPassed402527 ms$0.03
8 h agoPassed402445 ms$0.03
12 h agoPassed402396 ms$0.03
16 h agoPassed402538 ms$0.03
21 h agoPassed402400 ms$0.03
Show 10 older checks
25 h agoPassed402454 ms$0.03
29 h agoPassed402456 ms$0.03
33 h agoPassed402496 ms$0.03
37 h agoPassed402427 ms$0.03
41 h agoPassed402425 ms$0.03
45 h agoPassed402458 ms$0.03
2 days agoPassed402528 ms$0.03
2 days agoPassed402545 ms$0.03
2 days agoPassed402471 ms$0.03
3 days agoPassed402489 ms$0.03