Provided by DataForSEO
Look Up Monthly Search Volume and CPC for a List of Keywords (DataForSEO)
Look up Google Ads figures for a list of keywords in one location and language: the monthly number of searches, the advertiser competition level and the cost-per-click bid range. Hand it keywords you already have. Pay per request, with no plan.
Contract snapshot: 2026-09-29. Inspect in Glasser for current terms.
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"keywords",
"location_code",
"language_code"
],
"properties": {
"keywords": {
"type": "array",
"items": {
"type": "string",
"pattern": "^(?:(?!(?:site|inurl|intitle|allintitle|allinurl|filetype|related|cache):).)*$",
"maxLength": 700,
"minLength": 1
},
"maxItems": 100,
"minItems": 1
},
"language_code": {
"type": "string",
"pattern": "^[a-z]{2}$"
},
"location_code": {
"type": "integer",
"maximum": 99999999,
"minimum": 1
}
},
"additionalProperties": false
}{
"keywords": [
"coffee roaster",
"espresso machine"
],
"language_code": "en",
"location_code": 2840
}This Endpoint publishes no output schema. You get the Provider's own response body, unchanged — we do not warrant a shape we cannot guarantee.
How to run it
Two fields identify it: the Provider and the endpoint key. The key looks like a path because it usually mirrors the Provider's own, but it is an opaque identifier — not a URL you can open. The same provider:endpoint pair is what your Policy lists.
Once: paste this into your agent's chat. The Skill installs the CLI and logs in by itself. For an agent that cannot use a shell, connect it over MCP instead.
set up https://glasser.ai/SKILL.mdThen ask for this Endpoint:
Run the DataForSEO Endpoint /v3/keywords_data/google_ads/search_volume/live on Glasser with input {"keywords":["coffee roaster","espresso machine"],"language_code":"en","location_code":2840}glasser run -p dataforseo -e '/v3/keywords_data/google_ads/search_volume/live' -i '{"keywords":["coffee roaster","espresso machine"],"language_code":"en","location_code":2840}' --endpoint-version 2Pinned to version 2, the one this page shows: if a newer version is published first, the Run is refused instead of charged under new terms. Install and log in first on Get Started.
Once per Run:
IDEMPOTENCY_KEY=$(uuidgen)Run it, and copy this same block to send it again:
curl -X POST https://api.glasser.ai/v1/runs \
-H "Authorization: Bearer gl_..." \
-H "Idempotency-Key: $IDEMPOTENCY_KEY" \
-H "Content-Type: application/json" \
-d '{"provider":"dataforseo","endpoint":"/v3/keywords_data/google_ads/search_volume/live","input":{"keywords":["coffee roaster","espresso machine"],"language_code":"en","location_code":2840},"endpoint_version":2}'Reuse the same Idempotency-Key to send it again: the second send is a read of the first Run. A new key is a new Run and a new Charge. Pinned to version 2 for the same reason as the CLI.
What each outcome charges
| No result | The Provider answered: nothing matched. | $0.09 |
|---|---|---|
| Provider error | The Provider failed to answer. | $0.00 |
| Timed out | The deadline won. | $0.00 |
| Internal failure | Our defect. | $0.00 |