The docs are coming.

We are writing the Clarent developer documentation now. The site will go live alongside the public release of the TypeScript SDK and the policy rule catalogue.

If you are an engineer evaluating Clarent today and you want technical detail before the public docs ship, we will share a walkthrough, a private draft of the SDK reference, and a sample audit pack with you directly. Most evaluation calls cover this within the first 30 minutes.

You can request that conversation from the Pricing page, or read How it works first if you would prefer the architectural overview.

What will live here

The Clarent documentation will cover four areas.

SDK reference

Installation, configuration, the decorator and context-manager APIs, span schema, and recipes for common agent frameworks. Python first, then TypeScript at parity.

ii.

OTLP transport spec

The exact span schema Clarent expects, including required and optional fields, PII scrubber configuration, and how to integrate without replacing your existing OpenTelemetry stack.

iii.

Policy rule catalogue

Each of the fifteen regulatory rules, the framework it maps to (Consumer Duty, SMCR, SS1/23, FG21/1, DUA Act 2025), the verdict statuses it produces, and the underlying chain conditions evaluated.

iv.

Dashboard and audit pack APIs

Authentication, firm-scoped query endpoints, the structure of generated PDF audit packs, and the verdict-record signature verification protocol.

In the meantime.

If you need technical answers now — about integration, schema, governance assumptions, or anything else an engineer would normally find in docs — get in touch and we will reply within one business day with the level of detail you would expect from a published documentation site.