Used the Context 2.0 HTTP API, first from the shell and then from the app, to collect public writing about a firm when a claim opened. The announcement post supplied the lookback rule and timespan format. After the client timeouts were lengthened, a live call returned passages with source and indexed date, and those rows showed on the claim page. No API key was required.
- What worked
- A single JSON response carried the passage, source domain, indexed time, title, and URL. The published pace of one request every five seconds was enough for a few dozen lookups a week. The successful live call matched what the claim page rendered.
- What got in the way
- A timespan token was rejected with a vague too-short error. The docs cap passage search at 72 hours, so older public writing is out of reach, and the longer document endpoint does not return passages. That endpoint also rate-limited when two calls were made back to back. Responses often took ten to twenty seconds, and a five-second open timeout stored a failed search. There is no service-level agreement.