AIAny
AI Infra2026
Icon for item

AskChem: Claim-Centered Infrastructure for Chemistry Literature Synthesis

Indexes chemistry literature as provenance-bearing atomic claims and provides a faceted taxonomy, evidence graph, and REST/SDK/MCP APIs so researchers and AI agents can retrieve verifiable, claim-level findings across papers; live index contains 2.4M claims from 147K papers.

Introduction

Why this matters

Most literature-search tools return ranked documents, leaving humans and AI agents to find, verify, and synthesize specific results manually. AskChem flips the retrieval unit from the paper to the provenance-bearing claim: each paper is decomposed into small, typed assertions grounded by a source DOI and a verbatim quote or explicit evidence locator. That shift reduces citation hallucination for agent readers and makes it straightforward to assemble cross-paper answers that are directly verifiable.

Key Findings
  • Claim-level indexing at scale: the live index contains about 2.4M claims drawn from 147K papers (1925–2026), stored with full-text and vector indices to support fast retrieval and browsing. This makes fine-grained facts first-class search objects instead of buried sentences inside full papers.
  • Complementary retrieval structures: a stabilized faceted taxonomy for hierarchical browsing, an evidence graph that links supporting/contradicting claims, and source records with DOI and metadata; these structures let users traverse supporting evidence rather than chase whole documents.
  • Agent-first ergonomics and evaluation gains: AskChem exposes REST/SDK/MCP endpoints for agents; on a benchmark (AskChem-Bench) grounding a GPT-5.5 reader in AskChem raised resolvable DOI rate to 100% and substantially increased citation density versus unguided readers, demonstrating reduced citation fabrication and higher coverage of recent high-impact work.
  • Operational tradeoffs: the system favors verifiability and speed over exhaustive paper-level summarization; some complex experimental details remain easier to inspect in the original paper than in isolated claims.
Who It's For and Tradeoffs

Great fit if you need to assemble or verify quantitative findings across chemistry papers, instrument agent readers with provable evidence, or interactively browse a taxonomy of chemical claims. It simplifies workflows where traceable provenance and rapid cross-paper comparison matter (e.g., method/metric lookup, surveying catalyst performance, building grounded agent answers).

Look elsewhere if you need full-paper narrative synthesis, deep methods replication from unstructured methods sections, or maximal numeric detail tied to figures and tables without following evidence locators back to originals; AskChem is optimized for claim retrieval and provenance, not as a drop-in replacement for paper-reading during careful experimental reproduction.

Where It Fits

AskChem sits between document search engines and closed agentic research systems: more granular and verifiable than standard retrieval, more open and interactive than heavyweight closed pipelines. It complements RAG-style readers by supplying resolvable, source-anchored claims instead of whole-document snippets, making it particularly useful as an agent-facing retrieval layer.

Information

  • Websitearxiv.org
  • AuthorsBing Yan, Gregory Wolfe, Stefano Martiniani, Kyunghyun Cho
  • Published date2026/07/30

More Items

GitHub
AI Infra2026

Measures multiline text layout and block height without triggering browser reflow: it measures text segments once via Canvas+Intl.Segmenter and caches widths, then computes line breaks with pure arithmetic. Useful for streaming AI text, virtualization, and custom per-line rendering.

GitHub
AI Infra2026

Provides high-performance CUDA/CUTLASS kernels implementing Kimi Delta Attention (KDA), accelerating KDA prefill on SM90+ (Hopper) GPUs. Integrates as a drop-in backend for flash-linear-attention, supports native variable-length batching, and targets K=V=128; requires CUDA 12.9+/PyTorch 2.4+.

Measures how agent memory systems miss implicitly associated facts by introducing InMind, a 125-task benchmark with paired controls that separate stored-vs-retrieval vs knowledge gaps. Quantifies a large retrieval-interface blind spot and points to routing as the core open problem.