If you follow Ramp on X, you've seen the team launching new products at a wild pace. And if you're one of their 50,000+ customers, your use cases probably go well beyond corporate cards by now. Cards are necessary, but the newer agentic features are where the real leverage is: helping teams find savings in their spend, claw back hours of operational work, and do more without growing headcount.
Spider-man meme, but make it enterprise software
Last fall, the Browserbase and Ramp teams started co-building Ramp's procurement agent. The web is still where most business actually gets done, so for agents to be useful, they need to navigate browsers the same way people do. Waymos figured this out for the physical world by adapting to roads, lights, and traffic that already existed. Browserbase is doing the same for digital agents, giving them a way to use the web that's already there instead of waiting for every site to ship an API.
For Ellen, the PM leading procurement at Ramp, the build-versus-buy call was easy. Her team was three people, the procurement agent was already in flight, and building a browser agent on top of everything else on the roadmap wasn't realistic. Browserbase was already running in Ramp's stack on receipt capture, which gave the team firsthand evidence that the infrastructure was reliable at scale. On the other side, Browserbase's own finance team was looking for a procurement solution, so the company came in as both the infrastructure partner and an early customer dogfooding from day one.
#"Aside from the fact that we were actually using you to build this, you're so ahead in the automation space. We've been looking for very AI-pilled, innovative partners who are willing to build with us, put up with the challenges, and push into the future.” - Ellen Li, Product Manager, Ramp#
Ramp is betting on "autonomous finance," a version of financial ops where 99% of the operational work runs through agents and people focus on the strategic calls only humans can make. Browserbase handles the real-merchant-site execution underneath, so Ramp's product team can build the finance logic on top of it.
Agents that see and act
Procurement
When an employee submits a request to procure new software in Ramp, the procurement agent picks it up, opens a Browserbase session, and works through the vendor's site to pull together the review materials an approver would otherwise gather by hand. It generates a security assessment by checking compliance posture and certifications, captures the contract terms and pricing details, and attaches everything to the request for the approver to see a complete picture.
Beatriz, Chief of Staff at Browserbase, was an early user of the procurement agent. When she was evaluating a new software vendor, the Ramp flow caught that it didn't meet internal security requirements, otherwise saving her team hours on manual review.
Receipts
Browser agents also power Ramp’s receipt fetching feature. Some receipts come in through email or Slack as employees forward them, but the trickier ones live in merchant order histories on the web. Ramp uses Browserbase to contextualize transactions by pulling data like receipts from merchant portals automatically.
Who do you know here?
A receipt fetch and a procurement search share the same underlying requirement: the agent needs the website to let it in.
Old approaches to that problem leaned on disguise: rotate the user-agent header, swap IPs, do whatever it takes to look like a human. That model scales poorly and treats every site as adversarial, even when the agent is doing legitimate work on a real user's behalf.
Browserbase’s Agent Identity takes a different approach. Every session carries a cryptographically verified credential via Web Bot Auth, an open standard adopted by Cloudflare, Stytch, and others. Instead of pretending to be a person, the agent arrives with proof of who it is and who it's acting for, which is the kind of signal trust providers can actually verify. Cloudflare validates that traffic at the edge, Stytch enables verification on the website side, and Browserbase issues and manages the credential for every session.
Financial agents that scale
Every Ramp release moves more of the day-to-day finance work onto agents, and Browserbase is building toward the infrastructure that makes that shape of work possible. Most of finance still moves one task at a time. David, Expert in Residence at Ramp, frames the future as one person being able to kick off hundreds or thousands of agents in parallel and get a consolidated answer back. With proper browser agents in the loop, procurement evaluations, receipt collection, and other finance work get handled more thoroughly and faster than any human-paced workflow could match.
Browserbase customers ran about a thousand years of browsing last year, and they're on track to ten times that this year, with Ramp accounting for a meaningful share of the volume.
Thanks to David, Ellen, and the entire Ramp team for co-building with Browserbase.
Ready to get started? Spin up your first browser session, or talk to an expert about your enterprise needs.
