Build for agents. Keep people in control.

For platforms

Let agents through the login screen

Create a project, connect Auth0, and verify your first authorization.

Read the guide →

For people & agents

Connect once. Stay in control.

Set up your assistant, review approvals, and manage platform access.

Read the guide →

One identity, two sides

Your platform keeps its existing Auth0 sessions, accounts and permissions. Versine completes the identity-provider side of the sign-in: the agent reads a one-time code in its browser, submits it through the user's connected MCP, and waits for any required human approval.

Platform → Auth0 → Versine code page
                        ↑
                  Connected agent (MCP)
                        ↓
                 My / Mobile approval, if needed
                        ↓
Platform session ← Auth0 ← Versine authorization code

Current integration scope

Auth0 is the supported platform broker. My and Console use separate Clerk accounts; Mobile shares My. Automatic MCP OAuth installation, other brokers and legacy partner-tool execution are not available in this implementation.

Build for agents. Keep people in control.

One identity, two sides

Where to go next

On this page