Skip to main content
CAIBots
CAIBots
CONFIDENTIAL · FOR AUTHORIZED PERSONNEL ONLY
SYNTHETIC DEMO DATA · NO REAL BORROWER PII · NOT LEGAL OR CREDIT ADVICE
Engineering Documentation · Credit Underwriting AI

Implementation
Guide

Credit Underwriting Agentic AI · V4.0

AudienceIT Engineering · LOS Integration Team · Model Risk Management ScopeLOS Connectivity · API Provisioning · Policy Upload · Model Validation · UAT Protocol Estimated EffortPhase 1: 3–5 Days Engineering · Phase 2: 5–10 Days (includes validation) PrerequisitesBAA Signed · LOS API Sandbox Access · Bureau Permissible Purpose Confirmed VersionV4.0 · July 2026
01
LOS Connectivity

Loan Origination System Integration

Step-by-step guide to connecting the CAIBots Credit Underwriting Pipeline to your LOS via REST API or webhook.
Supported LOS Platforms

Connector architecture for: nCino (Salesforce-based), Encompass, Finastra LaserPro / Mortgagebot, Baker Hill NextGen, FICO Origination Manager. Custom REST/webhook integration available for all other platforms. Average adapter deployment: 3–5 engineering days; full LOS integration is validated end-to-end across the 90-day pilot.

1
Step 1 · Credentials
Provision CAIBots API Credentials Required
CAIBots Customer Success Engineer provisions your institution's API key pair (client_id + client_secret) for sandbox and production environments. Keys are scoped to your institution and carry your bureau permissible purpose linkage.
Request sandbox credentials via your CSE or the CAIBots customer portal (provided at onboarding)
Store credentials in your institution's secrets manager (AWS Secrets Manager, Azure Key Vault, or HashiCorp Vault)
Never hardcode credentials in application code — strict policy enforcement
Production keys issued only after SR 11-7 validation sign-off and security review
2
Step 2 · Webhook or API
Configure LOS Trigger — Webhook or REST API Call
Two integration patterns supported. Choose based on your LOS capability:
# Pattern A: Webhook (LOS pushes to CAIBots on new application) POST https://api.caibots.com/v1/underwriting/trigger # Pattern B: Pull (CAIBots polls your LOS queue) GET https://api.caibots.com/v1/underwriting/pull/{los_queue_id} # Authentication: Bearer token (OAuth 2.0 client credentials flow) Authorization: Bearer {access_token} Content-Type: application/json
Webhook pattern recommended for real-time decisioning (nCino, Baker Hill)
Pull pattern for batch environments or LOS platforms without webhook support
All traffic over TLS 1.3 minimum · Mutual TLS available for high-security environments
3
Step 3 · Field Mapping
Application Data Field Mapping Required
Map your LOS application fields to the CAIBots standardized schema. Field mapping configuration is YAML-based and maintained in the CAIBots admin portal. Required fields by loan type are pre-defined.
# Example field mapping (YAML) — Consumer/HELOC loan_type: consumer_heloc borrower_ssn: los_field:applicant.ssn_masked # masked — 4 digits only loan_amount: los_field:loan.requested_amount property_address: los_field:collateral.address_full annual_income: los_field:applicant.income_verified loan_purpose: los_field:loan.purpose_code
CAIBots provides pre-built mapping templates for nCino, Finastra, and Baker Hill
Custom field mapping validated by CSE before production activation
SSN transmitted as masked (last 4) — full SSN never leaves institution boundary
4
Step 4 · Write-Back
Decision Write-Back to LOS Required
CAIBots writes the decision package back to your LOS automatically upon pipeline completion. Configure write-back endpoint and field targets in the admin portal.
Decision (Auto-Approve / Auto-Decline / Route-to-Officer) written to loan status field
Risk grade (1–10) written to risk rating field
Credit memo attached as PDF to document management system
Reg B adverse action notice queued in notice management system
Exception log written to exception tracking fields
Audit log reference ID stored in LOS for examiner cross-reference
02
Data Source Setup

API Key Provisioning — Source Tools

