For Lenders
Area scoring with the methodology version on every response.
Every response is stamped with the methodology version that produced it, every release is published with what it moved, and every value names its source. Built for underwriting that has to show its working.
Built for regulated underwriting
Four things model risk signs off.
Cite the methodology version behind every number, score the book in bulk, watch it drift, and keep every percentile scoped to its own nation.
Versioned methodology
Every response carries the methodology version that produced it, and every release is published with what it changed.
Bulk-score the book
Map up to 1,000 records in one call, or 20,000 as a job, and score the whole portfolio.
Track drift on the book
Prove you knew on the day a tracked area moved. Sample-size gated, signed on delivery.
Country-scoped percentiles
England, Wales and Scotland use different indices. We never manufacture a cross-border rank.
Why it survives audit
Made to be defended, line by line.
Your auditors ask how every number was made and whether it still holds. The answer is in the response.
Versioned and published
The version is on every response. A release that moves a figure is published, and Monitor labels it a method change.
Plan-replayable AI
Every query echoes the executed plan. Replay it and the same plan runs again, no model in the loop.
Sample-size honest
Change detection is gated on transaction count. Thin evidence never fires a false alert.
Frequently asked
Questions your model risk team asks first.
How do we track methodology versions?
Every response body carries the methodology version that ran, and the changelog lists every release with the figures it moved. Store the response version with your decision; a change in a watched portfolio caused by a later release is labelled as a method change.
Can we replay an AI-assisted query for audit?
Yes, this is the core audit contract. Every query returns the executed plan alongside a plan_source that says whether the planner translated a natural-language question or the caller sent the plan directly. Store the plan with the decision, paste it back later, and the same deterministic executor runs it again on the current data. The model is never in the replay path.
How do you help with FCA and PRA model risk requirements?
We do not certify your model, that is your model risk team's job. We give you the inputs to do it well: a versioned methodology with a public registry, engine_version on every response, a plan-replayable AI seam, sample-size gating, country-scoped percentiles, and source attribution on every signal. The full methodology is public and drops into your model documentation pack.
What gets stored about our portfolios?
Just the postcode or area code and an optional label you supply to map back to your own records. No PII, no borrower data, no loan amounts. Change reports and signed webhooks carry only the areas and the moves.
Close the model-governance gap your auditors keep flagging.
Bulk-score the book, track drift, cite the version behind every number, and replay any AI query as a deterministic plan. The audit trail is the response.