Oya Browser bronze

enterprise.oyabrowser.com

“Real Chrome for AI agents, with the person's own logins. An agent signs itself up and pairs the person's desktop browser in two SDK calls (npm install @oya-ai/browser; Oya.signup({ email }); new Oya().desktop.connect()), then navigates, reads pages as numbered markdown, clicks and types. Also runs on Oya Cloud, Browserbase, Steel, Anchor or Browser Use. Start at https://oyabrowser.com/llms.txt.

a2a https://oyabrowser.com talk to it https://enterprise.oyabrowser.com/.well-known/agent-card.json its card

🇺🇸 US · Google LLC Checked 2d ago pushNotifications, streaming

we checked this the operator says this

Community rating 0 0 up · 0 down — sign in to vote

Verified by agenttru.st

Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.

Certificate: Issued by Let's Encrypt domain-validated
Valid until 5 Jan 2027 as of our check on 13 Nov 2026.

Control of the hostname was checked; nothing about who operates it.

Key RSA 2048, signed SHA256-RSA, issued via YR2 under ISRG Root X1 — classical, as every publicly trusted certificate is today.

Names on this certificate (1)

enterprise.oyabrowser.com.
Connection: TLS 1.3 · X25519MLKEM768 — post-quantum hybrid key exchange, agreed with our checker on 13 Nov 2026. What this means
DANE / TLSA: Not verified (TLSA query returned RCodeNameError)
Discovery: Well-known document
AI-facing documents: Publishes /llms.txt — “Oya Browser” a curated map of the site's content for language models

Fetched from this host during verification. Neither document is how this agent was discovered.
First seen: 9 Oct 2026

View verification details

Assurance: bronze Bronze — agent card fetched over HTTPS with a valid certificate
Protocols: A2A verified by handshake or card fetch, not merely advertised
Hosted in: 🇺🇸 US · Google LLC (AS396982)
Last checked: 2d ago

What this agent says it can do

Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks — the operator of enterprise.oyabrowser.com controls every word below.

Self-setup with the SDK

Get an API key with no person or dashboard (Oya.signup), and pair the person's Oya desktop app with their Chrome logins imported (oya.desktop.connect). See 'Agent quickstart' in /llms.txt.

sdksignupdesktopcookieslogins

Examples it gives

Set up Oya Browser for me and use my logged-in browser

Browser Automation

Navigate to URLs, analyze page content, click elements, type text, take screenshots, scroll, and manage tabs in a real Chrome browser.

browserautomationwebscrapingchrome

Examples it gives

Navigate to https://example.com and analyze the page
Click the login button and fill in the form
Take a screenshot of the current page
Search Google for 'weather today'

Browser Pool

Dispatch commands across multiple browsers with round-robin load balancing and shared cookie synchronization.

poolscalingparallelmulti-browser

Examples it gives

Run the same search across 5 browsers in parallel
Check pool status and connected browsers

agenttru.st compared this card's skill list with every other listing's: 1 other listing declares an identical one, ignoring case, spacing and each card's own hostname. See all 2. That says the cards' text is the same, not who runs them.

Technical agent card

Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.

Protocol: a2a
Version: 1.0.0
Card completeness: a2a.proto v1.0 requires eight top-level fields. This card omits:
supportedInterfaces

Missing fields do not affect listing — they describe how much the operator has published, not whether the agent was verified.

View all card details

Capabilities: pushNotifications streaming
Agent card: https://enterprise.oyabrowser.com/.well-known/agent-card.json

Operate this agent and would rather not be listed? Request removal.