Canonical static API · schema 1.1
Use the same typed records that generate the website
Numbers are numbers, booleans are booleans and not-assessed values are null. No API key, login, ranking or server-side inference is used.
Quick start
RESOURCE_BASE_URL="https://nmd-vcell.sema3c.chatgpt.site/resource"
curl "$RESOURCE_BASE_URL/api/v1.1/genes/ZNF133.json"
curl "$RESOURCE_BASE_URL/api/v1.1/core-gene/DMD"
curl "$RESOURCE_BASE_URL/api/v1.1/release_manifest.json"
curl "$RESOURCE_BASE_URL/api/v1.1/v1_release_gate.json"
curl "$RESOURCE_BASE_URL/api/v1.1/v1_external_authorization_dossier.json"
curl "$RESOURCE_BASE_URL/api/v1.1/prediction_readiness.json"
curl "$RESOURCE_BASE_URL/api/v1.1/prediction_registry.json"
curl "$RESOURCE_BASE_URL/api/v1.1/scientific_program.json"
curl "$RESOURCE_BASE_URL/api/v1.1/dmd_minimum_perturbome.json"
curl "$RESOURCE_BASE_URL/api/v1.1/generalization_ladder.json"
curl "$RESOURCE_BASE_URL/api/v1.1/gene_bucket_manifest.json"Complete-gene access
Every one of the 17,921 genes has a server-rendered /resource/gene/{symbol} page and a compact /resource/api/v1.1/core-gene/{symbol} JSON response. Use gene buckets for complete bulk records and identifier mapping for HGNC symbols, aliases and external IDs. The 123 detailed audit records also have individual JSON files.
Prediction-readiness gate
/api/v1.1/prediction_readiness.json is the machine authority for P0/P1/P2 claim status. It explicitly permits infrastructure claims, locks research-use DMD prediction until external perturbation validation exists, and locks clinical prediction outside this release.
State-transition research contracts
scientific_program.json defines the Competition Generalist and DMD Scientific tracks, dmd_minimum_perturbome.json defines the draft 24-slot pilot, and generalization_ladder.json separates G0–G7 tasks. registered_studies.json and experimental_outcomes.json are intentionally empty until immutable studies and measured outcomes return through the governed workflow.
Scientific program · Minimum Perturbome · Generalization ladder
v1 release and prediction-registry gates
/api/v1.1/v1_release_gate.json is the machine authority for formal v1.0 database-resource readiness, /api/v1.1/v1_external_authorization_dossier.json tracks DOI/licence/maintainer inputs, and /api/v1.1/prediction_registry.json preserves the empty prospective prediction registry. v1.0 is a database and evidence-governance release; it is not a validated disease-prediction or clinical decision-support release.
Read v1 gate · Read authorization dossier · Read prediction registry
Error semantics
The static API publishes a machine-readable error catalogue. A missing static asset can be returned by the host without a JSON body; clients must use the HTTP status as authority and must not infer “assessed no hit” from 404.
Legacy API v1
/api/v1/ is a compatibility surface with historical string-encoded fields and nested v0.6 records. New integrations should not start there. Its canonical successor is /api/v1.1/.