Typed SDK
Use @alphayard/unibox-sdk for typed workspace, file, search, upload, folder, and related operations.
Obsi Drive · Developers
Use the same file layer—without an unlimited-cost API.
The typed SDK, REST API, and OpenAPI use the same workspace model as the app, while automated traffic is bounded separately from normal storage behavior.
Obsi Drive
developersOne canonical file layerSource-aware · protected when chosen · governed automationREST API
Use the /api/v1 surface for workspaces, files, folders, search, quota, analytics, and supported file delivery.
OpenAPI
Use the generated API document as a machine-readable reference for clients and tooling.
Cost guardrails
API keys, proxied transfer, and costly operations are bounded by plan limits, application circuit breakers, and optional spend caps.
→
Install @alphayard/unibox-sdk or use the REST API directly.
→
Choose a signed-in session or supported API key and explicit application/workspace context.
→
Configure an optional monthly cost cap before high-volume automation.
→
Start with list or search requests, then add uploads and delivery only as the workflow needs them.
npm
npm install @alphayard/unibox-sdkREST
GET /api/v1/workspaces/:workspaceId/filesSafety
costCap + transferLimit + scopedKeyAutomation stops at configured safety limits instead of silently creating overage.
Obsi Drive