Skip to main content

Underwrite

Underwrite is the flagship Decision Platform call: given an entity and context, return who should get access or credit — and why.

Flow

1

Ensure the entity exists

POST /v1/entities (or retrieve by id). Keep your external_id stable.
2

Attach context

Identity links, consents, transactions, and feature snapshots as your program requires.
3

Call underwrite

POST /v1/underwrite with your product / program code and an Idempotency-Key.
4

Persist the record

Store id (decision id), verdict, reasons, recommended limit, policy version, and model version.
5

Monitor

Subscribe to webhooks and monitoring so material changes re-enter policy.

Sandbox example (founder-beta)

Illustrative sandbox-policy-v1 response for a business credit line request. Field names match the Decision API contract (packages/contracts + /v1/underwrite). Host status: founder-beta / coming online — use the base URL Vence issues for your org.
id is the decision id used in retrieve / replay / review paths. Decision evidence (feature snapshot, policy checksum, rule trace) is persisted server-side — retrieve it via GET /v1/decisions/{id}/replay, not as a free-form array on the underwrite body.

What you get back

  • Verdict (approve / approve_with_conditions / manual_review / decline)
  • Recommended limit (major units) when policy approves
  • Principal reason codes (with impact)
  • Conditions (when applicable)
  • Policy version, model version, and policy checksum
  • Confidence and repayment probability when the engine returns them

Retrieve and replay

  • GET /v1/decisions/{decision_id} — canonical decision
  • GET /v1/decisions/{decision_id}/replay — replay policy evaluation for audit
  • POST /v1/decisions/{decision_id}/reviews — human review
  • POST /v1/decisions/{decision_id}/outcomes — record real-world outcomes into the Trust Graph
Use Console → Playground to inspect the same decision a human operator sees.

What “good” looks like

You explain the decision to a risk committee without opening a black box. That is the product. See Sandbox decision flow for the full entity → features → policy → decision → replay → audit → outcome path with request/response examples. Also Entities, Decision Engine, Webhooks.