# How Vesta Uses Browser Use to Collect Mortgage Compliance Evidence From Websites Without APIs

By Steven Van · 2026-09-21

Vesta's mortgage agents run OFAC, SAM.gov and HUD searches and pull county tax bills, saving each page as a PDF under zero data retention.

Vesta, a loan origination system for mortgage lenders, uses [Browser Use](<https://creatorstoolbox.com/resources/browser-use>) to collect compliance evidence from websites that have no APIs. In a [customer case study](<https://browser-use.com/posts/vesta>), Browser Use describes how Vesta's agents handle the parts of a loan file that only exist on a website.

## What the agents do

Vesta's agent hands Browser Use a task for each step. 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 as evidence.

- Search borrowers on OFAC's sanctions list, the SAM.gov exclusions list and HUD's Limited Denial of Participation list.

- Pull property tax bills from the relevant county portal.

- Capture property records from listing and record sites.

One loan needs between one and a handful of browser sessions. The PDFs also matter when a loan is sold, since investors often require them as part of the file.

## What Browser Use handles

- **Bot detection and CAPTCHAs:** handled inside the session with stealth and CAPTCHA handling.

- **Corporate SSO logins:** credentials are passed as secrets scoped to allowed domains, so they do not appear in the task text or the model context.

- **Structured answers:** Vesta sends an output schema with every task and gets JSON back.

- **Documents:** the agent saves the page as a PDF or downloads the bill the portal offers, and Vesta retrieves the file from the session.

## Security and data terms

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. Browser Use also 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.

To meet Vesta's requirement that inference stays in the US, Browser Use runs Anthropic models through AWS Bedrock and routes OpenAI models to US-only endpoints for Vesta's production project.

## Scope of the agent

The agent only collects evidence. Vesta's platform and its lender customers make the credit decision. Vesta built its integration on the Browser Use task API in early 2026 and moved production to the v4 agent in August 2026, keeping the same shape: one task per compliance step, a schema in, a PDF out.

![Browser Use](<https://www.google.com/s2/favicons?domain=browser-use.com&sz=128>)

Browser Use

Open-source browser automation platform for AI agents — let LLMs drive a real browser to research, fill forms, scrape, and complete multi-step tasks.

[View Browser Use →](<https://creatorstoolbox.com/resources/browser-use>)

Sources

[Original source](<https://browser-use.com/posts/vesta>)

[Read How Vesta Uses Browser Use to Collect Mortgage Compliance Evidence From Websites Without APIs on Creators Toolbox](<https://creatorstoolbox.com/blog/browser-use-how-vesta-uses-browser-use-to-collect-mortgage-compliance-evidence>)

---
Canonical source: https://creatorstoolbox.com/blog/browser-use-how-vesta-uses-browser-use-to-collect-mortgage-compliance-evidence