DataForSEO
Domain Analytics Technologies Domains By Html Terms
This endpoint provides domains based on the HTML terms they use on their homepage. In addition to the list of domains, you will also get their technology profiles, the country and language they belong to, and other related data.
Usage based DataForSEOEnrichmentdataforseo/domain-analytics-technologies-domains-by-html-termsActive
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-technologies-domains-by-html-terms (Domain Analytics Technologies Domains By Html Terms). Call inspect_tool with {"tool_id": "dataforseo/domain-analytics-technologies-domains-by-html-terms"} 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-technologies-domains-by-html-terms" 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 |
|---|---|---|---|
search_terms | string[] | Yes | target search terms required field specify target HTML elements, tags, attributes, their content or all of the above if you specify more than one search term, you will receive only the domains containing all of the specified terms in the HT |
keywords | string[] | No | target keywords in the domain's title, description or meta keywords optional field UTF-8 encoding maximum number of keywords you can specify: 10 example: ["seo","software"]learn more about rules and limitations of keyword and keywords field |
mode | string | No | search mode optional field possible search mode types: strict_entry - search for results exactly matching the order, intervals and separators in the specified search terms entry - search for results ignoring the order, intervals and separat |
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: <, <=, >, >=, =, <>, in, no |
order_by | string[] | No | results sorting rules optional field available fields: domain_rank, domain, last_visited, country_iso_code, language_code, content_language_code possible sorting types: asc - results will be sorted in the ascending order desc - results will |
limit | integer | No | the maximum number of returned domains optional field default value: 100 maximum value: 10000 |
offset | integer | No | offset in the results array of returned domains optional field default value: 0 if you specify the 10 value, the first ten domains in the results array will be omitted and the data will be provided for the successive domains; Note: the maxi |
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 |
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-technologies-domains-by-html-terms",
"input": {
"search_terms": [
"data-attrid"
],
"order_by": [
"last_visited,desc"
],
"limit": 10,
"offset": 0
}
}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.