Customer developer docs

What is Definite

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

What is Definite

Definite is an AI workflow layer for finance teams. It connects your financial systems read-only — ERP and ledgers, banking and billing, data warehouses and BI, documents and spreadsheets — and runs bounded agents across finance workflows: close and reconciliations, controls testing, FP&A and variance analysis, billing and revenue integrity, and tax and compliance work such as regulatory reporting.

The division of labor is strict:

  • Agents do the labor. They map data, investigate exceptions, draft explanations and adjustments, and assemble workpapers and reports. Every agent action carries provenance.
  • Only the deterministic engine decides. A versioned rules engine emits every PASS, FAIL, or CANNOT_VERIFY. An LLM never decides pass or fail. Missing, late, or disputed input fails closed to CANNOT_VERIFY — never an assumed pass.
  • Humans keep judgment. FAIL and CANNOT_VERIFY findings become exceptions for human review. Agent drafts never auto-apply to anything a reviewer or auditor relies on.
  • Every check leaves a receipt. Signed, hash-chained receipts carry references and hashes — never raw sensitive values — and remain independently verifiable without Definite.

Definite is read-only by design: it never files on your behalf, never writes to source systems, and never initiates transactions. Client data is never used for model training.

Before you begin

  1. Sign up at app.usedefinite.com and complete onboarding: institution, entity and period, reports, and definitions. See the console overview.
  2. Connect at least one read-only source under Data, or work from uploaded documents.
  3. Create a tenant API key from Settings → API Keys if you integrate over REST or an SDK. Raw keys are shown once at creation.

Check readiness over the API

text
curl "$DEFINITE_VAULT_URL/v1/readiness" \
  -H "X-Vault-API-Key: $DEFINITE_VAULT_API_KEY"

Readiness is workflow metadata, not a verdict: verdict counts from the deterministic engine, active runs, open exceptions, missing inputs, ledger integrity, and per-program status.

Start a run

text
curl -X POST "$DEFINITE_VAULT_URL/v1/programs/program_call_report/runs" \
  -H "X-Vault-API-Key: $DEFINITE_VAULT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"idempotency_key":"quarter-close-2026-q2","trigger":"manual"}'

The request returns 202 with a queued run. Runs read from immutable source snapshots Definite already holds; the API does not accept raw source values.

What happens next

The run advances through five stages: ingest, map, check, investigate, and assemble. Only the check stage is the deterministic engine — its events carry actor_kind: deterministic_engine and never a model identity. Agent stages may label, investigate, draft, and assemble, but cannot emit or override a verdict.

Continue with your first workflow run for polling, stage telemetry, exceptions, and receipts.