Definite documentation

Know what is ready.
Prove every check.

Agent labor. Deterministic checks. Independently verifiable evidence.

Definite connects your financial systems read-only and runs bounded agents across close, reconciliations, controls testing, and reporting — without write access to source systems or filing authority.

Python · readiness and receipts

Python
from definite import DefiniteClient

# reads DEFINITE_BASE_URL and DEFINITE_API_KEY
with DefiniteClient() as client:
    readiness = client.get_readiness()
    print(readiness.verdict_counts)

    for run in client.list_runs(limit=5).items:
        print(run.run_id, run.status)

    for receipt in client.list_receipts().items:
        print(receipt.rule_id, receipt.verdict)
System guarantees

3

Exact deterministic verdicts

Read-only

No source-system writes

Signed

Hash-chained rule receipts

SDK + API

TypeScript · Python · REST

How it works

One durable run. Five explicit stages.

Definite · ingest → map → check → investigate → assemble
01

Ingest

Read immutable snapshots from read-only connections, scheduled file drops, and uploads.

→
02

Map

Agents propose classifications and mappings with confidence and provenance; humans review.

→
03

Check

The deterministic engine emits PASS, FAIL, or CANNOT_VERIFY for every applicable rule.

→
04

Investigate

Agents gather evidence and draft explanations while humans retain judgment.

→
05

Assemble

Build workpapers, reports, and evidence packs with lineage back to source records.

Reference

Explore the docs. From inputs to signed receipts.

01

Getting started

The AI workflow layer for finance teams: read-only connections, bounded agents, deterministic verification, signed receipts.

02

Using the console

Overview, Reconciliation, Reconciliation Controls, Exceptions, Approvals, Evidence, Data, Mappings, and settings.

03

SDKs and integrations

Monitor readiness, runs, exceptions, and receipts from Node and TypeScript services with definite-ts.

04

API reference

Readiness, definitions, programs, runs, mappings, exceptions, sources, artifacts, and receipts.

05

How Definite works

Read-only connections, the Vault control plane, the agent runtime, the deterministic engine, and the console.

06

Security and audit

Signing keys, receipt chains, the Merkle audit ledger, and the step-by-step verification procedure.

07

Compliance

Signed, reproducible evidence packs with control-to-evidence crosswalks for named compliance frameworks.

08

Requirements

URLs, keys, read-only credentials, network paths, and operational agreements needed to go live.

09

FAQ

Common questions about verdicts, fail-closed behavior, data handling, models, receipts, and roles.