---
title: "Live ai dataforseolabs google serp competitors"
description: "Run job:dataforseolabs.google.serp-competitors.live-ai through the looot API: 1 provider, from $0.012 per call. Inputs, prices, output shape and code for curl, JavaScript and Python."
sidebar:
  hidden: true
---

{/* Generated by scripts/generate-api-reference.mjs from data/api-reference.json. Do not edit. */}

Live ai dataforseolabs google serp competitors.

Job id `dataforseolabs.google.serp-competitors.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.serp-competitors.live-ai` and looot picks one of them; with `fallback` on, a miss moves on to the next. See [Jobs](/concepts/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 |
| --- | --- | --- | --- |
| `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: ["median_position", "in", [1, 10]] Combined: [["median_position", "in", [1, 10]], "and", ["domain", "not_like", "%w... |
| `include_subdomains` | boolean | no | Include keywords from subdomains |
| `item_types` | array | no | display results by item type indicates the type of search results included in the response |
| `keywords` | array | yes | keywords array required field the results will be based on the keywords you specify in this array UTF-8 encoding; the keywords will be converted to lowercase format; you can specify the maximum of 200 keywords |
| `language_code` | string | no | language code required field example: en |
| `language_name` | string | no | language name, e.g. 'English' |
| `limit` | number | no | Maximum number of keywords to return |
| `location_code` | integer | no | DataForSEO location code, e.g. 2840 for the United States |
| `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 the comma is used as a separator example: ["avg_position,asc"] default rule: ["rating,desc"] note that you can set no more than three sorting rules in a single request you should use a comma to separate several sorting rules example: ["avg_position,asc","etv... |

## Providers and prices

| Provider | Tool | Price |
| --- | --- | --- |
| [DataForSEO](/providers/dataforseo) | [`dataforseo-dataforseo-labs-google-serp-competitors-live-ai`](/reference/tools/dataforseo-dataforseo-labs-google-serp-competitors-live-ai) | $0.012 per call |

A call that fails at the provider costs $0. See [What's free](/money/free-and-failures).

## Output

The run's `result` holds the provider's answer. Signed in, `looot inspect dataforseo-dataforseo-labs-google-serp-competitors-live-ai` prints its fields.

## Run it

Every call needs your API token in `LOOOT_TOKEN`; [Sign in](/get-started/sign-in#use-the-token-in-scripts-and-agents) 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:

<CodeGroup>

```bash curl
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.serp-competitors.live-ai","input":{"keywords":[]},"wait":30}'
```

```js JavaScript
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.serp-competitors.live-ai",
    input: {
      keywords: [],
    },
    wait: 30,
  }),
});
const run = await response.json();
console.log(run.status, run.result);
```

```python Python
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.serp-competitors.live-ai",
        "input": {
            "keywords": [],
        },
        "wait": 30,
    },
    timeout=90,
)
run = response.json()
print(run["status"], run.get("result"))
```

</CodeGroup>

To pin one provider, send its tool id as `endpointId` instead of `job:dataforseolabs.google.serp-competitors.live-ai`.