Related keywords API - expand a seed keyword using Google's "searches related to" graph…
Related keywords API - expand a seed keyword using Google's "searches related to" graph, returning the related keywords (traversed to a configurable depth) each with monthly search volume, CPC, competition, keyword difficulty and search intent, plus the furth…
by seo.openverbs.com · 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
Related keywords API - expand a seed keyword using Google's "searches related to" graph, returning the related keywords (traversed to a configurable depth) each with monthly search volume, CPC, competition, keyword difficulty and search intent, plus the further related terms branching off each. For content-cluster planning and keyword discovery. No matches returns empty results.
Tags: related keywords api · keyword expansion api · searches related to · serp related searches · keyword research api · bazaar
Call contract
- Method
- POST
- Input
- json
- Output
- json
- Last paid call
- 2026-10-12
{
"depth": 1,
"keyword": "example",
"limit": 1
}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/31057.jsonfor the price and payment options. - Pay. Call
GET https://seo.openverbs.com/v1/related-keywords. 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.04 / request
- Protocol
- x402 v2
- Auth
- No account or API key. Pay per request.
- Networks
- Base
- Demand
- 4 calls · 4 unique payers in 30d (public x402 Bazaar data)
x402 payment requirements
| Scheme | Network | Asset | Amount | Pay to | Timeout |
|---|---|---|---|---|---|
| exact | Base eip155:8453 | USDC | $0.04 | 0xb3f4de103F34b99f0Da19B4F16D6B53a14C2194A | 300s |
accepts[] (raw JSON)
[
{
"scheme": "exact",
"network": "eip155:8453",
"payTo": "0xb3f4de103F34b99f0Da19B4F16D6B53a14C2194A",
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"amount": "40000",
"amountUsd": 0.04,
"maxTimeoutSeconds": 300
}
]Examples
curl "https://seo.openverbs.com/v1/related-keywords"
# -> 402 Payment Required, accepts[] lists how to pay
# retry with a PAYMENT-SIGNATURE (or PAYMENT header) once paidconst res = await fetch("https://seo.openverbs.com/v1/related-keywords");
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://seo.openverbs.com/v1/related-keywords")
if res.status_code == 402:
accepts = res.json()["accepts"]
# pay one of accepts[] via an x402 client, then retry with the payment headerDetails
- Provider
- seo.openverbs.com
- Endpoint
- https://seo.openverbs.com/v1/related-keywords
- Machine-readable
/resources/31057.json