Strada browser automation: agents for portals with no API

The unautomatable part of your business is usually a website somebody logs into. On September 24, Strada launched browser automation so its AI agents can operate carrier portals and legacy core systems that ship no API at all. Insurance is the vertical, but the pattern is everyone's: the vendor with no integration, the state licensing site, the distributor portal where someone re-keys orders by hand.

What actually happened

Strada is an AI platform for P&C carriers, MGAs, wholesalers and TPAs, already running voice, chat and email agents for claims intake and policy servicing. Browser automation joins those same workflows rather than sitting beside them as a separate tool.

The setup model is the notable design choice: a user records a task once, and Strada captures it as an executable workflow agents then run against live data. No engineering work to add a new portal. The example cited in the announcement is processing a policy endorsement from request through system update.

Two details matter more than the demo. First, agents use the credentials and permissions the organization already assigns to its own users — the agent is a seat, governed by the access controls the portal already enforces. Second, every run is recorded start to finish for review and audit. CEO Amir Prodensky frames it as closing "the gap between what teams want to automate and what their systems allow."

It is available now to Strada customers. No pricing was published, and we found no reliable figure for the company's funding, so we are not quoting one.

Why browser automation matters for your business

"No API" is the single most common reason automation projects die. Not model quality, not budget. Someone scopes the workflow, hits the vendor portal in step three, and the project becomes a hiring decision instead. Browser-driving agents move that wall.

Record-once beats writing selectors. The old version of this was RPA, and RPA earned its reputation honestly: brittle scripts keyed to DOM positions that shattered when the vendor shipped a redesign. A recorded task interpreted by a model degrades differently — it can adapt to a moved button, and it can fail loudly instead of silently clicking the wrong thing. Verify that behavior before you trust it with anything that writes.

Using existing user credentials is the right call, and it is also the risk. Right, because you get the portal's own permission model and audit log for free instead of inventing a shadow one. Risk, because whatever that human account can do, the agent can do at machine speed. Give the agent its own named seat with the narrowest role the portal offers — never a shared login, never an admin account because it was easier.

The audit trail is what makes this sellable internally. "An AI logged into the carrier portal on our behalf" is a sentence that stops a compliance conversation cold. "Here is the recording of exactly what it clicked, under which user, at which timestamp" restarts it. If you build this yourself, build the log before the automation.

Start with read-only work. Pull the data, reconcile it, and leave the writes to a person for the first month. The pattern earns write access; it does not start with it.

Sources: Strada announcement via IT Business Net, Strada.