Parser stability
Reference table for parser tiers and how to request a deterministic adapter.
This page is the reference partner to Sources → Parser types. The conceptual explanation lives there; this page is the table you can scan when you're trying to figure out what tier a given source will land in.
Tier reference #
| Tier | Source pattern | Behavior on upstream breakage | LLM cost per poll |
|---|---|---|---|
| Stable | Has a purpose-built adapter (see catalog) | Returns zero entries with a logged warning | None |
| Best-effort (AI fallback) | Anything else | Returns whatever the model extracts; cached by content hash | Small per-poll, skipped on cache hit |
Request a deterministic tracker
Tracking a release-notes page that's critical for your work? Ask us to build a deterministic adapter and we'll usually add it within a few days. Adapters take roughly 50–150 lines of code each; the long pole is verifying the page structure stays stable, not writing the parser.
The fastest way is right in the product: open Add source, paste the URL, and when it routes to the best-effort (AI fallback) tier you'll see a Request a deterministic tracker button. Add an optional product name and a link to an example release, then submit. Your request is logged so we can prioritize by real demand (sources requested by multiple users move up the queue), and the team is notified.
Prefer email? info@devupdate.io with "Request a deterministic tracker" in
the subject and the URL, product name, and one or two example releases works too.