Provided by DataForSEO
Content Analysis rating_distribution live
Rating_distribution live via DataForSEO Content Analysis. One task per call, priced by the vendor's own rate card; an empty result set is reported as no result.
Contract snapshot: 2026-09-17. Inspect in Glasser for current terms.
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"keyword"
],
"properties": {
"tag": {
"type": "string",
"maxLength": 2048,
"minLength": 1
},
"keyword": {
"type": "string",
"maxLength": 2048,
"minLength": 1
},
"page_type": {
"type": "array",
"items": {
"type": "string",
"maxLength": 2048,
"minLength": 1
},
"maxItems": 100,
"minItems": 1
},
"rank_scale": {
"type": "string",
"maxLength": 2048,
"minLength": 1
},
"search_mode": {
"type": "string",
"maxLength": 2048,
"minLength": 1
},
"internal_list_limit": {
"type": "integer"
},
"positive_connotation_threshold": {
"anyOf": [
{
"type": "number"
},
{
"enum": [
"Infinity",
"-Infinity",
"NaN"
],
"type": "string"
}
]
},
"sentiments_connotation_threshold": {
"anyOf": [
{
"type": "number"
},
{
"enum": [
"Infinity",
"-Infinity",
"NaN"
],
"type": "string"
}
]
}
},
"additionalProperties": false
}{
"keyword": "logitech"
}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/content_analysis/rating_distribution/live on Glasser with input {"keyword":"logitech"}glasser run -p dataforseo -e '/v3/content_analysis/rating_distribution/live' -i '{"keyword":"logitech"}' --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/content_analysis/rating_distribution/live","input":{"keyword":"logitech"},"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.024 |
|---|---|---|
| Provider error | The Provider failed to answer. | $0.00 |
| Timed out | The deadline won. | $0.00 |
| Internal failure | Our defect. | $0.00 |