Repository navigation
Correct Backlinks + LLM Mentions to pay-as-you-go (DataForSEO 2026-07-01) - #6
Merged
Merged
Conversation
…-01 update) DataForSEO cancelled the $100/mo minimums on the Backlinks and LLM Mentions APIs on 2026-07-01 and moved every endpoint to pay-as-you-go. The brain previously asserted both were subscription-gated (40204), including an authoritative "NOT removed" debunk in cap-backlinks-api that became false after the published update. Re-verified live 2026-07-08 against the production API: summary/live, bulk_ranks/live, and llm_mentions/search/live now return 20000 Ok (were 40204). Captured the first authentic Backlinks + LLM Mentions fixtures (local .raw, gitignored per repo convention) and a dated re-probe cost log. - Reframe 40204 as a defined-but-legacy code for these modules: kept in the error catalog, no longer returned on a pay-as-you-go account - Flip dashboard-map.json gate flags (gated/gated_partial -> false) and rewrite the gate notes - Add a dated pricing-update source to source-ledger and update the two Backlinks/LLM-Mentions claim rows with the re-probe result - Correct hub, operator dashboard, overview, hot cache, current-requirements, changelog, and build log - Preserve the honest timeline: gated through 2026-06-26, removed 2026-07-01 Verification: audit_brain market-ready, score 100; pytest 6 passed. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.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 changed and why
On 2026-07-01 DataForSEO published a pricing update that cancelled all remaining monthly commitments and moved every endpoint to a 100% pay-as-you-go model. The $100/mo minimums on the Backlinks API and LLM Mentions API were removed (existing subscriptions auto-cancelled, access retained).
The brain asserted the opposite. As of 2026-06-26 it documented both modules as subscription-gated (
40204), andcap-backlinks-apieven carried an authoritative "the subscription was NOT removed" debunk. That was accurate on 2026-06-26 and became false on 2026-07-01. This PR corrects the brain across 24 files.Verification
40204endpoints now return20000 Okwith real data:/v3/backlinks/summary/live->20000(dataforseo.com: 347,004 backlinks, rank 323), ~$0.024/v3/backlinks/bulk_ranks/live->20000, ~$0.024/v3/ai_optimization/llm_mentions/search/live->20000, ~$0.105.raw/, gitignored per repo convention) plus a dated re-probe cost log.Changes
dashboard-map.jsongate flags flipped (gated/gated_partial->false) with rewritten gate notes.source-ledger.jsongains a dated pricing-update source; the two Backlinks / LLM-Mentions claim rows updated with the re-probe result.DataForSEO Brain Home), operator dashboard, overview, hot cache,current-requirements,CHANGELOG, and build log all corrected.Gates
audit_brain.py --require market-ready: market-ready, score 100pytest: 6 passed (the CI gate)Notes / out of scope
tests/test_pipeline.pyhas a pre-existing, date-dependent failure:build_demo_vault.pystamps today's date into the demo vault, sopackage_release --release-type market-readyblocks on "dirty tracked files" before reaching the market-ready check, which the test's assertion string doesn't match. Unrelated to this content change (CI runs pytest, not this self-test). Flagging for a separate fix.hot.mdandcurrent-requirementsnote that pricing figures are due a refresh.🤖 Generated with Claude Code