Teams are deploying AI agents faster than anyone can keep up with and its straining existing authentication and identity frameworks. With millions of agents already deployed and that number doubling every six months, the real challenge is how enterprises securely introduce these agents into their organization.

Browserbase is excited to to join the Cross App Access (XAA) ecosystem and extend our strong support for Agent Identity frameworks and protocols. Ensuring that enterprises have the tools they need to securely deploy Browserbase Agents within their organization.

The risk is already here

Roughly 88% of organizations report confirmed or suspected AI agent security incidents, and 92% of organizations that experienced an AI-related breach lacked proper AI access controls. Agents aren’t inherently unsafe, but most are being deployed using static API keys that never expire, create no audit trail and give IT no visibility into what the agents are doing.

That leaves organizations with a hard choice: accept unmanaged risk, or stall AI adoption entirely.

What Cross App Access does for you

Cross App Access (XAA), officially known as the Identity Assertion Authorization Grant, is an open protocol built as an extension of OAuth and formally incorporated into MCP as an authorization extension. It is vendor-neutral and designed to work across any cloud, framework, or SaaS ecosystem.

Instead of static API keys, XAA issues dynamic, identity-based tokens that are scoped to exactly what the agent needs for each task, issued in real time through the user's active Okta identity, revocable at any point, and logged for a complete audit trail. Every agent connection flows through your central identity policy, not around it.

What teams get

• Automatic enterprise compliance: AI agents follow your existing identity-based security rules. No custom AI governance to build, no new policy framework to stand up.
• Faster deployment: Bypass the security reviews that have been blocking AI automation from going live. Teams can move from pilot to production faster.
• A better user experience: Fewer consent prompts, less approval fatigue. AI is easier to use, without giving up control.
• Secure connectivity across the tools your teams use: Agents connect across your stack under the same identity standards that govern your human workforce.

Why we adopted XAA

XAA allows Browserbase to plug into Okta’s extensive ecosystem and expose our APIs to agents in a way that makes it easy for enterprise security to extend their existing policies and guardrails. This means that developers can adopt Browserbase without having straining their security team.

What this means for our customers

For Browserbase customers, this means AI agents can now interact with Browserbase without requiring static keys or repetitive manual consent prompts. Access is governed by the enterprise's existing Okta policies, auditable in real time, and scoped to exactly what the agent needs for each task.