Getting Started
April 16, 2026
Info
DSAR is currently in alpha. APIs, package surfaces, configuration, and documentation may change as the project evolves.
This guide is the fastest way to run DSAR locally, inspect the HTTP contract, and make your first request through the runtime.
Prerequisites
- Bun
1.3+ - A local checkout of this workspace
- One terminal for the runtime and one for callers such as the CLI or examples
Fastest Local Path
The quickest way to see the full surface is the kitchen-sink runtime plus the dashboard and subject-portal examples.
Supporting example READMEs:
examples/kitchen-sink/README.mdexamples/dashboard/README.mdexamples/subject-portal/README.md
Verify the Runtime
Once the runtime is up, inspect these endpoints:
GET /statusfor healthGET /spec.jsonfor the generated OpenAPI documentGET /docsfor interactive HTTP reference
If you mount DSAR at a base path such as /api/v1, the same endpoints become
/api/v1/status, /api/v1/spec.json, and /api/v1/docs.
Create Your First Request
CLI
Use DSAR_API_TOKEN when your runtime expects machine access credentials.
Node SDK
Choose the Right Runtime Surface
@dsar/backend: embed the HTTP runtime into your own service@dsar/node-sdk: call DSAR from server-side application code@dsar/cli: script or explore the HTTP surface from the terminal@dsar/core: selectmanaged,self-hosted,custom, orofflineclient modes behind a stable application-facing contract
See SDK and Runtime Modes for the comparison.
Next Steps
- Read Request Lifecycle for the end-to-end workflow
- Use API Reference for endpoint details
- Use Integration Guides to wire auth, storage, and inbound/outbound adapters