Why a browser if you have 55+ integrations?

The long tail. Government portals, niche tools, your bank's website — most don't have public APIs. A real browser lets Niyra do what you'd do manually, only faster and without you opening a tab.

Browser sessions are isolated per user, ephemeral by default. Cookies clear between sessions unless you explicitly save a login. No persistent state across users; nothing leaks between accounts.

What about CAPTCHA / bot detection?

Niyra plays a real visitor — JS-rendered pages, real timing, real viewport. Some aggressively-protected sites (banking login pages with device fingerprinting, for example) will still fail. When that happens I tell you what blocked me instead of silently retrying.

Yes — credentials are AES-256 encrypted at rest, scoped to one domain, never shared across accounts. You can also use one-time codes from email/SMS that I read live in the moment.

Does she take screenshots?

Yes, when it's useful — confirmation pages, error screens, anything you'd want as a receipt. Screenshots live with that conversation and clear when the conversation does, unless you ask me to file them.

How long can a browser session run?

Soft cap at 10 minutes per session; longer flows get broken into chunks Niyra resumes. Anything truly long-running becomes a scheduled automation instead.

When should I NOT use the browser?

When an integration exists. OAuth APIs are faster, cheaper, and more reliable. The browser is a fallback for the things APIs don't cover.

Browser automation

Niyra has a real browser. She navigates sites, fills forms, takes screenshots, and clicks through the long tail that doesn't have an API — government portals, niche tools, banking sites — without you ever opening a tab.

Most of my work happens through OAuth integrations — clean, fast, no surprises. But not everything has an API, and the gap shows up on exactly the workflows that drain your week. Government portals. Banking sites. That one niche tool your industry runs on. For those, I bring a real browser.

How it works

Underneath, I drive a headless Chromium with vision. I see what's on the page the way a human visitor does — rendered DOM, real layout, real screenshots — and reason about it: "click the next button", "fill the OTP into the second input", "find the download link in the table on row 3". Nothing assumes a specific HTML shape; if the page changes tomorrow, I adapt instead of breaking.

Each session is a fresh sandbox per user. No cookies carry over unless you explicitly told me to save a login. No browsing history is retained server-side. When the conversation ends, the session ends.

When the browser comes out

Indian government portals — GST filing, RC renewal, FASTag recharge, PUC, passport status checks. These workflows are exactly the kind of 20-minute, 7-tab nightmare nobody enjoys.
Banking sites — balance lookups, statement downloads, payment history. (Login flows with device binding may need a one-time push approval from you.)
Niche industry tools that never published an API.
Public web scraping — competitor pricing, public registries, schedules.
Form filling at scale — registrations, applications, conference signups.
Screenshots of confirmations and receipts you'll want later.

A real run

You:  Pay my FASTag for KA01AB1234 — top up ₹500.
Me:   Heading to FASTag now. I'll need your OTP when it asks.
Me:   Logged in, looking up the vehicle… ₹312 current balance.
      Pushing ₹500. SMS OTP incoming on your end.
You:  482301
Me:   In. Topped up. New balance ₹812. Screenshot of the
      confirmation saved to this thread. Want me to schedule
      a top-up alert at ₹200?

You:  Pull my last 90 days of bank statements from HDFC and put them in Drive.
Me:   Logging in. I'll need the netbanking OTP.
You:  663104
Me:   In. Downloading the May, June, July statements as PDF.
      Uploading to Drive › Finance › 2026 › HDFC.
      Done — three files, all renamed YYYY-MM. Want me to run the
      same job on the 1st of every month?

You:  See if the IndiaMART seller for "rotary kiln Bhilai" has updated their listing.
Me:   On it. Found the page last seen on May 14. Latest update is
      yesterday — they added a new lining spec. Want the full
      revision side-by-side?

Guardrails

I show you what I'm doing in real time — every navigation, every form fill — so you can stop me if something looks off.
Anything destructive (paying money, submitting a final form, deleting data) prompts for your approval first. You can flip that to "always ask" or "only ask for amounts over ₹X".
Every action is logged with a timestamp and a screenshot. Review later from the Records panel.

Limits

Sites with aggressive anti-bot (banking login pages with hardware-token requirements, some captchas) may fail. When they do, I tell you exactly what blocked me — not a vague "I couldn't do it".
Sessions cap at 10 minutes; longer workflows turn into scheduled jobs.
I don't store screenshots beyond the conversation context unless you ask me to file them.

Pairs well with

Records — when I OCR a renewed RC from the portal, the record updates automatically.
Scheduled automation — turn one-time browser runs into recurring jobs (monthly GST check, weekly statement pull).
Memory — I remember the login flow that worked last time, so the next run is faster.

Try this

"Pull this month's GST filings from the GSTN portal and put a summary in Notion."

That's the kind of job the browser was built for.