"Mortgage lending runs on thousands of websites that will never have APIs, like county tax portals and government exclusionary lists. Browser Use lets our AI agent do that work the way a loan processor would: find the right county site, pull the tax bill, run the compliance search, and save the evidence. We bring our customers one step closer to fully automating all of their workflows."
— Mike Yu, Co-founder and CEO, Vesta
Vesta is the loan origination system where people and AI agents work together on a mortgage. Its agents use Browser Use to do the part of a loan file that only exists on a website: search a borrower on the government exclusion lists, pull a property tax bill from a county portal, capture a property record, and save the page as a PDF that goes into the file. Every session runs under zero data retention, because Vesta's customers are lenders.
What is Vesta?
Vesta is an AI-native loan origination system (LOS) for mortgage lenders. Its agents work the routine steps of a loan, log what they did for compliance, and route the exceptions to a person. Vesta connects to more than a hundred providers through APIs, from credit and automated underwriting to document and income verification.
The rest of the loan file does not have an API. A borrower has to be checked against OFAC's sanctions list, the SAM.gov exclusions list and HUD's Limited Denial of Participation list. A property tax bill has to come from whichever county portal serves that county. Property details live on listing and record sites built for a person with a mouse. None of these publish an endpoint a lender can rely on, and the regulator wants evidence, not a boolean. A search that cannot be shown later did not happen.
How Vesta uses Browser Use on a loan
For each of those steps, Vesta's agent hands a task to Browser Use. A Browser Use agent opens the portal in a managed cloud browser, enters the borrower's name or the property address, waits for the result, and returns two things: the answer in the schema Vesta asked for, and a PDF of the page it saw.
Vesta's platform stores the PDF on the loan, where it stays as evidence. Those PDFs matter beyond the audit: when a loan is later sold, investors often require them as part of the file.
That gives one loan somewhere between one and a handful of browser sessions, each one small, each one leaving a document behind.
What Browser Use takes on for Vesta:
- Portals that block automation. Government and property sites use bot detection and CAPTCHAs. Browser Use handles those inside the session (stealth, CAPTCHA handling).
- Logins with a corporate identity provider. Some portals sit behind an SSO redirect and two-factor codes. Credentials are passed as secrets scoped to allowed domains, so they never appear in the task text or the model context.
- Structured answers. Vesta sends an output schema with every task and gets JSON back, not prose (structured output).
- Documents. The agent saves the page as a PDF, or downloads the bill the portal offers, and Vesta retrieves the file from the session (workspaces and files).
Why a mortgage LOS chose Browser Use
Vesta needed three things from a browser layer that its lender customers would accept.
- Zero data retention. Lenders are strict about borrower data. Vesta's production project runs with zero data retention: task content, screenshots and files are purged automatically shortly after each session ends, and Vesta can purge a session on demand. Vesta's team asked for this in week one, before shipping anything.
- Enterprise security terms that flow down. Vesta onboards large lenders whose requirements reach every subprocessor that touches regulated data. Browser Use committed in writing to encryption in transit and at rest, annual SOC 2 Type II coverage, incident notification within set hours, deletion attestation on request, and subprocessors bound by terms at least as protective.
- Inference that stays in the United States. Vesta has a requirement that model inference happens in the US. Browser Use runs Anthropic models through AWS Bedrock and, for Vesta's production project, routes OpenAI models to US-only endpoints.
The agent never makes the decision. It collects the evidence; Vesta's platform and its lender customers make the call. Keeping the agent out of the credit decision is what makes this safe to automate in a regulated workflow.
Moving to the Browser Use v4 agent
Vesta built its integration on the Browser Use task API in early 2026 and moved production to the v4 agent in August 2026. The migration kept the same shape: one task per compliance step, a schema in, a PDF out.
Learn more about Vesta at vesta.com.
