Bugs we found in our own pipeline

The One Number in Our Newsletter That Wasn't Grounded in Filed Data — and What We Did About It

Every metric in an Edge Thirteen value pick comes from a structured data pull — except dividend yield, which we asked the write-up model to state without ever giving it the number. Here's the real error it produced, the fix, and the tool we built so it can't happen again.

The Bug That Fed Our Screener Table-of-Contents Text Instead of Real Risk Factors

Every SEC 10-K and 10-Q lists its own section headings twice — once in the table of contents, once as the real heading. A naive text search always matches the wrong one. Here's the scoring fix, with real code.

The One-Line .strip() That Silently Renamed Every Bank Capital Ratio

FFIEC's own Call Report TSV files encode field names in a way that breaks if you clean the file before you parse it. A $9,860 'ratio' is what gave it away.

Two Bugs Stripe's Own Docs Don't Mention: Building an Agent-Payable Endpoint on MPP

Stripe's Machine Payments Protocol lets an AI agent pay per request over plain HTTP 402, no crypto wallet involved. The sample code in the docs doesn't build. Here's what actually breaks, and the fix.

Our Own Link Checker Flagged SEC.gov Filings as Broken. They Weren't.

SEC.gov returns 403 to any crawler that doesn't identify itself with a real company name and contact email in its User-Agent header — and a 403 looks exactly like a dead link to most tools. Here's how to tell the difference, with real headers.