01
The user is ready.
They ask their agent to sign up for your platform and give it permission to get started.
Oversine
Backed by Y CombinatorLet agents sign up and log in
to your platform autonomously.
Support agent auth wherever you meet agents.
An illustration of assistants using Oversine to sign in through the browser or MCP. The example does not collect credentials. Select Continue with Oversine to replay.
The Problem
Your next user might arrive through an agent. Your login needs to let it in.
Book a demo02
The agent hits a wall.
It reaches a login flow built for a person, with no clear way to continue on the user’s behalf.
03
The user has to take over.
Instead of finishing the task, the agent sends the user back to a login screen. Some never come back.
Enter Oversine
Add Oversine to your sign-in page so agents can create accounts and log in for their users.
01
A button agents recognize.
The agent discovers Continue with Oversine and the sign-in details exposed in your page.
02
A code for this sign-in.
Oversine shows the agent a short-lived code tied to this browser and sign-in request.
03
The agent approves.
The agent approves the code in Oversine. The Oversine page then finishes signing in and returns the browser to your platform.
04
Your rules still apply.
The user’s delegated permission covers sign-in. Your platform’s session and authorization rules govern what the agent can do next.
Keep the auth you already use
Oversine integrates with your existing auth provider through a standard OpenID Connect (OIDC) connection.
Clerk
Auth0
Firebase
Supabase
Descope
AuthKitand more
Don't see your provider? Oversine uses OIDC, so any provider, or no provider, can support us. If you need help, email support@oversine.com.
Assistants don’t lack intelligence,
they lack autonomy.
Give them a way through the login screen. Oversine lets agents sign in with their user’s permission, so they can get on with what they came to do.