LendEasy/DocsLMS + Servicing·v1
Start integrating
Guides›Overview›Introduction
LendEasy Platform Documentation

Autopilot for loan servicing

Every decision governed. Every action traceable.

Hash-chained decision records

LendEasy orchestrates loan servicing operations with AI agents, bounded by your policies and backed by human judgement when it is needed. The result is audit-ready operations by design, a portfolio that scales without scaling headcount, and a borrower experience that does not keep office hours.

Signals in, outcomes out

Read it across. Work arrives as a signal — a borrower writes in, the lending core reports a missed payment, a court record matches — and leaves as an outcome somebody can audit. Between them sits one governed layer, where the AI workforce does the work and your team sees, approves, overrides or takes over through the same interface.

Every signalBorrower, lending-core, and external events
One workspaceAI and humans share cases and controls
Policy firstChecked before the action happens
Tracked to conclusionOwner, state, outcome, and evidence
Fig 1— Every signal becomes governed work and is tracked to a conclusion. The team sees, approves, overrides or takes over through the same layer the agents work in.

The four parts

Adoptable together or separately. Each owns a different half of the answer to what is true about this loan, and what may we do about it.

LendEasy Lending Core

The ledger, and the only place a loan fact lives. Balances, schedules, payments, accounting, Reg Z disclosures, statements and delinquency — every question about what a borrower owes resolves here. Installment, BNPL and merchant advances on one system of record.

Servicing Workspace

The work, running natively on top of that ledger and holding none of it. Cases, tasks and smart queues, a compliance check before every contact and account change, workflows you change without a release, and the screens your team runs them on.

AI Agent Workforce

The workers. Calls in both directions, conversations over chat, SMS and email, every document read on arrival, and hardship and promises negotiated inside the limits you configure — carrying cases to an outcome, and reaching a person where policy reserves the decision.

Borrower Self-Service

The front door, white-label on your domain. Pay, enrol in autopay, sign an agreement, upload the document a case asked for, ask for help — and each of those lands as real work on the servicing side rather than in an inbox.

Every change runs on the route that owns it, under an exact permission, leaving a record — one governed path for every mutation, whoever makes it.

Where to start

The fastest introduction is one worked case: a delinquency carried end to end, where the signal opens the case, the voice agent negotiates and records the arrangement inside policy, a specialist approves the one thing outside it, and the evidence is exam-ready at the close.

  • Quickstart — authenticate and make a production-shaped call in five minutes.
  • Guides — how each part works, for the Servicing Workspace and the Lending Core.
  • Recipes — end-to-end workflows, with the compliance checks called out at each step.
  • API Reference — every endpoint, grouped by resource, generated from the OpenAPI document.

Every calculation and servicing guide works from the same four named contracts, so balances carry from origination through payments, delinquency and closure without a new example on every page. Meet Harbor, Juniper, Cedar and Northstar, and see API availability for the exact runtime boundary of the current build.

Unified search across guides, recipes & the API referenceEsc