Sumanth(@Sumanth_077):I built a document agent with a live web-grounded decision engine! Decision models like Jev are powerful, but they don’t have live context by default. They can only reason over what they learned during training and the context you give them at inference time. That becomes a problem when you’re working with documents containing information that can change over time. An API referenced in a document could have been deprecated, a package or model recommendation could be outdated, or an instruction that was correct when the document was written may no longer work today. So I built an agent that checks these time-sensitive claims against the live web. I first use Agentic Document Extraction to parse the uploaded document while preserving its structure and content. From that extracted content, the agent identifies claims that are actually freshness-sensitive rather than sending every sentence for verification. For each claim, it keeps the original statement and the surrounding document context, then turns the verification into a decision task for Parallel’s Decisions API. Parallel searches the live web for evidence relevant to that specific claim and returns a grounded decision with supporting sources. The agent then maps the result into one of three states: - VALID: current evidence still supports the claim - OUTDATED: newer evidence contradicts or supersedes it - NEEDS REVIEW: the available evidence is not strong enough to make a reliable call For example, if an older document says: “Use API v1 for this integration.” the verification request includes that claim and its document context. Parallel can search the current API docs, check whether v1 is still supported, and ground the decision in the latest sources it finds. The final output keeps both sides together: the claim extracted from the original document and the current web evidence used to evaluate it. So instead of treating a document as static context, the agent can reason about which parts of it may have drifted since it was written. Github Repo: https://t.co/imsEHeUKdX This can be useful across technical docs, research reports, internal knowledge bases, implementation guides, product documentation, policies, and other documents where some claims remain stable while others age quickly.

2026.11.06 15:54

I built a document agent with a live web-grounded decision engine! Decision models like Jev are powerful, but they don’t have live context by default. They can only reason over what they learned during training and the context you give them at inference time. That becomes a problem when you’re working with documents containing information that can change over time. An API referenced in a document could have been deprecated, a package or model recommendation could be outdated, or an instruction that was correct when the document was written may no longer work today. So I built an agent that checks these time-sensitive claims against the live web. I first use Agentic Document Extraction to parse the uploaded document while preserving its structure and content. From that extracted content, the agent identifies claims that are actually freshness-sensitive rather than sending every sentence for verification. For each claim, it keeps the original statement and the surrounding document context, then turns the verification into a decision task for Parallel’s Decisions API. Parallel searches the live web for evidence relevant to that specific claim and returns a grounded decision with supporting sources. The agent then maps the result into one of three states: - VALID: current evidence still supports the claim - OUTDATED: newer evidence contradicts or supersedes it - NEEDS REVIEW: the available evidence is not strong enough to make a reliable call For example, if an older document says: “Use API v1 for this integration.” the verification request includes that claim and its document context. Parallel can search the current API docs, check whether v1 is still supported, and ground the decision in the latest sources it finds. The final output keeps both sides together: the claim extracted from the original document and the current web evidence used to evaluate it. So instead of treating a document as static context, the agent can reason about which parts of it may have drifted since it was written. Github Repo: This can be useful across technical docs, research reports, internal knowledge bases, implementation guides, product documentation, policies, and other documents where some claims remain stable while others age quickly.

Sumanth@Sumanth_077

2026.10.28 14:11

RAG for decision models is here! Parallel just launched the Decisions API, which combines live web search with bounded decision-making in a single call. Decision models like Jev are useful when the output is small and structured: yes/no, one option from a list, a category, or a routing decision. The problem is that those decisions are only as good as the context you give them. If the answer depends on something that changed recently, or information that only exists on the web, the normal flow becomes retrieval first and decision second. Parallel brings those two steps together. You provide the state and the questions you want answered. The API searches the web, grounds the decision in what it finds, and returns the typed answer along with probability, confidence, and sources. That makes it much more useful for agent workflows where a decision depends on current external information, research tasks where the model needs to verify something before choosing an outcome, or eval pipelines where the judgment needs grounding from the web. It can also answer multiple questions against the same retrieved context in one request, instead of repeating the search for every decision. So instead of: Search → retrieve context → decision model → structured answer you can make the grounded decision directly through one API. I think this is a pretty natural extension of where decision models are going: bounded outputs are useful, but giving that decision layer access to the live web makes the set of problems it can handle much larger.

커뮤니티로 전달