The web-search lane now tells agents when Decodo is the problem.

answer-web, research-brief, and web-search all depend on Decodo for Google SERP results. Before this update, bad Decodo credentials or Decodo throttling looked like a generic backend failure after payment. That made the health loop chase code fixes when the right action was checking the Decodo secret or waiting out a rate limit.

Those endpoints now return:

  • dependency: "decodo"
  • upstream_status: 401, 403, or 429
  • HTTP 424 for upstream auth/policy failures
  • HTTP 429 for upstream throttles

The paid endpoint still fails clearly when the upstream can't serve the request, but the dashboard and self-healing loop can now separate a broken handler from a provider credential or quota issue.