Check keywords.For Google and AI.

Why buy instead of build

We hold the accounts. Your agent pays by the call.

Endpoints and prices

88 endpoints. Check the price first.
Paid per call.

Connect your agent

Choose your protocol. Keep control of payment.

1 · JavaScript: inspect the Keyword Metrics price

// Free quote only. No wallet, signature or automatic payment.
const response = await fetch("https://agent.connskill.com/v1/keyword-metrics", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({ keywords: ["seo api", "keyword research"],
    location_code: 2276, language_code: "de" }),
  signal: AbortSignal.timeout(15000)
});
console.log(response.status, await response.json());
// HTTP 402 is a price offer, not a purchase or a delivered result.

Prepare one Keyword Metrics purchase with your agent

2 · A2A protocol (agent-to-agent)

# fetch the current agent card; paid skills use the x402 extension
curl https://agent.connskill.com/.well-known/agent-card.json

# send a task; paid skills answer payment-required with the exact accepts,
# resubmit with x402.payment.payload (EIP-3009 signature) and the taskId
curl -X POST https://agent.connskill.com/a2a -H 'Content-Type: application/json' -d '{
  "jsonrpc":"2.0","id":1,"method":"message/send","params":{"message":{
    "parts":[{"kind":"data","data":{"skill":"keyword-metrics","input":{"keywords":["seo api","keyword research"],"location_code":2276,"language_code":"de"}}}]}}}'

3 · MCP (Claude, Cursor, Codex, OpenClaw, Hermes)

Two ways. Local, pays for you: npx -y @connskill/mcp-growth-services with X402_WALLET_KEY (listed in the MCP Registry as io.github.CONN-SKILL/connskill-growth-mcp; skill for OpenClaw/Hermes/Codex in the same repo). Hosted, no install: claude mcp add --transport http connskill https://agent.connskill.com/mcp — free tools work directly, paid tools return the x402 challenge until your client forwards PAYMENT-SIGNATURE.

# Claude Code: plugin with MCP + skill (asks for the wallet key in its own config)
claude plugin marketplace add CONN-SKILL/connskill-growth-mcp
claude plugin install connskill-growth@connskill
# Hermes: tap the repo, install the skill
hermes skills tap add CONN-SKILL/connskill-growth-mcp && hermes skills install connskill-growth
# Free quote with payment disabled; approve inputs and budget separately
X402_MAX_USD=0 node skills/connskill-growth/scripts/x402-call.mjs POST /v1/keyword-metrics '{"keywords":["seo api","keyword research"],"location_code":2276,"language_code":"de"}'

4 · Plain HTTP with wallet proof

Standard x402 first purchases still use PAYMENT-SIGNATURE. The additional wallet proof below is required for manual x-payment-tx purchases and private result retrieval.

Before sending funds, check the JSON POST schema, the supported manual purchase route and your wallet. The actual USDC token payer must be an EOA wallet that can sign an EIP-191 message. Only the ref query key is supported; keep the complete public URL and every JSON field unchanged.

# 1. inspect the exact quote before paying
curl -X POST https://agent.connskill.com/v1/keyword-metrics \
  -H 'Content-Type: application/json' \
  -d '{"keywords":["seo api","keyword research"],"location_code":2276,"language_code":"de"}'

# 2. only after compatibility checks: transfer the quoted USDC on Base
# to payTo, then insert the real token payer address and confirmed tx hash
# below. This challenge request is free and does not transfer funds.
curl -X POST https://agent.connskill.com/v1/payments/challenge \
  -H 'Content-Type: application/json' -d '{
  "purpose":"purchase","address":"TOKEN_PAYER_ADDRESS",
  "request":{"method":"POST","url":"/v1/keyword-metrics",
    "headers":{"x-payment-tx":"PAYMENT_TX_HASH"},
    "body":{"keywords":["seo api","keyword research"],"location_code":2276,"language_code":"de"}}}'

# 3. sign the exact returned message with the token payer wallet;
# construct SIGNED_SIWX as described below, then send the same request
curl -X POST https://agent.connskill.com/v1/keyword-metrics \
  -H 'Content-Type: application/json' \
  -H 'x-payment-tx: PAYMENT_TX_HASH' \
  -H "Sign-In-With-X: ${SIGNED_SIWX}" \
  -d '{"keywords":["seo api","keyword research"],"location_code":2276,"language_code":"de"}'

SIGNED_SIWX is base64 JSON containing the returned sign-in-with-x info fields, address, chainId eip155:8453, type eip191 and your actual signature. It is a one-use wallet proof, not a new spending authorization. Replace the address and transaction placeholders with your own values.

For private retrieval, request a fresh free challenge with purpose redelivery and sign its exact message. Use the identical full URL, complete JSON body and original payment-reference headers. A standard x402 payment may use its original nonce reference when no transaction hash is known. Do not create another spending authorization. If the stored result is unavailable or the payment remains unresolved, use wallet support instead of ordering or paying again.

Wallet challenge schema · Wallet support

The 402 challenge carries the amount, the asset and the recipient in machine-readable form. Full spec at /openapi.json, service index at /.well-known/x402, agent card at /.well-known/agent-card.json, status at /health.