How It Works
1
Create an Auth Agent
An Auth Agent represents a login session for a specific website and profile. Create one for each domain + profile combination.
2
Start Authentication
Start the login flow. Users provide credentials via the hosted page (or your own UI).
3
Use the Profile
Create browsers with the profile and navigate to the site—the session is already authenticated.For fully automated flows, link Credentials to enable re-authentication without user input.
Choose Your Integration
Hosted UI
Start here - Simplest integrationRedirect users to Kernel’s hosted page. Add features incrementally: save credentials for auto-reauth, custom login URLs, SSO support.
Programmatic
Full control - Custom UI or headlessBuild your own credential collection. Handle login fields, SSO buttons, MFA selection, and external actions (push notifications, security keys).
Why Agent Auth?
The most valuable workflows live behind logins. Agent Auth provides:- Works on any website - Login pages discovered and handled automatically
- SSO/OAuth support - “Sign in with Google/GitHub/Microsoft” buttons work out of the box via
allowed_domains - 2FA/OTP handling - TOTP codes automated, SMS/email/push OTP supported
- Post-login URL - Get the URL where login landed (
post_login_url) so you can start automations from the right page - Session monitoring - Automatic re-authentication when sessions expire (with stored credentials)
- Secure by default - Credentials encrypted at rest, never exposed in API responses or passed to LLMs
Security
| Feature | Description |
|---|---|
| Encrypted credentials | Values encrypted with per-organization keys |
| No credential exposure | Never returned in API responses or passed to LLMs |
| Encrypted profiles | Browser session state encrypted end-to-end |
| Isolated execution | Each login runs in an isolated browser environment |

