Customer developer docs

Integrate,
operate, and
verify Ledgix.

Every agent action. Human-authorized. Cryptographically proven.

Start with the customer setup path: create an API key, add policy content, tune manual review, wire the SDK into one sensitive tool, and only then move into advanced API and verification work.

Start integrating →Book a Demo
01 — Sections

Explore the docs. Pick where you are in the integration.

01

Getting started

Create your API key, add policy content, set review controls, and run your first guarded request.

02

SDK guides

Add Ledgix to Node, Next.js, LangChain, and Vercel AI flows with one customer-facing example path.

03

Setup and operations

Upload files, paste text, register rules, or import Confluence pages so Ledgix can evaluate real customer requests.

04

API reference

Reference the customer-facing endpoints for clearance, polling, policy registration, settings, reviews, and verification.

05

How Ledgix works

See where the dashboard, SDKs, direct API, and optional gateway fit around your application and tools.

06

Security and audit

Learn what tokens, JWKS, checkpoints, and proof bundles mean in customer-facing terms.

07

Compliance frameworks

Status matrix for every framework Ledgix maps to today, plus how to export a signed evidence pack.

08

Requirements

Know which URLs, secrets, network paths, and gateway decisions your team needs before going live.

09

FAQ

Common questions from customer engineering teams about setup, approvals, reviews, and verification.

02 — Customer path

Three steps. Day-one setup, one guarded tool, then the review workflow.

  1. 01

    Set up your tenant

    Use the customer dashboard to create an API key, upload or import policy content, and set your starting review threshold.

  2. 02

    Guard one sensitive tool

    Wrap the exact action you care about with the TypeScript SDK, Python SDK, or a direct request to the Ledgix API.

  3. 03

    Operate the review workflow

    Handle approved, denied, and pending-review responses, notify reviewers, and use proof APIs when you need advanced verification.

03 — What these docs optimize for

A real first implementation. Not a tour.

Audience

Customer engineering teams

These pages assume you are new to Ledgix. They explain the parts you configure and call directly, not how Ledgix is hosted internally.

Main path

Set up, guard, review

Opinionated on purpose: set up the tenant, upload policies, integrate one guarded payment or refund action, and verify manual review works before expanding.

Advanced

Audit & verification

Proof bundles, checkpoints, JWKS, and token verification — documented and positioned after day-one setup, not in front of it.