Teknium 6696c7b0a4 fix(web): Exa and Keenable origin statuses never read as vendor throttling ...

Keyless Exa reports the target's status as CRAWL_HTTP_<code> / CRAWL_NOT_FOUND and
Keenable mirrors it as its own HTTP status with a "The target server ..." message.
Neither used the "HTTP <code> from origin" shape, so a site's own 429 walked the
keyless extract ring as if the vendor throttled us, and a 404 read as a vendor
failure with an API-key hint. Normalise both (keyless and keyed paths) into the
origin shape; Keenable's own rate limit and refusals keep the vendor wording and
still fail over.

2026-10-28 13:13:12 -07:00

..

__init__.py

…

plugin.yaml

…

provider.py

fix(web): Exa and Keenable origin statuses never read as vendor throttling

2026-10-28 13:13:12 -07:00