Webz.io CEO Ran Geva’s post, Dark Web Monitoring API: First-Post Filters Hide Replies, is about one query parameter. Its opening line states the problem: “Your dark web monitoring API can locate a seller’s opening post and still miss the reply that challenges it.” The Cyber API’s is_first:true filter returns only the first post in a thread. That works for a discovery screen and badly for a collector that follows a case. With a query like "ExampleCo" is_first:true, the collector finishes without an error, the analyst sees the seller’s claim, and the reply disputing the sample’s attribution never arrives.
There is no marketing figure to discount here. The one real-world reference, AhnLab’s 4 November bulletin on OBSOFT’s claims against five South Korean companies, is handled carefully: the post says the bulletin describes claims, not confirmed damage, and that the constructed example “does not describe the OBSOFT discussion.” The advice is specific. Drop the first-post filter where replies matter. Keep uuid as the post identifier and thread.uuid as the thread identifier. Make sure your own deduplication doesn’t keep only the first record per thread and quietly bring the filter back. Write a regression fixture that shows two post IDs under one thread ID. The post warns: “Check the actual analyst-facing message, not the number of records in the database.”
On the Webz.io provider page, this story is about the Webz.io Cyber API, which carries the is_first filter and the thread model. It sits next to the Webz.io Data Breaches API, where alerts like the OBSOFT claims end up, and the Webz.io Firehose API for collectors that stream rather than query. The catalog records 13 API pages in total.
On the Kin Score, Webz.io measures 55.6, in the strong band. Access clarity is a perfect 100.0 and discoverability is 80.0. Contract quality is 0.0, and Agent Readiness (36.3, rated agent-ready) has spec presence and OpenAPI examples unlit. That’s the gap in this post. Webz.io explains the semantics of uuid versus thread.uuid more precisely than most providers document anything. But the explanation is in prose and in query syntax, with no machine-readable contract that a collector or an agent could validate against. A fixture can catch the regression the post describes. A published schema would let anyone see those two identifiers before writing the fixture.