Institution-credentialed access required for each data source. CAIBots never holds your bureau credentials — keys are vaulted in your infrastructure and passed at runtime.
Source
Type
Provisioning Notes
MCO (Tri-Merge Bureau)
API · Bureau
Institution must have existing MCO relationship. Share permissible purpose code with CAIBots. Institution's API credentials stored in institution vault — never in CAIBots systems.
SBA SBSS Score
API · SBA
SBA lender credentials required. SBSS pull authorized by SBA 7(a) approval authority. CAIBots configures SBSS threshold at onboarding (default: ≥155 eligible).
CoreLogic AVM
API · Property
CoreLogic Direct API subscription required. Institution credentials vaulted. Confidence interval minimum configurable (default: ≥75%). Low-confidence routes to manual appraisal flag.
ATTOM Data Solutions
API · Property
ATTOM API subscription required. Provides deed, tax, and distress data supplementing AVM. No institution-specific credential linkage required — CAIBots platform subscription.
CoStar Group
API · CRE
CoStar institutional subscription or CAIBots platform access available. Required for CRE&I loan types. Institution may use existing CoStar relationship credentials.
GSFA / EDGAR / Finity
RAG · Financial
EDGAR is public API — no credentials required. GSFA and Finity accessed via CAIBots platform credentials. Institution uploads financial documents to secure document ingestion endpoint.
IRS 4506-C
API · IRS
Institution must be authorized IRS Income Verification Express Service (IVES) participant. Borrower consent captured at application. CAIBots submits request via institution's IVES credentials.
D&B Paydex
API · Commercial
D&B Direct+ API subscription required for commercial scoring. DUNS verification automated. Institution credentials vaulted.
Credential Security Architecture

All institution API credentials are stored in the institution's own secrets manager infrastructure. CAIBots implements a token-passing architecture at runtime — credentials are fetched from the institution's vault at execution time and never persisted in CAIBots systems. Full credential flow documentation available in the Security Architecture Supplement.

03
Policy Configuration

Credit Policy Matrix Upload & HITL Threshold Configuration

CAIBots operates on your institution's credit policy — not a generic model. Policy upload and HITL threshold configuration are performed at onboarding.

Credit Policy Matrix Upload

The credit policy matrix is uploaded via the CAIBots Admin Portal in Excel or PDF format. CAIBots parses the policy into a machine-readable rule set during onboarding. Policy versioning maintained — all decisions reference specific policy version at time of decision.

Policy matrix should include: FICO/score minimums by loan type, LTV/LTC maximums, DSCR minimums, concentration limits, maximum loan amounts by tier, and exception approval authority levels
Separate policy books supported by business unit (Community Banking, Commercial RE, SBA, etc.)
Policy updates processed within 24 hours — prior decisions not retroactively re-scored
Policy change audit log maintained for examiner review

HITL Threshold Configuration

HITL (Human-in-the-Loop) gates are configured during onboarding based on your institution's risk appetite and delegated authority framework. Default thresholds provided — customizable during Phase 1 calibration workshop.

# Default HITL threshold configuration (customizable) hitl_triggers: policy_exception_any: true # Any policy exception → HITL risk_grade_threshold: 6 # Grade ≥6 → HITL (pass/watch boundary) loan_amount_consumer: 150000 # Auto-decision limit: $150K consumer all_commercial_loans: true # All SBA/CRE/ABL → HITL always fair_lending_flag: true # Fair lending signal → HITL + FL officer covenant_breach: true # Portfolio breach → HITL for remediation
04
Model Validation

SR 11-7 Model Validation Protocol

CAIBots provides a complete model validation package. Institution's Model Risk Management function conducts independent validation before production authorization.

CAIBots Provides (Model Documentation Package)

Model Development Documentation (MDD) — agent architecture, training data sources, decision logic
Conceptual Soundness Analysis — agent design rationale and regulatory basis
Ongoing Monitoring Plan — KPI dashboard, drift detection, performance metrics
Backtesting Protocol — shadow-mode comparison vs manual underwriting, executed on the institution’s historical applications during Phase 1–2 (target sample: 500+)
Limitation Documentation — known boundaries, out-of-scope scenarios, edge cases
Parallel Run Comparison Report (generated during Phase 1–2 pilot)

Institution MRM Validation Steps

V1
MRM Review
Review Model Development Documentation
MRM Officer reviews CAIBots-provided MDD. Validates conceptual soundness of agent design. Documents findings in institution's model risk register. Target: 5 business days.
V2
Independent Testing
Independent Validation Testing (500-Application Replay Sample)
MRM or designated validator replays 500+ historical applications through the CAIBots sandbox (a 25-case smoke test may precede the full replay). Compares agent outputs to manual underwriter decisions using a statistically powered concordance methodology. Documents concordance rate, confidence intervals, and material differences.
V3
Sign-Off
MRM Validation Report & Sign-Off
MRM documents validation findings, conditions (if any), and issues conditional or unconditional approval. Approval required before production key issuance. Ongoing monitoring requirements documented.
05
User Acceptance Testing

UAT Protocol — Credit Officer Workbench

