Trevor H.

Tried Claygent variants (Navigator, Argon). Argon helps with discovery, but consistent PDF reading is unreliable and sometimes summaries come from secondary sources instead of the PDF.

Ideal: a Clay-native pattern that handles redirects/viewers and image-only PDFs with OCR. If needed, we’d consider a tiny external “PDF fetcher” API called from Clay (handles redirects/cookies/JS-gated downloads + OCR, returns text URL and hash).

Scale target is 10k–20k accounts with cost control. We’ll capture provenance and confidence, and only push high-confidence results downstream.

Questions: what’s working for you in Clay today for high-reliability PDF fetch-and-parse? Any agent-chaining prompts, retries/backoff patterns, or tools you recommend? If you use a minimal external helper, what’s the lightest approach that plugs cleanly into a Custom API step?