Skip to main content
Human guide: work with your agent → Inspect one DataForSEO action before starting provider-backed work. Your first result is a verified input and output contract.

​
Provider-specific requirements

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 packages/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.

​
Find an applicable action

Confirm your effective workspace, then search the live catalog:
Search returns candidates. Check the returned provider and operation rather than selecting a similar title automatically.

​
Inspect the selected contract

Replace <returned-tool-id> with the identifier returned by discovery:
These commands do not execute the selected provider action. Read its required inputs, supported access mode, pricing unit, outputs, and limits. A connection does not establish that every action supports BYOK. Follow the provider-specific requirements above and the live action contract.

​
Prepare one reviewed input

Use one authorized record that matches the inspected schema. Preserve its source identity and define the result you will accept. Open the action reference for its payload and response shape. Provider-backed execution can incur usage or external effects. For reusable logic, follow Write Plays. For direct-call recovery, use Tool execution recovery.
Continue only when the workspace, provider, required fields, acceptance rule, and applicable price are understood. Keep unavailable access separate from no-result evidence.