Build on the Validiti stack over standard, signed APIs. You call sealed products; you never touch the engine.
- Genesis speaks the S3 API — point any S3 client at your endpoint.
- The AI speaks the OpenAI API — change one base URL, keep your code.
- A small signed REST surface covers compute, identity, and intake screening.
Every response carries a signed receipt binding the result to the exact records it came from — verify it offline, no call-home.
Program to it, not into it. Each capability is a sealed, signed binary running on your hardware or your instance. There is nothing of ours to
import, and no way to see how it works — only what it returns.
docs/storage.md— S3-compatible storage (Genesis)docs/ai.md— OpenAI-compatible + grounded answers (/ask,/sense)docs/rest.md— signed REST (/compute,/verify,/intake,/health)docs/receipts.md— verifying the signed receiptdocs/access.md— getting credentials (contract is access)schemas/— request/response examplessdk/python/·sdk/js/— thin HTTP clients (zero engine, just convenience)
Authorization: Bearer <YOUR_KEY>
Your base URLs ($VALIDITI_S3, $VALIDITI_AI, $VALIDITI_API) come with your access — on-prem or hosted.
This is a preview. Live credentials and the sealed on-prem binary are issued under a development agreement.
See docs/access.md. Public self-serve keys are coming soon.
The docs and the thin client SDKs in this repo are MIT (see LICENSE). The Validiti engine and
services are proprietary and delivered separately as sealed, signed binaries — they are not in this repo and
never will be.