> ## Documentation Index
> Fetch the complete documentation index at: https://deepline.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Dataforseo API Guide for GTM Workflows

> Use DataForSEO for native SEO and content-analysis endpoints. Most tools are generated directly from the docs catalog, so prefer regeneration over hand edits.

## Playbook

# DataForSEO

Use DataForSEO when you need broad SEO, SERP, content analysis, backlink, or keyword datasets directly from the provider API.

## Auth

* DataForSEO upstream uses HTTP Basic auth.
* Store `DATA_FOR_SEO_API_KEY` as either a raw `login:password`, a pre-encoded base64 token, or a full `Basic ...` header value.

## Execution notes

* Generated POST tools send the payload as a single-task array because DataForSEO task/live endpoints are array-based.
* Generated GET tools pass top-level fields as query parameters.
* Pricing metadata is scraped from DataForSEO pricing pages and may be formula-based rather than fixed per call.

## Generated surface

* Most tool docs, fixtures, sample outputs, mocks, and catalog metadata are generated by `src/lib/integrations/dataforseo/dev/generate-dataforseo-provider.ts`.
* If the docs or schemas drift, update the scraper/generator and regenerate instead of manually editing generated artifacts.