Skip to main content

What you get

Rows you can compute on: one row per extracted value, each carrying the conditions it was measured under and the excerpt it came from. Not a summary of papers — a dataset built from them. This is what teams reach for when abstracts are not enough: an aerodynamics group extracting mathematical formulas from full texts, a materials team collecting performance figures across test conditions, a clinical team pulling effect sizes for a meta-analysis.

Who it’s for

Engineering and physical-science R&D, and any research team assembling a quantitative dataset from published work.
Full-text excerpts (include_full_text_chunks) require a paid plan or an Enterprise API key, and currently cover open-access papers. Everything else on this page — search, filtering, metadata — works on any plan.

How it works

1

Fix the schema before extracting

Decide every column up front: the value, its units, the conditions it was measured under, the method, the sample or specimen, and the source. A schema settled mid-run produces a table you cannot pivot.
2

Phrase the query as the thing being extracted

Excerpts are selected for relevance to your query. Searching the paper’s topic returns introduction paragraphs; searching the measurement returns the results section. This single choice does more for extraction quality than anything else.
3

Set the domain, or drown

Without domain, technical terms pull in unrelated biomedical hits. domain=mat,eng,phys,chem is the difference between a usable and an unusable result set.
4

Keep every value with its conditions and its excerpt

A number without its test conditions is not comparable to another number. A number without its excerpt is not auditable. Both travel with the row.
5

Distinguish not-reported from not-extracted

Use different values for the two. Conflating them silently biases every downstream count.

The API call

Each result’s full_text_chunks holds query-relevant excerpts. Pair with metadata already on the result — doi, title, publish_year, journal_name, url — so each extracted row carries its provenance.

The extraction prompt

What to check before you trust it

  • Spot-check five rows against their excerpts. The excerpt column exists precisely so this takes two minutes rather than an afternoon.
  • Watch for silent unit assumptions. Values converted without an original-units column are the most common corruption in extracted datasets.
  • Check the CONDITIONS NOT REPORTED rate. If it is near zero, conditions are being assumed rather than read.
  • Coverage is not uniform. Full-text excerpts currently cover open-access papers, so a closed-access subfield will be under-represented. Check whether your topic skews that way before treating the dataset as complete.

Substantiate a product claim with published evidence

Turn extracted evidence into a defensible claim file.

Create a biomarker evidence report

The same extraction discipline inside a clinical evidence review.

Best practices

Excerpt-first extraction and the rest of the primitives.

All use cases

Browse the gallery by persona.