Skip to main content
Institutions often ask: “Can we trust sharing signals with other banks?” This page answers that for legal, compliance, and fraud operations — before any technical integration.
Enrollment-first model: you can join and contribute approved signal types without purchasing network consumption (CLM-ADD-NET-C). Consumption is an optional second phase under contract.

​
Why enroll before consuming

Commercial incentive: eligible contributors may receive a 10 % discount on CLM-ADD-NET-C (consumption), per contract.

​
Clausum guarantees to your institution

Technical depth: Intelligence network integration guide · 28 signal types catalog (engineering: NETWORK_SIGNAL_CATALOG.md in repo).

​
What you control vs. what Clausum manages

1

1. Base contract

CLM-MOD-INST (Financial Hub) + Clausum onboarding — sandbox access.
2

2. Legal scoping

Agree which signal types appear in contribute_list_types (start with 3–5 types).
3

3. Enable contribution

Dashboard → Contribute to network · server key clm_sk_* or contributor key clm_cnt_*.
4

4. Pilot feed

POST /api/v1/network/intelligence from sandbox — validate normalization and revocation runbook.
5

5. (Optional) Consumption

Contract CLM-ADD-NET-C · assess matches peer signals above your trust threshold.

​
Signal catalog summary (28 types)

Legal can approve a subset for pilot. Groups:
Your institution commits to:
  • Publish only signals with agreed operational/legal basis (not experimental dumps).
  • Stay within approved contribute_list_types.
  • Maintain an internal revocation runbook for false positives.
  • Use server-side keys only — never embed secrets in client apps.
  • Name fraud and compliance contacts for the pilot.
Clausum commits to:
  • Never disclose your institution name to other network participants.
  • Never expose reason_detail cross-tenant.
  • Apply catalog normalization / hashing rules.
  • Enable immediate revocation of your signals.
  • Operate contributor trust score and staff audit.
  • Provide public docs, sandbox, and onboarding support (CLM-SVC-ONB).
Contractual details (DPA, retention, jurisdiction, SLA) are defined in the master agreement — this page describes product capabilities.

​
Pre-signature checklist

  • Approved signal types for contribution (explicit list)
  • Internal legal basis for each category
  • Named operational contact (revocation + escalation)
  • Pilot on sandbox.clausum.ai before production
  • (Phase 2) Decision on CLM-ADD-NET-C and initial min_trust_score

Integration guide

API, quick starts, troubleshooting

Bank segment

Financial Hub bundle

Payout assessment

SPEI / disbursement gate

API keys

Permissions and key prefixes
Support: api@clausum.ai