79trust / 100

Related Keywords

by seo.openverbs.com in Search & web

x402 APIPassing, checked 1 h ago

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.

POST https://seo.openverbs.com/v1/related-keywords

Last 30 days

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed

Uptime
100%
Response time
560 ms typical, 620 ms slowest 5%
Last check
1 h ago
Next check
any minute now

How to call it

POST https://seo.openverbs.com/v1/related-keywords

Each call costs $0.04 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.

POST https://seo.openverbs.com/v1/related-keywords
content-type: application/json

{
  "depth": 1,
  "keyword": "example",
  "limit": 1
}

Parameters

ParameterTypeRequiredDescription
depthintegerNoHow many levels of the related-searches graph to traverse (0-4). Defaults to 1.
keywordstringYesSeed keyword to expand.
languageCodestringNoLanguage code (2-letter). Defaults to en.
limitintegerNoMaximum keywords to return. Defaults to 20.
locationCodeintegerNoDataForSEO location code. Defaults to 2840 (United States).

Example response

The listing has no example response.

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.04.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://seo.openverbs.com/v1/related-keywords' \
  -H 'content-type: application/json' \
  --data-raw '{"depth":1,"keyword":"example","limit":1}'

# 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 - -X POST 'https://seo.openverbs.com/v1/related-keywords' \
  -H 'content-type: application/json' \
  --data-raw '{"depth":1,"keyword":"example","limit":1}' \
  | 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.04 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.04" });
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.04 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fseo.openverbs.com%2Fv1%2Frelated-keywords&method=POST
const res = await pay("https://seo.openverbs.com/v1/related-keywords", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    "depth": 1,
    "keyword": "example",
    "limit": 1
  }),
});
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.04 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.04"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.post(
        "https://seo.openverbs.com/v1/related-keywords",
        json={
            "depth": 1,
            "keyword": "example",
            "limit": 1,
        },
    )
    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
1 h agoPassed402620 ms$0.04
5 h agoPassed402564 ms$0.04
9 h agoPassed402599 ms$0.04
13 h agoPassed402561 ms$0.04
17 h agoPassed402163 ms$0.04
21 h agoPassed402561 ms$0.04
25 h agoPassed402611 ms$0.04
29 h agoPassed402493 ms$0.04
32 h agoPassed402561 ms$0.04
36 h agoPassed402502 ms$0.04
40 h agoPassed402477 ms$0.04
43 h agoPassed402575 ms$0.04
47 h agoPassed402549 ms$0.04
2 days agoPassed402493 ms$0.04
2 days agoPassed402560 ms$0.04