Live ai dataforseolabs google relevant pages
Run job:dataforseolabs.google.relevant-pages.live-ai through the looot API: 1 provider, from $0.012 per call. Inputs, prices, output shape and code for curl, JavaScript and Python.
Live ai dataforseolabs google relevant pages.
Job id dataforseolabs.google.relevant-pages.live-ai, in Search & SERP (SEO keyword & domain research). As of 2026-10-01, 1 provider serve it through 1 tool. Run job:dataforseolabs.google.relevant-pages.live-ai and looot picks one of them; with fallback on, a miss moves on to the next. See Jobs.
Inputs
This job has one tool, so it takes that tool’s fields. Any key you send passes through unchanged.
| Name | Type | Required | Description |
|---|---|---|---|
exclude_top_domains |
boolean | no | indicates whether to exclude world’s largest websites optional field default value: false set to true if you want to get highly-relevant competitors excluding the top websites |
filters |
array | no | Array-based filter expression. A single condition is a 3-element array: [field, operator, value]. Combine conditions with [“and”|“or”] between them: [condition, “and”, condition]. Max 8 filters. Operators: regex, not_regex, <, <=, >, >=, =, <>, in, not_in, match, not_match, ilike, not_ilike, like, not_like Use % with like/not_like/ilike/not_ilike as a wildcard. Examples: Single: [“metrics.organic.count”, “>”, 50] Combined: [[“metrics.organic.pos_1”, “<>”, 0], “and”, [“metrics.organic.impressi… |
ignore_synonyms |
boolean | no | ignore highly similar keywords, if set to true, results will be more accurate |
include_clickstream_data |
boolean | no | Include or exclude data from clickstream-based metrics in the result |
item_types |
array | no | display results by item type indicates the type of search results included in the response |
language_code |
string | no | language code required field example: en |
limit |
number | no | Maximum number of keywords to return |
location_name |
string | no | full name of the location required field only in format “Country” (not “City” or “Region”) example: ‘United Kingdom’, ‘United States’, ‘Canada’ |
offset |
number | no | offset in the results array of returned keywords optional field default value: 0 if you specify the 10 value, the first ten keywords in the results array will be omitted and the data will be provided for the successive keywords |
order_by |
array | 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 you should use a comma to specify a sorting type example: [“metrics.paid.etv,asc”] Note: you can set no more than three sorting rules in a single request you should use a comma to separate several sorting rules example: [“metrics.organic.etv,desc”,“metrics.p… |
target |
string | yes | target domain |
Providers and prices
| Provider | Tool | Price |
|---|---|---|
| DataForSEO | dataforseo-dataforseo-labs-google-relevant-pages-live-ai |
$0.012 per call |
A call that fails at the provider costs $0. See What’s free.
Output
The run’s result holds the provider’s answer. Signed in, looot inspect dataforseo-dataforseo-labs-google-relevant-pages-live-ai prints its fields.
Run it
Every call needs your API token in LOOOT_TOKEN; Sign in shows how to get one. Each run also needs a new idempotency key, so a retry never pays twice. With wait: 30 the answer comes back inline when the run ends within 30 seconds. Otherwise you get the running run back: poll GET /v1/runs/<runId>.
Example input with placeholder values:
curl -X POST "https://api.looot.ai/v1/runs" \
-H "Authorization: Bearer $LOOOT_TOKEN" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: $(uuidgen)" \
-d '{"endpointId":"job:dataforseolabs.google.relevant-pages.live-ai","input":{"target":"<target>"},"wait":30}'const response = await fetch("https://api.looot.ai/v1/runs", {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.LOOOT_TOKEN}`,
"Content-Type": "application/json",
"Idempotency-Key": crypto.randomUUID(),
},
body: JSON.stringify({
endpointId: "job:dataforseolabs.google.relevant-pages.live-ai",
input: {
target: "<target>",
},
wait: 30,
}),
});
const run = await response.json();
console.log(run.status, run.result);import os
import uuid
import requests
response = requests.post(
"https://api.looot.ai/v1/runs",
headers={
"Authorization": f"Bearer {os.environ['LOOOT_TOKEN']}",
"Idempotency-Key": str(uuid.uuid4()),
},
json={
"endpointId": "job:dataforseolabs.google.relevant-pages.live-ai",
"input": {
"target": "<target>",
},
"wait": 30,
},
timeout=90,
)
run = response.json()
print(run["status"], run.get("result"))To pin one provider, send its tool id as endpointId instead of job:dataforseolabs.google.relevant-pages.live-ai.