API Roadmap and Changelog
What we're building next for the Amass Platform API, and what has shipped so far. This page tracks the public REST API only — the changelog below does not cover the MCP server or the Amass app.
Have a feature request or want something prioritized? Reach out at support@amass.tech.
Upcoming
Not in any particular order, and subject to change based on user feedback and evolving priorities.
- ALWAYS: optimizing retrieval quality, performance, and cost.
- Extend change detection to the remaining Cores — update/creation dates and a change feed, as now shipped on TrialCore, BiomedCore and RegulatoryCore.
- TrialCore: structured readouts, biomarkers, and more.
- New Core: diseases/indications
- Preprints, conference abstracts, and other non-journal biomedical literature
- Paper supplements and other grey literature
- Molecular data
API Changelog
User-facing changes to the public REST API (/v1), grouped by month, newest first.
September 2026
- 🔄 RegulatoryCore change feed —
GET /v1/cores/regulatorycore/changesreturns the FDA and EMA authorizations created, updated, or deleted in a window, so a local copy can be kept in sync without re-reading the corpus. Both agencies ride one feed and one cursor; it also catches revisions to a record's parsed labels, reviews, SmPCs and EPARs. Same shape and cursor semantics as the TrialCore and BiomedCore feeds. See RegulatoryCore. - 🕓 RegulatoryCore create and update dates — records now return
createDate(when the record entered Amass, distinct from when it was authorized), andlastUpdateDatenow reports when Amass last wrote the record rather than an agency-reported date. Filterable withminCreateDateandmin/maxLastUpdateDate. The agency's own dates stay available asauthorizationDate,fdaDetails.labelDateandfdaDetails.withdrawalDate. See RegulatoryCore.
August 2026
- ⚡ Faster search — BiomedCore and TrialCore keyword search responds about 50% faster. Request and response shapes are unchanged. Retrieval speed and quality stay an active work item, so expect more entries here.
- 🏷️ Better drug-name matching — TrialCore already matched some alternative drug names; it now covers many more compounds and holds up on the development codes and brand names it used to miss. See TrialCore.
- 🎯 Scoped change feeds — both feeds now take an optional
amassIdparam (repeat it, max 100) and report only those records, so an app tracking a watchlist no longer has to page the whole corpus to find it. Every guarantee is unchanged: deletions, results revisions and removed outcomes still surface, which is what polling a date filter on search could never do. Cursors are bound to the set they were issued for. See TrialCore and BiomedCore. - 🔄 BiomedCore change feed —
GET /v1/cores/biomedcore/changesreturns the publications created, updated, or withdrawn in a window, so a local copy can be kept in sync without re-reading the corpus. Same shape and same cursor semantics as the TrialCore feed. See BiomedCore. - 🔄 TrialCore change feed —
GET /v1/cores/trialcore/changesreturns the trials created, updated, or removed from their source registry in a window, so a local copy can be kept in sync without re-reading the corpus. One feed and one cursor covers all three; page untilnextCursorisnull. It also catches revisions to a trial's posted results, which leave the trial record itself unchanged. See TrialCore. - 🕓 BiomedCore create and update dates — records now return
createDate(when the record entered Amass, distinct from when it was published) andlastUpdateDate(when Amass last wrote the record). Filterable withminCreateDateandmin/maxLastUpdateDate.createDatematches the value the change feed reports, so a feed item can be reconciled against a record without a fetch. See BiomedCore.
July 2026
- 🔗 PatentCore → BiomedCore links —
GET /v1/cores/patentcore/records?include=referencesBiomedCoreresolves literature to BiomedCore Amass IDs (AMBC_…), linking each patent to the papers it references. Adds to the existinginclude=referencesDrugCorecross-link. See PatentCore. - 📜 PatentCore published (preview) — full-text search over title, abstract, claims, and description, plus structured filters (jurisdiction, CPC/IPC classification, assignee/inventor, dates, citation count), get-by-id, and batch lookup by publication/application/family id. Search collapses each patent family to its highest-ranked publication, and records carry citation lineage and cross-links to DrugCore and BiomedCore. See PatentCore.
- 🌍 International clinical trials — TrialCore now covers non-US trials from the WHO ICTRP (national registries such as EUCTR, ChiCTR, JPRN, and ISRCTN) alongside ClinicalTrials.gov. Every record carries three provenance fields —
registryId(the source-registry native id, populated even whennctIdis null),sourceRegistry, andsourceUrl— so you can identify and trace where each trial came from. The lookup endpoint also acceptsregistryId, so non-US trials can be resolved by their native id. See TrialCore.
June 2026
- 🧬 GeneCore published — 43K+ harmonized gene records from HGNC, NCBI, UniProt, and Ensembl: keyword search across gene symbols, names, synonyms, and gene families with a multi-value
geneTypefilter, get-by-id, and batch lookup that resolves common public gene IDs (Ensembl, NCBI Entrez, UniProt, HGNC, and more) to Amass IDs. Target genes are enriched with profile data (drug tractability, curated safety liabilities, population genetic constraint, and cellular essentiality), and records link to DrugCore viainclude=referencesDrugCore. See GeneCore. - 🔗 TrialCore → DrugCore links —
GET /v1/cores/trialcore/records?include=referencesDrugCorereturns the Amass IDs of DrugCore records (drugs) associated with each trial. - 🎯 DrugCore mechanisms of action — drug records now return
mechanismsOfAction[]with action type, target type, and resolved gene targets (Ensembl id, symbol, name, synonyms), plus an opt-ininclude=referencesGeneCorelink to the upcoming GeneCore. See DrugCore. - 🔎 RegulatoryCore full-text document search —
GET /v1/cores/regulatorycore/records?query=now searches the parsed full text of FDA labels, FDA reviews, EMA SmPCs, and EMA EPARs; matching records returndocumentSections[]excerpts with addressable section ids. See RegulatoryCore. - 📄 RegulatoryCore document sections — record responses include a section table of contents, and
GET /v1/cores/regulatorycore/records/{amassId}/document-sections/{documentSectionId}fetches a single parsed section with its full content. - 🏛️ RegulatoryCore published — cross-agency FDA + EMA drug authorizations on a shared schema: search with multi-value filters, get-by-id, batch lookup, cross-market links, and
include=fdaDetails/emaDetails/referencesDrugCore. See RegulatoryCore. - 💊 DrugCore published — drug records with search, get-by-id, and batch lookup; multi-value
drugType/maxClinicalStagefilters; and cross-core references to trials, publications, and regulatory records. See DrugCore. - 🎚️ TrialCore multi-value enum filters —
phase,overallStatus,studyType,sponsorType, andinterventionTypeaccept repeated values (OR within a filter, AND across filters). See TrialCore.
May 2026
- 🐛 BiomedCore search relevance boost — keyword search no longer returns off-topic records boosted by journal quality.
- 💳 Clearer out-of-credits errors — responses now state explicitly when your organization has run out of API credits.
- 👥 BiomedCore author & institution filters —
authorOrcids,authorNames,institutionRors, andinstitutionNamesonGET /v1/cores/biomedcore/records. See BiomedCore. - 🧾 Credit cost header — every billable response carries
X-Amass-Credit-Cost. See Pricing. - 💰 Credits balance endpoint —
GET /v1/credits/api-creditsreturns your organization's remaining API credits.
April 2026
- 🚀 Public API launch — BiomedCore opens the platform:
GET /v1/cores/biomedcore/recordssearch, get-by-id, and batch lookup over enriched biomedical literature. See BiomedCore. - 🧪 TrialCore — clinical trial records with rich filtering, get-by-id, and batch lookup. See TrialCore.
- 🔗 Cross-core references —
references/citedBywithin BiomedCore, plusreferencesTrialCore/referencesBiomedCorelinks between the two Cores. - 💳 Usage-based credits — per-request billing with the credit system behind Pricing.
- 📚 Developer docs — interactive API reference, this documentation site, the
/capabilitiesdiscovery endpoint, andllms.txtfor AI agents.