Live ai dataforseolabs google historical serps

Run job:dataforseolabs.google.historical-serps.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 historical serps.

Job id dataforseolabs.google.historical-serps.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.historical-serps.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, date format: YYYY-MM-DD
`date_to`	string	no	ending date of the time range, date format: YYYY-MM-DD
`keyword`	string	yes	target keyword
`language_code`	string	no	language code required field example: en
`language_name`	string	no	language name, e.g. ‘English’
`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’

Providers and prices

Provider	Tool	Price
DataForSEO	`dataforseo-dataforseo-labs-google-historical-serps-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-historical-serps-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.historical-serps.live-ai","input":{"keyword":"<keyword>"},"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.historical-serps.live-ai",
    input: {
      keyword: "<keyword>",
    },
    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.historical-serps.live-ai",
        "input": {
            "keyword": "<keyword>",
        },
        "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.historical-serps.live-ai.