TypeScript SDK and Golden Paths

Start from regulated upload, litigation hold room, external evidence share, chain-of-custody export, and permaweb publish flows instead of assembling 39 API surface groups from scratch.

Generated from OpenAPI plus high-level helpers for profiles, traceability, and connectors. Works in Node and browser with retries and typed errors.

Make integration feel like product onboarding, not protocol archaeology.

The TypeScript SDK shortens the path from evaluation to production. It turns the growing API surface into a typed client with helpers for the flows customers actually need first.

Value

Lower time-to-first-integration

Typed calls, retries, and curated helpers reduce the amount of custom glue code teams write before shipping.

Keep docs and runtime aligned

When OpenAPI, embedded docs, and the SDK move together, customers trust the platform surface more quickly.

Improve platform credibility with engineers

A good SDK makes the product feel intentionally built for teams that integrate from code, not only from demos.

For operators

  • Use generated client coverage for breadth and higher-level helpers for profile, trace, and connector workflows.
  • Pair SDK examples with the docs collection so implementation and reference material tell the same story.
  • Use the SDK as the cleanest path for partner engineering teams that do not want to build raw HTTP wrappers.

For buyers

  • Useful for platform engineers, solution architects, and partners evaluating implementation effort.
  • Helps convert technical evaluation into adoption because the integration path feels shorter and safer.
  • Supports a stronger enterprise narrative around maturity, maintainability, and developer experience.