The decision this is for.
The proposed enterprise product is a permissioned dataset with a documented schema, original annotations and provenance. Its value would come from consistent experimental context and usable rights, not a claim to own public facts. A data product must exist and pass customer tests before a paid API or annual license is offered.
What the scoped deliverable includes.
Schema and field definitions
Source identifiers, dates, study model, endpoints, limitations and documented missingness.
Permissioned delivery
Contracted internal-use or integration rights and a clear distinction between annotations, public facts and third-party content.
Versioned records
Release identifiers and change handling so downstream applications can reproduce their evidence inputs.
Pilot acceptance tests
A sample dataset and agreed retrieval, coverage or integration tasks before annual access is expanded.
What we need to scope it.
The integration use case, fields, anticipated users, export or API needs, rights requirements and a test dataset specification.
How acceptance works.
Rights-cleared records and demonstrated usefulness on agreed tasks. No endpoint or service-level commitment is assumed until a working pilot is delivered.
Illustrative brief: an internal discovery dashboard needs versioned records linking a reported cell-state change to the model, measurement and source limitation.
Where the scope stops.
No live paid API is currently advertised as operating. No right to republish copyrighted articles, no guaranteed completeness and no ownership claim over public facts.
Before you inquire.
Can we buy API access immediately?
This is a design-partner invitation, not a functioning subscription endpoint. Delivery, rights and support must be established before sale.
Scope and proposed economics adapted from Karam’s 15 October 2026 commercial planning map. Prices are tests for a future written scope, not established sales, assured availability or verified willingness to pay. External sources do not endorse Karam.