Structured UAT ensures the Credit Officer Workbench is validated across all loan types and user roles before production cutover.
Test Case
Category
Pass Criteria
Consumer HELOC Auto-Approval
Auto-Decision
Agent pipeline completes in ≤5s. Auto-approve decision with ECOA clear and LOS write-back confirmed. Reg B notice not required — approval notice generated.
Consumer HELOC Decline (Score Fail)
Auto-Decision
Auto-decline routed correctly. Reg B notice generated with FCRA reason codes within 2 business days. LOS status updated to Declined.
SBA 7(a) — Officer Workbench Routing
Commercial
Pipeline routes to Credit Officer Workbench (never auto-decision). Workbench displays full credit memo, SBSS score, financial spread, risk grade, and SBA eligibility status.
CRE&I — Collateral Valuation
Commercial
CoStar AVM or appraisal comparison displayed. LTV calculated against policy maximum. Low-confidence AVM (below 75%) triggers manual appraisal flag in workbench.
Policy Exception — HITL Required
HITL Gate
Any application with identified policy exception routes to Credit Officer Workbench with exception highlighted, severity score displayed, and justification prompt surfaced.
Fair Lending Flag — Dual Routing
Compliance Scope
Fair lending signal triggers simultaneous notification to Credit Officer AND Fair Lending Officer. Neither can approve without the other's sign-off captured in audit log.
Counteroffer — Near-Miss Structuring
HITL Gate
Below-policy DSCR at requested amount triggers agent capacity solve. Counter terms displayed in workbench; officer COUNTER action transmits terms, generates the Reg B counteroffer notice, and starts the 90-day acceptance window with automatic adverse-action finalization on expiry.
Committee Routing — Multi-Sign-Off
HITL Gate
Exposure above single-officer authority routes to Credit Committee. Three independent sign-offs recorded in the audit ledger before final action unlocks; the vote, execution writes, and post-write validation are individually logged.
HITL SLA — Escalation Path
HITL Gate
Gate SLA timer visible on every pending decision. On expiry, escalation notification dispatches to the CCO, the event is ledger-logged, and the gate remains open — no silent timeout, no auto-action.
Return to Analysis — Officer Loopback
HITL Gate
Officer RETURN action closes the gate without a decision, logs the return rationale, and re-opens the pipeline for a fresh run with updated inputs. No decision or notice is generated.
Decision Rationale — Mandatory Capture
Governance
Approve/counter/decline on any exception or flagged case requires a written rationale before the action commits; rationale text, role, and timestamp appear in the exported audit ledger.
DSCR Alert — Portfolio Monitoring
Portfolio
DSCR deterioration below threshold generates watchlist alert in LOS. Covenant breach generates HITL action item with remediation workflow prompt. Portfolio officer notified.
Maturity Renewal — Annual Review
Renewal
Updated financial spread generated from new documents. Risk grade migration displayed. Renewal credit memo assembled with prior-year comparison. Officer workbench surfaces for approval.
SR 11-7 Audit Log Export
Governance
Full audit log exportable in CSV/PDF for any date range. Includes agent execution sequence, data sources queried, decision rationale, and officer actions. Examiner-ready format confirmed.
LOS Bi-Directional Round-Trip
Integration
Application data received from LOS, processed, and decision written back to correct LOS fields within 5 seconds of pipeline completion. Field mapping validated for all required fields.
UAT Sign-Off Threshold

Production authorization requires: (1) All 15 UAT test cases pass with zero critical failures; (2) ≥90% user satisfaction score from Credit Officer UAT cohort (minimum 5 officers); (3) IT LOS integration validation confirmed by IT Lead; (4) Fair Lending Officer sign-off on compliance test cases. UAT results documented in the Phase 2 gate report submitted to MRM and CRO.

06
Infrastructure

Infrastructure Requirements

Minimum infrastructure requirements for hosting the CAIBots Credit Underwriting Pipeline in production.
Component
Environment
Specification
CAIBots Agent Runtime
Cloud / SaaS
Hosted in CAIBots cloud (AWS us-east-1 primary, us-west-2 DR). No on-prem agent runtime required. Designed to SOC 2 Type II control objectives; a formal Type II examination is on the security roadmap, and current security documentation is available under NDA. TLS 1.3 in transit · AES-256 at rest.
Institution Secrets Manager
Institution
AWS Secrets Manager, Azure Key Vault, or HashiCorp Vault required for API credential storage. CAIBots does not store institution API keys.
LOS Integration Layer
Institution / DMZ
Lightweight REST adapter deployed in institution DMZ or LOS environment. Handles webhook/pull connectivity. No inbound firewall rules required — outbound HTTPS only.
Document Ingestion Endpoint
Institution / S3
Secure S3-compatible document drop for financial statement upload. Institution-controlled bucket with CAIBots read-only cross-account access. Documents deleted after 30-day retention period.
Credit Officer Workbench
Browser / SaaS
Web-based. No install required. Supports Chrome, Edge, Safari. SSO/SAML 2.0 integration available (Okta, Azure AD, Ping). MFA enforced for all users.
07
Client Platforms

