Browser

How do you automate work on payer portals with no API?

Payer portal automation does the work revenue-cycle staff do by hand on payer websites that have no API: prior authorizations, eligibility checks, claim status, denials and appeals. With Oya, an AI agent does the task once on the portal, signed in as your staff, and Oya saves it as a playbook that runs the next ones with no model. On Oya Cloud and the enterprise edition this runs under a BAA.

The portal work it takes off your team

The same tasks, on every payer that has a website and no API.

  • Filing and tracking prior authorizations.
  • Checking eligibility, copays and deductibles before the visit.
  • Pulling claim status and remittance detail.
  • Working denials and filing appeals on the payer form.
  • Keeping provider enrollment and payer rosters current.

Run it once, then replay it with no model

An agent does the task once in plain language. Oya saves it as a playbook (Playwright code, with the member ID and other details as variables), and the playbook replays with no model calls. When a portal changes, the replay stops at the step that moved, the agent finishes from there, and its fix becomes the playbook.

Signed in as your staff

Stored passwords and TOTP seeds are sealed and never shown to the model. When a sign-in needs a person, such as a text-message code, staff can take over the session and hand it back.

Under HIPAA's controls

On Oya Cloud and the enterprise edition, the controls live in the browser.

  • We sign BAAs. Our SOC 2 Type II audit is in progress.
  • Every action, by an agent or a person, is a hash-chained audit row the database refuses to edit or delete, kept for 365 days at least.
  • Oya Cloud, or the enterprise edition in your own infrastructure (Docker, ECS, GCP or Kubernetes), so PHI can stay in your network.
  • A person can watch any session live, take over and hand it back.
  • Browsers reach only the hosts you allow.

Questions

Can an AI agent work a payer portal that has no API?

Yes. Oya works the portal the way staff do, in a real browser, signed in as your staff. A person can watch any session and take over at any point.

Do we pay for a model on every run?

No. The agent works a task out once; the saved playbook replays it with no model calls. The model comes back only for a step a portal changed.

How much faster is it?

Customers report 10 to 30 times the throughput of the same work by hand.

Is payer portal automation with Oya HIPAA compliant?

On Oya Cloud and the enterprise edition, yes: Oya is HIPAA compliant and we sign BAAs. Write to [email protected].

Can I self-host a HIPAA-compliant agentic browser?

Yes, with the enterprise edition: it runs on Docker, ECS, GCP or Kubernetes, comes with a BAA, and keeps HIPAA workloads in your own infrastructure. Write to [email protected]. The source-available community edition self-hosts too, without the HIPAA offering. Every playbook exports as Playwright code you keep.