Centralized passkey prototype

One login, every site.

This isolated lab tests MagicAuth as the passkey relying party for the whole network. The browser ceremony stays on magicauth.app, and every dynamic action goes to api.magicauth.app.

Email firstEmail identifies the user and keeps magic links as the universal fallback.

Passkey nextReturning users can use Face ID, Touch ID, Windows Hello, or a security key.

No edge backendLaravel on api.magicauth.app remains the only dynamic runtime.

Try the flow

Email login unlocks passkey registration. Returning users can then sign in with their device.

RP ID: magicauth.app

Detecting passkey support in this browser...

Checking

WebAuthn API

Checks whether this browser exposes PublicKeyCredential.

Checking

Platform authenticator

Checks whether this device can use built-in verification.

Checking

Passkey autofill

Checks support for conditional mediation when available.

Checking

Client capabilities

Uses the newer capability API when supported.

Live endpoints: /passkeys/options/login, /passkeys/login, /passkeys/options/register, /passkeys/register. Email fallback: POST https://api.magicauth.app/auth/widget/send-magic-link.