Ideal for products that need fast iteration without losing type safety. TypeScript SDK

Typed protocol flows for product surfaces, tooling, and event-rich interfaces.

The TypeScript SDK helps teams expose Poiva through dashboards, developer tools, admin experiences, and browser-based operations while preserving protocol intent.

What this page covers

Expose resource contracts consistently.
Make event payloads easy to inspect and replay.
Keep browser and server runtime concerns explicit.
Design for rich tooling and observability.
Highlights

Protocol-native entry points for this surface.

Typed clients

Model protocol resources and events across web and Node.js environments.

See concepts

Event-friendly

Useful for reactive UIs, event streams, and workflow tooling.

See MCP

Extension-ready

Support domain profiles without mutating core protocol semantics.

Read spec
TypeScript-first flow ts
const mission = await poiva.missions.create({...});
await poiva.evidence.attach(mission.id, evidence);
const verification = await poiva.verifications.evaluate(mission.id);
Working principles

Keep the protocol stable while implementations evolve.

Expose resource contracts consistently.
Make event payloads easy to inspect and replay.
Keep browser and server runtime concerns explicit.
Design for rich tooling and observability.
Related pages

Continue through the public protocol surface.

Contribute

Help shape future SDK conventions and extension design.

Join discussion
Next step

Protocol clarity matters in fast-moving products too.

TypeScript implementations can evolve quickly, but the protocol surface should remain stable enough for other systems to understand.