When APIs don’t exist, the browser does.
Some tools just don’t have APIs. The Oya browser integration gives your AI employee a real Chrome session — for LinkedIn engagement, web scraping, account self-service, and any task that has to look like a real human used the site.
What it does
Real interactions
Click, scroll, type, and submit forms in a real Chrome session — not a fragile DOM-only scraper.
Read what you see
Pull text, prices, statuses, or any data visible on the page — even from sites that don’t expose data publicly.
Sandboxed by default
Each session runs in an isolated browser environment. No cross-contamination between accounts or runs.
How to use the browser
- 1
Enable browser tool on the AI employee
Open the Tools page on your AI employee and toggle "Browser" on. No external account needed.
- 2
Pick your domains
Optionally restrict the browser to specific allowed domains (e.g. linkedin.com only). Reduces blast radius.
- 3
Authorize sessions where needed
For tools requiring login (LinkedIn, your own admin panel), do a one-time login through the browser proxy. We store the session encrypted.
- 4
Run a test task
Ask the AI employee to "open my LinkedIn feed and tell me the top 3 posts" or similar to confirm everything works.
Detailed walkthrough with screenshots: Channels & Apps in the docs.
What it doesn’t do (yet)
We’d rather be upfront about the edges than promise things we don’t deliver.
- Page-load times add latency — a browser run is slower than an API call.
- Some sites with aggressive bot detection may challenge the session — we surface those failures clearly.
- CAPTCHAs are not auto-solved; the AI flags them for human handling.
Frequently asked
When should I use the browser vs an API integration?
Always prefer an API if one exists — it’s faster, cheaper, and more reliable. Use the browser when there’s no API, or when the API doesn’t expose what you need.
Is this safe for accounts like LinkedIn?
We pace actions like a real human and respect each platform’s usage norms. Treat AI-driven engagement like manual engagement — it’s the safest assumption.
How are logged-in sessions handled?
Encrypted server-side and only used by your AI employee’s runs. You can revoke a session at any time from the tool’s settings.
How is the data handled?
Page contents are processed for the active run and stored in your run history for audit. We do not use your data to train any AI model.
How do I disable the browser?
Toggle "Browser" off on the AI employee’s Tools page. Open sessions are terminated immediately.
A note on AI accuracy
Oya’s AI employees are powered by large language models and may produce inaccurate, incomplete, or out-of-date responses. They are tools to assist your work, not authoritative sources. Always verify important information — especially numbers, dates, names, and any business or financial action — before relying on AI-generated output. If your AI employee suggests a destructive action (deleting data, sending money, posting publicly), confirm it yourself before approving.
No model training
Your data is not used to train AI models. It’s used to do the work you asked for, then logged in your run history for your audit.
Full audit trail
Every AI employee action maps to a run in Oya. Inputs, outputs, tools used, cost — all visible and auditable.
Build automations for sites without APIs.
Free to enable. $10 in free credits. Pay only for browser actions actually run.