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 stable parser
Tracking a release-notes page that's critical for your work? Email us with the URL and we'll add a deterministic adapter, usually 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.
Email info@devupdate.io with "Request a stable parser" in the subject
line and:
- The URL of the release-notes page.
- The package or product name.
- One or two example releases (link to a release on the page) so we can verify the parser against real data.
We prioritize requests by usage — sources tracked by multiple users move up the queue.