Lending software has spent two decades getting easier to use by getting more visual. Drag a box here, connect it to a box there, fill in the fields. It was a real improvement. But if you've ever stared at a blank canvas knowing exactly what you want and not how to build it, you know the cost: the policy lives in your head, and the work is translating it.

Meet Arc, the intelligence layer we're building into LendAPI. The idea is simple: talking is the new drag and drop.

Describe it

Tell Arc what you need. It asks what it needs to know.

Type what you want in plain English: "Build a decision tree to validate credit score using FICO at a 680 cutoff."

Before it builds anything, Arc asks what the rule is for. A 680 cutoff means something different for a loan approval, a pricing tier, or an identity check, and a good teammate asks instead of guessing. Pick the answer, and Arc builds the draft: FICO score first, then debt-to-income, then income stability, with clear outcomes of approve, decline, or send to review.

You describe it. Arc builds the draft. Nothing goes live until you publish it.

There's a prompt for that

From napkin to flow, URL to portal, sentence to price

Arc isn't limited to one kind of task. In our early look:

Take a photo of a hand-drawn sketch of your process, and Arc turns it into a flow, with an application form, a KYC check, a pass-or-fail condition, and an offer, all as drafts. Point it at your company's website, and it drafts a borrower portal in your brand colors. Ask it to price a personal loan for prime borrowers, and it drafts a pricing table by FICO band.

The practical impact: the first draft of anything takes minutes, so your team spends its time improving ideas instead of assembling them.

It works the night shift

Wake up to a briefed team

Arc keeps working when you're not. While your underwriting queue sits quiet at 2 a.m., it moves applications through documents, income, bank statements, and a written brief on each file.

In the morning, your underwriter is greeted with the state of the world: "14 files read overnight. 3 need you." Where a document is missing, Arc has already drafted the email asking the borrower for it, so a single click sends it. Where a file is ready, Arc has drafted the decision, with the key facts (credit score, debt-to-income, years at employer) laid out and the evidence attached.

Then it waits. Arc proposes. You decide.

Arc goes where you work

No new screen to learn

A tool people have to remember to open is a tool people forget. So Arc shows up where your team already is.

In team chat, anyone can type a question like "how many apps are stuck in KYB?" and get an answer, plus an offer to draft the fix. On your reports, Arc notices things you'd otherwise miss, like $4,120 spent on credit pulls for applicants who were already declined, and suggests checking KYC first. And through our MCP connection, you can bring LendAPI into the AI assistant you already use and ask it to brief you on an application.

Agents propose. Humans publish.

Every part of Arc follows the same rule. It can read, draft, and recommend as fast as it likes. It can't put anything live and can't make a final decision on its own. That's how lenders get the speed of automation without giving up accountability.

Want an early look?

We're opening Arc to early partners first. If you'd like to see how it would work with your credit policy, go to https://www.lendapi.com/contact