Keyword Suggestions
by Long-tail keyword suggestions in Search & web
Keyword suggestions API - find long-tail keywords that contain your seed phrase (full-text phrase match), each with Google monthly search volume, CPC, competition, keyword difficulty and search intent. Complements keyword-ideas (semantically related terms) with literal phrase-match variations. For long-tail content and PPC research. No matches returns empty results.
https://seo.openverbs.com/v1/keyword-suggestions- Price
- $0.04
- per call in USDC
- Uptime
- 100%
- last 30 days
- Response time
- 559 ms
- 628 ms slowest 5%
- Last check
- Passed
- 2 h ago, next any minute now
Reliability
How to call it
POST https://seo.openverbs.com/v1/keyword-suggestions
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/keyword-suggestions
content-type: application/json
{
"keyword": "example",
"limit": 1,
"locationCode": 1
}Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
keyword | string | Yes | Seed phrase; suggestions contain this phrase. |
languageCode | string | No | Language code (2-letter). Defaults to en. |
limit | integer | No | Maximum suggestions to return. Defaults to 20. |
locationCode | integer | No | DataForSEO 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/keyword-suggestions' \
-H 'content-type: application/json' \
--data-raw '{"keyword":"example","limit":1,"locationCode":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/keyword-suggestions' \
-H 'content-type: application/json' \
--data-raw '{"keyword":"example","limit":1,"locationCode":1}' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: 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%2Fkeyword-suggestions&method=POST
const res = await pay("https://seo.openverbs.com/v1/keyword-suggestions", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"keyword": "example",
"limit": 1,
"locationCode": 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/keyword-suggestions",
json={
"keyword": "example",
"limit": 1,
"locationCode": 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
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 2 h ago | Passed | 402 | 529 ms | $0.04 |
| 6 h ago | Passed | 402 | 604 ms | $0.04 |
| 10 h ago | Passed | 402 | 563 ms | $0.04 |
| 14 h ago | Passed | 402 | 528 ms | $0.04 |
| 18 h ago | Passed | 402 | 568 ms | $0.04 |
Show 10 older checks
| 22 h ago | Passed | 402 | 549 ms | $0.04 |
| 26 h ago | Passed | 402 | 566 ms | $0.04 |
| 30 h ago | Passed | 402 | 558 ms | $0.04 |
| 33 h ago | Passed | 402 | 580 ms | $0.04 |
| 37 h ago | Passed | 402 | 559 ms | $0.04 |
| 40 h ago | Passed | 402 | 567 ms | $0.04 |
| 44 h ago | Passed | 402 | 628 ms | $0.04 |
| 47 h ago | Passed | 402 | 500 ms | $0.04 |
| 2 days ago | Passed | 402 | 561 ms | $0.04 |
| 2 days ago | Passed | 402 | 559 ms | $0.04 |