SettleSignal Verified settlement intelligence

Data licensing

Verified settlement intelligence, as data.

Every field is traced to an official source — court orders, settlement administrators, and government refund programs — re-checked on a schedule, and delivered as a clean API. You get a fresh, verified settlement feed with the full evidence trail behind every value, so your product can cite provenance instead of guessing.

Talk to us How we verify →
26 verified settlements
522 field-level citations
96% avg verification confidence
Jun 7, 2026 last verified

Who it's for

Built for teams shipping money-back products.

Claim-filing & consumer apps

A fresh, verified feed with deadlines, eligibility, and proof requirements, plus the official claim destinations. Route users to the right official form with confidence the details were checked against the source record.

Fintech & money-finding products

Surface "you may have money waiting" features backed by provenance, not scraped rumors. Each settlement carries the evidence trail your compliance and risk teams will ask for.

Law firms & administrators

Monitor the settlement landscape with court-grade citations: case and court details, administrator, deadlines, and the payment-status lifecycle, each traced to an official document and re-checked on a schedule.

What you get

The full record, plus the evidence behind it.

Every field

  • Claim deadline, plus exclusion and objection deadlines
  • Eligibility summary and class period
  • Proof requirement and estimated payout text
  • Case name, case number, and court
  • Settlement administrator
  • Payment-status lifecycle

Per-field provenance

  • Evidence source URL for the value
  • The exact supporting snippet from the document
  • Confidence score and verification tier
  • Verified and last-checked timestamps
  • Source-document type and content hash

The differentiator: public pages show the named authority only; the licensed API carries the full evidence trail — the source links, snippets, and document hashes we use to verify each field.

Sample

One field, with its provenance.

A single field_provenance entry from the detail endpoint. Evidence URLs are masked in this public sample; the full URLs are part of the licensed payload. 

{
  "field_name": "claim_deadline",
  "value": "2026-09-01",
  "source_url": "https://…full-url-in-licensed-api…",
  "source_snippet": "Claims must be submitted by September 1, 2026 to the …",
  "confidence": 95,
  "verified_at": "2026-06-05T14:22:08+00:00",
  "last_checked_at": "2026-06-05T14:22:08+00:00",
  "document": {
    "type": "long_form_notice_pdf",
    "url": "https://…full-url-in-licensed-api…",
    "fetched_at": "2026-06-05T14:21:55+00:00",
    "content_hash": "sha256:9f2c…e1a7"
  }
}

Download sample (JSON)

Integration

A small, read-only API.

  • GET /api/v1/settlements/ — paginated list of verified records
  • GET /api/v1/settlements/<slug>/ — full record with per-field provenance
  • GET /api/v1/meta/ — dataset metadata and live metrics
curl https://settlesignal.com/api/v1/settlements/ \
  -H "Authorization: Bearer ss_live_EXAMPLEKEY"

Authenticate with an Authorization: Bearer header or X-API-Key. Keys are issued per partner and are revocable; rate limits are set per contract.

Tell us what you're building.

Licensing is handled directly — no self-serve billing. Describe your use case and the fields you need, and we'll scope access and a sample for your team.

Talk to us