DataForSEO
Domain Analytics Whois Overview
This endpoint will provide you with Whois data enriched with backlink stats, and ranking and traffic info from organic and paid search results. Using this endpoint you will be able to get all these data for the domains matching the parameters you specify in the request.
Usage based DataForSEOEnrichmentdataforseo/domain-analytics-whois-overviewActive
Use this tool with your agent
Give this to your agent
Use my connected Agentik MCP server. I want to use the tool dataforseo/domain-analytics-whois-overview (Domain Analytics Whois Overview). Call inspect_tool with {"tool_id": "dataforseo/domain-analytics-whois-overview"} first and tell me the price before anything runs. Ask me for the inputs it needs; never invent values, IDs or file URLs. When I confirm, call run_tool with tool_id "dataforseo/domain-analytics-whois-overview" and my inputs, follow it with get_run if it is still running, and give me the result and the price Agentik reports. If the tool is unavailable, say so and use discover_tools to propose an alternative.Show the prompt
Paste it into Claude, ChatGPT or Codex: your agent takes it from there, and shows the price before it runs.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
limit | integer | No | the maximum number of returned domains optional field default value: 100 maximum value: 1000 |
offset | integer | No | offset in the results array of returned items optional field default value: 0 if you specify the 10 value, the first ten items in the results array will be omitted and the data will be provided for the successive items; Note: we recommend u |
offset_token | string | No | token for subsequent requests optional field provided in the identical filed of the response to each request; use this parameter to avoid timeouts while trying to obtain over 100,000 results in a single request; by specifying the unique off |
filters | any[] | No | array of results filtering parameters optional field you can add several filters at once (8 filters maximum) you should set a logical operator and, or between the conditions the following operators are supported: regex, <, <=, >, >=, =, <>, |
order_by | string[] | No | results sorting rules optional field you can use the same values as in the filters array to sort the results possible sorting types: asc - results will be sorted in the ascending order desc - results will be sorted in the descending order t |
tag | string | No | user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response |
How your agent calls it
First inspect_tool for the current schema and price, then run_tool with the published example after confirming your inputs:
{
"tool_id": "dataforseo/domain-analytics-whois-overview",
"input": {
"limit": 10,
"filters": [
[
"epp_status_codes",
"in",
[
"client_transfer_prohibited",
"client_update_prohibited"
]
]
]
}
}Price and billing
- Price
- Usage based
- Model
- Usage based
- Detail
- Billed at the cost the provider reports for the call, never above $100. Your agent sees the maximum before running.
- The provider’s price, 0% markup.
- One prepaid balance for every provider; your agent sees the price before it runs.
- Pay for measured usage; unused reservations are released.