Introduction

The platform serves two audiences from one system. For an engineer, it is a REST API: every advice decision is recorded into a tamper-evident hash chain, the result is signed, and the artefacts are exposed through webhooks and endpoints that wire into an existing pipeline. For a compliance officer, it is a permanent system of record, one the firm, its clients, or the FCA can inspect without trusting the firm not to have edited it after the fact.

Both views describe the same product. The technical decisions are the compliance decisions in code: append-only storage, hash-linked records, ECDSA P-256 signatures, and externally verifiable certificates.

What you will find here

• Getting Started: install the SDK, obtain an API key, submit a first record, and follow it into the ledger end to end.
• Concepts: the moving parts, namely the ledger, review, certificates, the governance layer, and firms and users.
• Features: the governance capabilities layered on top of the ledger, from the model registry to chain integrity.
• Reference: exhaustive tables for ledger event types, enums, webhook payloads, error codes, and the data model.
• Cookbook: worked recipes for the tasks firms build most often.
• Compliance: how each capability maps to a specific FCA rule, with citations.
• API Reference: every endpoint, parameter, and schema, generated from the OpenAPI specification.

How to read these docs

If you are evaluating the platform as a compliance officer, start with The Ledger, then The Governance Layer, then Regulatory coverage. Skip the code blocks.

If you are an engineer integrating the platform, start with Quickstart, then Authentication, then pick the cookbook recipe closest to what you are building.

If you already know what you are doing and just need an endpoint, jump to the API Reference.

The short version

Every advice decision flows through the API. The platform records it as an immutable entry in your firm's hash chain, optionally routes it to a human reviewer through Review, and, when the review is complete, issues a cryptographically signed certificate that anyone can verify with your firm's public key. The certificate is the proof, the chain is the audit trail, and the webhooks notify your other systems that it happened.

Everything else in these docs elaborates on those four steps.