Live ai dataforseolabs google page intersection

Run job:dataforseolabs.google.page-intersection.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 page intersection.

Job id dataforseolabs.google.page-intersection.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.page-intersection.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_pages`	array	no	URLs of pages you want to exclude optional field you can set up to 10 pages in this array if you use this array, results will contain the keywords for which URLs from the pages object rank, but URLs from exclude_pages array do not; note that if you specify this field, the results will be based on the keywords any URL from pages ranks for regardless of intersections between them. However, you can set intersection_mode to intersect and results will contain the keywords all URLs from pages rank…
`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: [“keyword_data.keyword_info.search_volume”, “in”, [100, 1000]] Combined: [[“intersection_result.1.etv”, “>”, 0], “a…
`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
`intersection_mode`	string	no	indicates whether to intersect keywords optional field use this field to intersect or merge results for the specified URLs possible values: union, intersect union, results are based on all keywords any URL from pages rank for; intersect, results are based on the keywords all URLs from pages rank for in the same SERP: by default, results are based on the intersect mode if you specify only pages array. If you specify exclude_pages as well, results are based on the union mode
`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 set up a sorting parameter example: [“keyword_data.keyword_info.competition,desc”] default rule: [“keyword_data.keyword_info.search_volume,desc”] note that you can set no more than three sorting rules in a single request you should…
`pages`	object	yes	object of numbered keys to domains/pages, e.g. {“1”: “nike.com”, “2”: “adidas.com”} (DataForSEO intersection format); Object containing two page values to compare

Providers and prices

Provider	Tool	Price
DataForSEO	`dataforseo-dataforseo-labs-google-page-intersection-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-page-intersection-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.page-intersection.live-ai","input":{"pages":{"1":"https://www.nike.com/","2":"https://www.adidas.com/"}},"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.page-intersection.live-ai",
    input: {
      pages: {
        "1": "https://www.nike.com/",
        "2": "https://www.adidas.com/",
      },
    },
    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.page-intersection.live-ai",
        "input": {
            "pages": {
                "1": "https://www.nike.com/",
                "2": "https://www.adidas.com/",
            },
        },
        "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.page-intersection.live-ai.