The Psyntient Node · Node API
One API to consented neural data.
The Node API is how Applications, hardware, and AI systems talk to a user's Psyntient Node. The Node owns the connections to the user's Neural Vault and, with consent, the Noetic Archive — so you never have to.
Node API overview · Video coming soon
§ 01
What it is
The Node API is the stable programmatic surface every Application, device, and service uses to reach a user's Neural Vault and — with the user's explicit, revocable consent — the shared Noetic Archive. You call the API; the Psyntient Node enforces authentication, encryption, provenance, and consent on every operation.
The Node API is the programmatic surface of the Node. Its conversational counterpart — the Noetic Interface — is how humans talk to the same Node directly. Both are part of every Node.
§ 02
Who it's for
App developers
Ship an app on Psyntient once and it works with every user's Vault and, with consent, the Archive — no per-integration deals with device makers or storage providers.
Hardware developers
Register a device with the Node and its data lands in the user's Vault with consent and provenance intact from the first sample. Focus on the sensor, not on storage or auth.
AI labs
Request Archive-scale batches of paired neural + phenomenological data through the same API — versioned Editions, calibrated ground truth, and explicit contributor consent.
§ 03
How it relates to the stack
§ 04
Auth model
Every call carries a scoped access token issued by the user's Node. Scopes map to specific packets, sessions, or Vault capabilities, and can be revoked by the user at any time. Tokens never grant blanket access — access is always to this Vault, these scopes, for this period.
Full authentication docs land here as the SDK stabilizes.
§ 05
Endpoints overview
Recording
Open, stream, and close a live capture session against a connected device.
Docs coming soon
Observation Packets
Create, read, revise, and inspect Observation Packets in a user's Vault.
Docs coming soon
Vault access
Query the Vault under consent scopes — sessions, packets, notes, methods, analyses.
Docs coming soon
Archive query
Search neural archetypes, request exemplar packets, and pull versioned Editions.
Docs coming soon
Consent & provenance
Request, verify, and revoke consent; read the provenance chain of any packet.
Docs coming soon
Webhooks
Subscribe to Vault and Archive events — new sessions, consent changes, Edition releases.
Docs coming soon
§ 06
SDKs & quickstart
First-party SDKs for JavaScript/TypeScript and Python are planned; a Rust reference implementation of the Node is the source of truth for wire formats. A "hello, packet" quickstart lands with the first public SDK release.