ZooData

@Kyle Dong that three-lane breakdown (retryable / don't-retry / content-ok-but-degraded) is actually clearer than most APIs give you even without the granular attribution. makes sense you'd keep the fine-grained block signals internal rather than publish a map of exactly what trips detection. appreciate the detailed answer

Totally fair not to fake a null you can't stand behind. My pain sat one level below the semantics: `price` showing up in one response and vanishing from the next meant every field access in our agent needed a guard, since parsing code leans on a stable shape. If each page type always emitted its full key set with the value simply absent, that alone fixes the shape, and the sourced-vs-not flag you floated with Jernej could carry the did-we-check honesty on top. Does the fixed-per-page-type schema you mentioned to hazy already give me that stable key set, or can fields still drop out per call?

The pay-per-field pricing model is genuinely clever, it means agents only burn credits on what they actually need instead of paying for entire HTML dumps. Nice execution on the MCP server support too.

the auto-escalate-to-full-model-extraction when core fields fail validation is a smart fallback. if a site is mid A/B rollout and flips between old/new layout per request, does that thrash the escalation path back and forth before the new template locks in, or is there a cooldown so you're not eating full-model cost on every call during the rollout window?

the daily-cycle vs no-cache split for analytics vs realtime endpoints is smart, most tools pretend everything's live. does JS-heavy SPA rendering get priced the same as static pages or does that heavier compute cost more per call?

neat framing, agent-ready JSON instead of raw markdown. when a site restructures its page layout, does the schema auto-remap to catch the drift or does it silently break until someone notices the fields are empty?

The 75% token reduction claim makes sense structurally but I'm curious how it holds on pages where the most valuable data is buried in dynamic elements that only render after JavaScript executes , things like live pricing widgets, inventory counters, or seller ratings that load asynchronously. Is the JSON output pulling from the fully rendered DOM or the initial HTML response, because for e-commerce intelligence that difference is where the real data quality gap tends to sit.

Structured input is a better foundation for agents than making the model repeatedly interpret noisy pages. How do you preserve context that doesn’t fit neatly into the extracted schema but might become important to the agent later?

@Kyle Dong that's the right answer honestly, "we don't disguise a block as a success" is the thing that actually matters, most tools I've tried just eat the failure silently and you don't find out until your data looks wrong three steps downstream. does the response include which failure mode it hit, like captcha vs rate limit vs structure change, or is it just a generic fail code?

Great launch! The token math is the part that really matters, at least for agents. Paying to filter boilerplate out of 'clean' markdown is a tax you don't price in until the bill shows up! Wondering - when a site quietly ships a layout change or runs an A/B test, does that learned template keep mapping to the old fields and hand back a confidently wrong value?

curious how this holds up against anti-bot layers - a lot of the messiest sites to scrape aren't messy because of markup, they're messy because they actively try to block automated requests. does the per-field pricing still apply if a site just serves you a captcha wall instead of html, or is that a separate failure case

Skipping extra extraction credits and just paying for what you use is how all these tools should work. The included CLI makes it very easy to test the data formatting locally.

Any tool that helps agents work with structured data instead of messy web scrapes is a win. The included CLI is a nice touch for those of us who prefer working from the terminal.

Paying only for the fields used makes a lot of sense for data extraction.

Really glad to see an MCP server included from day one. It shows a deep understanding of current developer workflows and makes integrating this JSON extraction much more appealing.