Live ai keywordsdata dataforseo trends explore

Run job:keywordsdata.dataforseo-trends.explore.live-ai through the looot API: 1 provider, from $0.09 per call. Inputs, prices, output shape and code for curl, JavaScript and Python.

Live ai keywordsdata dataforseo trends explore.

Job id keywordsdata.dataforseo-trends.explore.live-ai, in Search & SERP (Keyword volume & trends). As of 2026-10-01, 1 provider serve it through 1 tool. Run job:keywordsdata.dataforseo-trends.explore.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
`date_from`	string	no	starting date of the time range if you don’t specify this field, the current day and month of the preceding year will be used by default minimal value for the web type: 2004-01-01 minimal value for other types: 2008-01-01 date format: “yyyy-mm-dd” example: “2019-01-15”
`date_to`	string	no	ending date of the time range if you don’t specify this field, the today’s date will be used by default date format: “yyyy-mm-dd” example: “2019-01-15”
`keywords`	array	yes	keywords the maximum number of keywords you can specify: 5
`location_name`	string	no	full name of the location optional field in format “Country” example: United Kingdom
`time_range`	string	no	preset time ranges if you specify date_from or date_to parameters, this field will be ignored when setting a task
`type`	string	no	dataforseo trends type

Providers and prices

Provider	Tool	Price
DataForSEO	`dataforseo-keywords-data-dataforseo-trends-explore-live-ai`	$0.09 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-keywords-data-dataforseo-trends-explore-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:keywordsdata.dataforseo-trends.explore.live-ai","input":{"keywords":[]},"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:keywordsdata.dataforseo-trends.explore.live-ai",
    input: {
      keywords: [],
    },
    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:keywordsdata.dataforseo-trends.explore.live-ai",
        "input": {
            "keywords": [],
        },
        "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:keywordsdata.dataforseo-trends.explore.live-ai.