Provided by Serpstat
Get Visibility, Keyword Count and Traffic Estimates for Up to Five Domains (Serpstat)
Get the headline figures of one to five domains in a regional database: every domain comes back with its visibility score, how many keywords it ranks for, its estimated organic traffic with the change since the month before, and its count of ad keywords. Supply the domains and a regional database code such as g_us. Headline figures per domain only, one object each and nothing itemized.
How to run it
Step 1Set up
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.md
Show me how to use the Serpstat endpoint /v4/SerpstatDomainProcedure.getDomainsInfo on Glasser.glasser run -p serpstat -e '/v4/SerpstatDomainProcedure.getDomainsInfo' -i '{"se":"g_us","domains":["example.com"]}' --endpoint-version 3Uses endpoint version 3. Inspect the current price before running. 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":"serpstat","endpoint":"/v4/SerpstatDomainProcedure.getDomainsInfo","input":{"se":"g_us","domains":["example.com"]},"endpoint_version":3}'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. Uses endpoint version 3; inspect the current price before running.
Step 2Try a specific example task
When you need to prioritize a keyword shortlist, you might compare search-volume metrics to understand demand for the topics you are considering.
Copy this prompt into your agent to review search demand for your keyword shortlist.
Use serpstat:/v4/SerpstatDomainProcedure.getDomainsInfo on Glasser.
Check demand for my keyword shortlist using the search-volume metrics actually returned.Endpoint structure
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"domains",
"se"
],
"properties": {
"se": {
"type": "string",
"pattern": "^[a-z]{1,2}_[a-z]{2,3}$",
"maxLength": 8
},
"domains": {
"type": "array",
"items": {
"type": "string",
"pattern": "^(?!-)(?:[a-z0-9-]+\\.)+[a-z]{2,}$",
"maxLength": 253,
"minLength": 3
},
"maxItems": 5,
"minItems": 1
}
},
"additionalProperties": false
}{
"se": "g_us",
"domains": [
"example.com"
]
}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 pricing works
| Per result returned | Charged for each result returned. | $0.0025 |
|---|---|---|
| Maximum per Run | The total charge will not exceed this amount. | $0.05 |
| No matching data | The Provider answered: nothing matched. | $0.002 |
| Provider error | The Provider failed to answer. | $0.00 |
| Timed out | The Run exceeded its time limit. | $0.00 |
| Internal failure | An internal error prevented completion. | $0.00 |