Underwritetenant/underwrite-demo
Role
Request a demo

Operator surfaces: queues, clocks, correspondence, billing.

Connectors, described by what they carry

This page names categories and interfaces rather than vendors. A logo wall would imply commercial relationships we would then have to keep true, and a compliance officer cannot audit a logo.

Connector identifiers are placeholders. Availability of a named vendor is confirmed in writing during implementation, never on a marketing page.

Categories
  • Correspondence
  • Despatch
  • Contracting
  • Billing
  • Access
  • Reporting
  • Events
  • INT-CRA

    Consumer reporting agencies

    Dispute despatch and results intake for nationwide consumer reporting agencies, by certified mail, by secure upload, or through the operator own submitted channel. Bureau identifiers in this demo are placeholders.

    Correspondence
  • INT-FUR

    Furnisher notices

    Records the date a notice of dispute is evidenced to a furnisher and the five business day agency obligation that precedes it.

    Correspondence
  • INT-MAIL

    Certified mail vendors

    Article numbers, acceptance scans and delivery events attach to the case as evidence, and the case state cannot advance without them.

    Despatch
  • INT-ESIGN

    Electronic signature

    Signature events return the document hash that was actually signed, which is the value the disclosure receipt stores.

    Contracting
  • INT-PAY

    Billing and payments

    Invoice creation is gated by the performance control. The payment processor never sees a charge the engine has not cleared.

    Billing
  • INT-IDP

    Identity provider

    SAML and OIDC single sign on, SCIM seat provisioning, and enforced separation between the review seat and the despatch seat.

    Access
  • INT-DW

    Warehouse export

    Scheduled, signed exports of cases, clocks and audit entries to object storage, in a schema that keeps the rule reference on every row.

    Reporting
  • INT-HOOK

    Webhooks

    Signed events for clock and control transitions, with a five minute replay window and per tenant secrets.

    Events

Evidence is the interface

Every connector exists to attach evidence to a case at the moment it is created rather than at the moment somebody remembers. Where a connector cannot produce evidence, the platform says so on the case instead of assuming the step happened.

  • An article number and an acceptance scan are attached before a despatch state is allowed to change.
  • A signature event returns the hash of the document that was actually signed.
  • A connector that goes down puts the case into a waiting state rather than a completed one.
POST /v3/webhooks

{
  "url": "https://ops.example/underwrite",
  "events": [
    "clock.started",
    "clock.extended",
    "clock.expired",
    "control.blocked",
    "document.delivered"
  ],
  "signature": "hmac-sha256",
  "replay_window_s": 300
}

Signed with a per tenant secret. Replays outside the window are rejected.

A mailroom counter with a squared-off stack of plain white envelopes, a postal scale and grey pigeonhole sorting shelves behind
Certified despatch is still paper at one end. The evidence is what has to be digital.

The full request and response shapes are on the API reference. If you need a connector that is not listed, it is an implementation conversation, not a roadmap promise:start there.