The new Amass app is live. Ask in plain language, check every claim. Try it free

Answers are only as useful as the evidence behind them

Scientific intelligence you can verify.

Amass searches papers, clinical trials, drugs, genes, patents, regulatory records and the live web. Every answer stays connected to its sources, so you can inspect the evidence behind it.

Free plan, $0 forever. No card required.

One question, three ways in: the app with its trace and citations, an assistant calling the Amass tool over MCP, and the API returning the record.

Each answer cites the ID of the record behind it, such as a PMID, NCT ID or patent number, in the Amass app, in Claude and ChatGPT over MCP, or from the API.

A fluent answer is not a checkable one.

Amass returns each answer with its sources. Each claim carries an identifier that opens the record it came from: a DOI, an NCT ID, a ChEMBL ID, a patent number or a regulatory application number.

peer-reviewed papers
43M+
BioMedCore
scholarly papers
233M+
ScholarCore*
patent filings
170M+
PatentCore
one schema
FDA + EMA
RegulatoryCore
drugs & molecules
22K+
DrugCore
clinical trials
1.2M+
TrialCore
human genes
43K+
GeneCore
real-time web sources
Live
WebCore*

* In the app; the API and MCP serve the other six.

  1. 01ScatterYour sources sit on separate platforms
  2. 02DriftThe same question gets different answers over time
  3. 03ConvergeAmass traces each claim to the record it came from
  4. 04CiteEvery answer shows its sources, so the team shares one picture

Research holds the answer

Evidence is scattered across teams, tools and documents.

Reasoning drifts across data, teams and time.

Amass resolves it to the record. Every claim cited to source.

One question about a medicine can touch a journal article, a trial registry, a patent and a regulatory label, then the slides and emails a team writes about them. None of them links to the others.

Each answer starts from whichever documents someone found. A slide repeats one reading of a result, an email another, and the readings drift as they are copied forward. None says where its figure came from.

Behind every claim sits a record, held in the *Core for that kind of source. A slide or an email is not a record, so Amass reads it but never cites it.

JournalBioMedCore
10.1056/NEJMoa2413258
RegistryTrialCore
NCT04822181
PatentPatentCore
US-2025375504-A1
LabelRegulatoryCore
NDA 215256
SlideQ3 review, slide 12
not a source
EmailRe: MASH readout, v7
not a source

Each reference opens its record. What was read but not cited stays on a list of its own, so the team works from one picture it can check.

The platform

One evidence base for researchers, agents and apps.

One record, served three ways: as the app writes it, as the API returns it and as an MCP tool call fetches it. The app searches all eight *Cores; the API and the MCP serve six.

  1. Grounded research across every surfaceUse Amass in the app, through agents, or directly via API and MCP.
  2. One engine over eight *Cores*Cores for papers, trials, drugs, genes, patents, and FDA + EMA regulatory records.
  3. Every claim traceable to sourceAnswers, workflows and outputs stay linked to the underlying evidence.

Researchers

Apps & Agents

Developers

Amass8 *Cores

App

MCP

API

Amass *Core architecture

BioMedCore

43M+

ScholarCore

233M+

PatentCore

170M+

RegulatoryCore

7K+

DrugCore

22K+

TrialCore

1.2M+

GeneCore

43K+

WebCore

Live

Provenance & citations

External data providers

PubMedLiteraturePMCLiteratureCrossrefLiteratureUSPTOPatentsEPOPatentsWIPOPatentsSureChEMBLPatentsFDARegulatoryEMARegulatoryClinicalTrials.govTrialsWHO ICTRPTrialsHGNCGenes & moleculesEnsemblGenes & moleculesUniProtGenes & moleculesChEMBLGenes & moleculesWebWeb

Connect your own data

SharePointYour dataOneDriveYour dataGoogle DriveYour dataDatabricksYour dataS3 / BlobYour dataNetwork drivesYour data

See the three surfaces →

MCP

Inside the assistant you already use.

Amass runs inside Claude, ChatGPT, Claude Code and Codex over the Model Context Protocol (MCP). The assistant calls an Amass tool, and the answer comes back with the identifiers.

Set it up →

An assistant calling Amass’s TrialCore search tool, and the two trial records it hands back.

API

The same record, as a response.

Build on the engine with one REST API across six cross-linked *Cores. Each response is typed and carries the identifiers of its sources.

One trial record from the documented TrialCore records path, as the API returns it.

API docs →

Used by people at

  • Novo Holdings
  • ALK-Abelló
  • Rigshospitalet
  • Statens Serum Institut
  • Summit Therapeutics
  • Danish Cancer Society
  • BioInnovation Institute
  • Sound Bioventures
  • Innovestor
  • Acesion Pharma
  • Hervolution
  • Neurometa Therapeutics
Amass gives our investment team one place to validate science, patents, and trials, with citations we can stand behind in committee.
Luis Toledo

Luis Toledo

Senior Scientist, Novo Holdings SeedLab

Your research, cited to source.

Start free in the app or with an API key. Enterprise deployments add an SLA, single-tenant hosting and onboarding support.

Data
No training on your data
Hosting
EU-hosted, enterprise
Isolation
Tenant-isolated by architecture
Certification
ISO 27001, SOC 2, NIS2: in motion