Client Platform & Device Strategy

Web-first by design: no endpoint software to install, package, or push through desktop-engineering review. Underwriting is a desktop-browser activity beside your LOS; mobile is an approval-and-alert surface, delivered as a responsive PWA in production. Native apps are a by-exception roadmap item — not a pilot or go-live requirement.
Surface
Phase
Specification
Underwriting Workbench — Desktop Browser
Pilot + Production
Primary surface for analysts, credit officers, MRM, and fair-lending review. Chrome / Edge / Safari (current and previous two majors). 1080p minimum; 1440p or dual-monitor recommended for memo + evidence side-by-side with the LOS. Zero install · SSO/SAML 2.0 · MFA enforced. The pilot requires only this row.
VDI / Thin Client
Pilot + Production
Citrix, VMware Horizon, and Azure Virtual Desktop supported — the workbench is a standard web application. Production build includes a reduced-motion rendering mode for constrained VDI graphics budgets.
Mobile Approval Surface — Responsive PWA
Production Phase 2+
Purpose-built for the away-from-desk moments in the governance loop: HITL approvals and declines, dual sign-off (Credit + Fair Lending Officer), committee sign-offs and votes, SLA-countdown escalation alerts, and covenant/portfolio notifications. Installable PWA with push notifications; read-optimized credit summary; per-action step-up authentication (WebAuthn / platform biometric); no borrower PII cached at rest on device; server-side session revocation.
Field Capture — Construction Draws
Roadmap
PWA camera capture for site-inspection photo evidence with geotag and timestamp, offline queue with sync-on-connect, feeding the draw-authorization evidence chain (Scenario 04 workflow).
MDM / BYOD Distribution
Production
Distributable through Microsoft Intune, Workspace ONE, or equivalent as a managed web app / PWA. Device-posture and conditional-access enforcement delegated to your identity provider; short session TTL on mobile; remote sign-out via IdP session revocation.
Native iOS / Android Apps
By Exception
Considered post-production on institution demand only — where managed-app-catalog distribution, deeper offline access, or OS-level push guarantees are hard requirements. Estimated 12–16 engineer-weeks plus ongoing dual-platform maintenance; the PWA covers the approval workflows without this cost. Not required for pilot or go-live.
08
Operations

Production Hardening & Operations Checklist

The operational disciplines that carry a pilot into steady-state production. Each item names its owner; none is a pilot blocker, all are go-live gates. Items marked [Reference] are substantiated in the linked documents rather than restated here.
Discipline
Owner
Go-Live Practice
Change Management & Rollback
CAIBots
Versioned releases with staged rollout; every policy-pack, calculation-engine, and rule change carries a version fingerprint stamped into decision records (see Architecture — policy hash). Rollback = redeploy prior version; decisions already written remain attributed to the pack that made them.
Monitoring & Alerting Handoff
Joint
CAIBots monitors runtime health and source-tool connectivity; institution receives webhook/e-mail alerts for pipeline failures, SLA escalations, and override-rate anomalies (the MRM drift signal). Alert routing configured during Phase 1 alongside LOS integration.
Incident Response
Joint
Severity-tiered response with defined acknowledgment SLAs in the pilot agreement; institution security contact named at kickoff; post-incident report with ledger extract for any event touching a credit decision. Degraded-mode behavior is by design: missing inputs abstain to a human (Scenario 15), they are never imputed.
Access Control & Reviews
Joint
Role-based access with least-privilege defaults (analyst / officer / fair-lending / MRM / admin); provisioning through the institution IdP (SSO/SAML, §06); quarterly access review export for the institution's user-access recertification process.
Key & Credential Rotation
Institution
All data-source credentials live in the institution vault (§02) and rotate on the institution's schedule; CAIBots reads at runtime and holds nothing to rotate. CAIBots-side service credentials rotate on a 90-day cycle.
Backup & Recovery
CAIBots
Multi-region posture per §06 (primary + DR region); decision records and ledger replicated cross-region; recovery objectives stated in the pilot agreement and tested before go-live with an institution-witnessed restore.
Vulnerability Management
CAIBots
[Reference] Annual independent penetration test and continuous dependency scanning per the security posture published at caibots.com/privacy#soc2; summary findings available to customers under NDA.
Log & Ledger Retention
Joint
Hash-chained decision ledger retained per the institution's DPA schedule (typically 7 years for banking records); operational logs 13 months; document retention 30 days (§06). Retention parameters set in the DPA, not in code.
Model & Rule Change Governance
Joint
Guardrail-rule and policy-matrix changes follow the institution's model-change process: proposed pack diff → MRM review → scheduled activation with new fingerprint → override-rate watch for the following cycle. The demo's versioned policy hash is this mechanism in miniature.