Skip to main content

Curiosity

The Psychedex knowledge graph. Structured pharmacological data, subjective effect mappings, and harm reduction content: versioned, cited, and queryable.


the data

295
Substances
252
Effects
2,729
Interaction rules
10,149
Citations
12
Routes

how data gets in

Psychedex data flows through a multi-stage pipeline designed for accuracy and accountability. Source material is extracted from published literature and pharmacological databases, then structured by automated agents. Human editors review, edit, and approve all content before publication. Nothing reaches the site without editorial sign-off.

Every safety-critical value — dose ranges, interaction severities, toxicity assessments — requires two independent citations. Values inferred by AI are labeled as inferred in the database. Uncertainty is surfaced, never hidden.

01SourcesPublished literature, pharmacological databases, clinical reports, and field data from drug-checking services.
02ResearchAutomated agents extract structured data from source material and cross-reference against existing records.
03GenerationAI-assisted drafting produces article sections, dose tables, and effect profiles from extracted data.
04VerificationEvery safety-critical value requires two independent citations. Inferred data is labeled as such.
05EditorialHuman editors review, edit, and approve all content before publication. No auto-publishing.Pseudonymous contributor data — experience reports, dose corrections, effect observations — feeds back into content generation and adjustment. Contributors are never identified publicly.
06PublicationApproved content is versioned, tagged, and deployed. Previous versions stay readable at /substances/<slug>/history, and the evidence behind each value at /substances/<slug>/evidence.

what's inside

Psychedex organizes knowledge into four parallel content indexes. Substances cover material entities. Practices cover immaterial entities. Effects link them both. Frameworks provides the models and theories that contextualize conscious experience. The effects taxonomy is the common language that connects everything.

substancesIdentity table
commonNametextdisplay name
slugtextunique
psychoactiveClassenumstimulant, depressant, psychedelic...
statusenumdraft → published
currentVersionIduuid→ substanceVersions
substanceVersionsVersioned content
pharmacologyjsonbreceptor binding, metabolism
crossTolerancejsonbtolerance group data
dosageEntriesPer-ROA dose tiers
roaenumoral, insufflated, inhaled...
tierenumthreshold → heavy
minDosenumeric
maxDosenumeric
unitstextmg, µg, ml

curiosity API

Curiosity is the general-purpose data API. It exposes published substance and effect records as structured JSON — dose tiers by route of administration, interactions with severity, duration, tolerance, chemistry. These 7 endpoints serve production traffic today; each one requires an API key.

GET/api/v1/curiosity/substancesPublished substances, paginated. Identity fields only — no dose or interaction data.
GET/api/v1/curiosity/substances/{slug}One substance in full — classes, dosage, duration, tolerance, withdrawal, toxicity, dependence, chemistry, legal status, effects, interactions.
GET/api/v1/curiosity/substances/{slug}/dosageDose tiers for one substance. Every tier is keyed by route of administration; a dose without its ROA is not returned.
GET/api/v1/curiosity/substances/{slug}/interactionsInteractions for one substance — the same resolved set the substance page states: pharmacological class rules and curated pairs, approved rows only, one row per named partner. Every row carries its severity classification and its review status.
GET/api/v1/curiosity/effectsThe full effect taxonomy — name, slug, category, description.
GET/api/v1/curiosity/effects/{slug}One effect with the substances reported to produce it.
GET/api/v1/curiosity/interactions/checkPairwise interactions across a set of substances, each with its severity and review status.

a request

GET /api/v1/curiosity/substances?page=1&limit=50
Authorization: Bearer <your-key>

every response

{
  "data": { ... },
  "meta": {
    "version": "1.0",
    "generated": "2026-08-13T09:41:07.201Z"
  }
}
AuthAPI key, every endpointSend Authorization: Bearer <key>. There is no anonymous tier.
Getting a keyManual, private previewThere is no self-serve signup. Write to contact@psychedex.org with what you are building and we will issue a key or tell you we cannot yet.
Rate limit120 requests/minutePer IP, shared across every /api/v1 endpoint. The limiter runs before the key check, so an over-limit request returns 429 even with a valid key.
Over limit429 + Retry-AfterBody is {"error":"rate_limited"}. There are no X-RateLimit-* headers.
Success shape{ data, meta }meta carries version and a generated timestamp.
Error shape{ error: { code, message }, meta }Four codes: UNAUTHORIZED, BAD_REQUEST, NOT_FOUND, INTERNAL_ERROR.
VersioningIn the pathBreaking changes get a new prefix. /api/v1 stays as it is.
LicensingNot finalizedUser-contributed content is CC BY 4.0 (see Terms). A licence for the dataset as a whole has not been set, so treat reuse terms as open questions and attribute Psychedex.

the platform

Eight APIs are named. Two of them exist. The badge on each card says which, and the line under the description says what stands behind the name today — including the two whose capability already ships under a Curiosity path, and the four that are a reserved name and nothing more.

Curiositylive
General data API

Exposes published substance and effect records as structured JSON — dosage by route of administration, interactions with severity, duration, tolerance, chemistry.

Seven endpoints, key-gated.

Atlaslive
Jurisdiction-aware legal status

Returns scheduling and legal status for a substance in a named jurisdiction, plus the jurisdictions that have entries.

One endpoint, key-gated. Jurisdiction coverage is thin — most substances answer 'unknown' for most jurisdictions.

Nexuspartial
Multi-substance interaction checking

Checks interactions across a set of substances with severity ratings and mechanisms.

No Nexus route. Pairwise checking across up to 10 substances ships today at /api/v1/curiosity/interactions/check.

Prismpartial
Effects taxonomy

Cross-modal queries across the effects index.

No Prism route. Effect lookup and effect-to-substance links ship today under /api/v1/curiosity/effects.

Entityplanned
Substance name resolution

Resolves common names, brand names, and chemical identifiers to canonical substance records.

No route. Slug and PSX ID are the only accepted identifiers today.

Tracerplanned
Provenance and version history

Data lineage, editorial history, and version diffs for any content entity.

No route. Provenance and version history are published as pages instead: /substances/<slug>/evidence and /substances/<slug>/history.

Sentinelplanned
Real-time supply monitoring

Aggregates drug-checking results and alert data for contamination and adulteration warnings.

No route and no data sources contracted. See /sentinel for the design and scope.

Beaconplanned
Emergency response protocols

Substance-specific emergency guidance, symptom triage, and first-responder protocols.

No route. Emergency guidance is published as pages at /harm-reduction/emergency.

principles

Open to readEvery substance, effect, and interaction record is readable on the site without an account. The API is the gated path to the same records, not a paywall around them.
Citation-linkedEvery data value traces back to its source. Confidence levels are shown, not hidden. Uncertainty is stated, not glossed over.
Safety-critical data is never generatedDose values, interaction severities, and toxicity assessments come from cited sources or the existing database. AI-inferred values are always labeled.
Privacy-firstContributors are pseudonymous. Analytics are cookieless and aggregate-only — no persistent identifiers follow you. The user-contributor link exists only for moderation.
Versioned and stableAPI endpoints are versioned. Breaking changes get new version numbers and are announced before they take effect.

status

The 8 endpoints above are live and stable. Getting in is the part that is not: keys are provisioned manually while the program is in private preview. There is no signup form and no key dashboard — write to contact@psychedex.org. Substance data continues to be reviewed and published behind them.