Every request in NoData is one of two things: compute a governed access decision, or verify one. Capsules, AI reads, documents, viewers and agents are adapters built on top of them.
compute() → decision + authorized view + proof
verify() → authentic + unalteredBase URL https://nodatacapsule.com/api/v1 · Auth Authorization: Bearer ndp_… · npm i @nodatachat/sdk
import { NoData } from '@nodatachat/sdk';
const nd = new NoData({ apiKey: 'ndp_...' });
// 1) compute — give information + intent + clearance, get a governed answer + proof.
const { decision, answer, proof } = await nd.compute({
question: 'What is the claim status?',
clearance: 'internal',
sections: [
{ title: 'Status', text: 'Claim status: approved. Region: Tel Aviv.' },
{ title: 'Client', text: 'Dana Cohen, ID 039821582, amount 42,500 NIS.' },
],
});
// "Client" (confidential) is withheld at internal clearance — never reaches the model.
// 2) verify — anyone, no key, no decryption.
const v = await nd.verify(proof.id); // → { authentic: true, unaltered: true }The billed unit: a governed access decision — decide, release only the authorized view, and sign it. One call.
POST /v1/documents/compute # information + intent + clearance → decision + proofGiven a decision proof id, confirm it is authentic and unaltered by re-verifying its signed hash-chain — third-party, no key, no decryption. Fail-closed: no proof is never "fine".
POST /access/verify # { proof_id } → { authentic, unaltered, ... }The actions that put you in control — never billed on purpose, so you can get your data governable without friction, then run decisions over it. Capsules are unlimited; revocation is free because turning access off is the action we want you to take without hesitating.
POST /v1/capsules · GET /v1/capsules · GET /v1/capsules/{id} # isolated environments
POST /v1/capsules/{id}/documents # seal a document in
POST /v1/capsules/{id}/members # people + access
POST /v1/capsules/{id}/ai-grants # what an agent may read
POST /v1/capsules/{id}/revoke # turn access off, instantly
POST /v1/recovery/pubkey · /copy · /event · GET /state # 12-word recovery + vault backup
GET /v1/overview · /v1/usage/invoice # your meterThe engines that power the adapters (blind relay, delivery, vault, channels) sit under nd.engines.* — you rarely call them directly. Microsoft 365, Google Workspace and sovereign deployment are the Enterprise plane — an expansion, not the entry.