fix(catalog): document DataForSEO Google AI Mode live as single-task - #528
Merged
Merged
Conversation
Feedback #94: catalog_get reused the generic "ARRAY of task objects — one object per task" note on dataforseo.x.serp-google-ai-mode-live-advanced. The live route accepts exactly one task; extra elements return per-task status 40000 behind HTTP 200. Name the cap in input.note, leave settlement and call splitting unchanged. Co-authored-by: SToneX <shitianxin@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this does
Stops
catalog_getfrom telling agents they can POST multiple tasks todataforseo.x.serp-google-ai-mode-live-advanced(/serp/google/ai_mode/live/advanced).Same class as
dataforseo.web.backlinks.summary(treg feedback #102 / #487): this is a Live single-task route. Extra array elements come back as per-task status40000"You can set only one task at a time" behind HTTP 200 (first task OK, the rest rejected at $0). The endpoint'sinput.notestill said "the POST body is an ARRAY of task objects with these fields — one object per task", which agents read as multi-task batching. Provider-levellimitsalready name Live = one task per POST; this endpoint's own note did not.Catalog-only: rewrite
input.noteto name the single-task cap and the 40000, including that HTTP stays 200. No settlement change, no auto-split of multi-task arrays into billed calls.Addresses treg feedback #94.
How it was tested
dataforseo.x.serp-google-ai-mode-live-advancednow mirrors backlinks.summary / google.serp.organic / page.audit: exactly one task object; extra elements get 40000.test_google_ai_mode_live_documents_single_task_constraintlocks the YAML note, 40000, and one-elementtest_request.test_catalog_get_dataforseo_ai_mode_live_names_the_single_task_limitlocks thecatalog_getHTTP payload.uv run --frozen python scripts/catalog_validate.py— 102 provider files, 0 errors.uv run --locked lint-imports— 14 contracts kept.uv run --with pytest-xdist pytest -n auto -q— 4171 passed, 8 skipped.Checklist
uv run --with pytest-xdist pytest -n auto -qpasses locallydocs/context/fragment (docs/context/architecture/catalog.md).envvalues)