Claude Code + SEO data
Claude Code runs the work loop and SEO data performs the selected operation. The Composer below preselects Claude Code, Claude Opus 5, and this tool so you can test one real task with the same billing and recovery path as any AgentSky run.
How the combination works
Claude Code decides when to call SEO data.
Claude Code runs the coding loop, reads and edits repository files, invokes tools, and reports the result from its cloud workspace.
Use the DataForSEO Google Organic Live Advanced endpoint to study the pages competing for a search query. The current AgentSky adapter fixes the location to the United States and derives the language from locale. This makes the tool useful for US search-result research, but not for choosing an arbitrary country.
Claude Code
Owns the task loop, context, model calls, tool choice, cloud computer, progress and final result.
SEO data
Performs the operation exposed by the current SEO data capability. Its input limits and output shape come from the live tool guide and adapter.
AgentSky
Keeps the selected agent, model, capability grant, task state and usage record together. Tool charges and model or runtime charges remain itemized separately.
Setup and first task
Start with one bounded seo data task.
The Composer carries Claude Code, Claude Opus 5, and SEO data. Begin with the smallest input that lets you inspect the output before expanding the workflow.
Open the Claude Code Composer
The Composer above preselects Claude Code, Claude Opus 5, and SEO data. Add the target, required inputs and a concrete expected result; the draft stays in place through sign-in.
State the SEO data boundary
Inspect US English search results for “AI coding agent”. Group the top results by product pages, comparisons, and documentation.
Run and verify the returned result
Check the output against the source or brief, confirm that the result has the expected format, and inspect the task usage for model, runtime and tool charges.
Inputs, cost and limits
What Claude Code + SEO data establishes
Repository work where Claude Code's coding workflow and supported Claude models fit the team's existing review process.
Configure and verify
- Claude Code and Claude Opus 5 are preselected for the browser evaluation.
- SEO data is enabled from the current capability catalog with its live input and output guidance.
- The first task can be checked from the returned artifact, text or provider result before a larger workflow is attempted.
Still depends on the task
- A tool guide does not guarantee a provider result for malformed, blocked or unsupported SEO data inputs.
- A successful tool call does not establish that the result is correct for your business decision; inspect the output at its source boundary.
- Total task cost can include model tokens, active computer time and the selected tool's billable units.
Current SEO data rates
dataforseo.serp
$0.006 per run; fallback estimate. Supplier-reported cost takes precedence and is charged at 2×.
Tool-specific details
Use the current SEO data contract.
Use the DataForSEO Google Organic Live Advanced endpoint to study the pages competing for a search query. The current AgentSky adapter fixes the location to the United States and derives the language from locale. This makes the tool useful for US search-result research, but not for choosing an arbitrary country.
Search engine and location
Google organic live advanced results; location_code 2840 (United States).
Language
locale defaults to en-US. The adapter sends the language portion before the hyphen; changing en-US to en-GB does not change the country.
Returned data
The adapter returns the provider’s result objects. Although the CLI lists a limit option, the current adapter does not forward it to DataForSEO.
Common questions
Related resources