1passAdd login to your web and app in 5 minutes

Why 1pass ​

• It takes 5 minutes — ask your AI assistant, and you're at your first login in five.
• Minimal user data — we never store sensitive data like legal names or national ID numbers.
• Users stay in control — sign-in history, connected apps, and devices are all managed by the user.

Start with the track that matches your app ​

→ Compare tracks · ⚠️ Separate the RP per surface (do not share one RP across mobile + web)

Where to start reading ​

• 5-minute Quickstart — see the whole flow with a single curl
• Core concepts — App, Scope, and Token in 30 seconds
• FAQ — questions from teams evaluating logi, and from users
• Security guide — the easy mistakes, collected
• API reference — interactive OpenAPI

Frequently asked (in brief) ​

Q. How do we add it to our service? — Follow the Quickstart and you'll reach your first login in about five minutes. You can even hand llms-full.txt to an AI and say "add 1pass" in one line. Q. Does it work on the web? — Yes. Both QR login and SSO push approval are supported. Q. What do users enter when they sign up? — Nothing. Installing the app is signing up. Email and name are used only when a service asks, and only with the user's per-field consent. Q. Do users have to install an app? — Yes. Every login needs exactly one way to authenticate. Because it's a 5 MB single-purpose app, you avoid the sign-up drop-off where an in-app browser blocks Google login. Q. iPhone only? — No, both iOS and Android are supported.

→ See the full FAQ

Hand the whole thing to an AI/LLM ​

We publish the full docs in an LLM-friendly format following the llms.txt standard.

• 📥 /llms.txt — page index + one-line summaries (4 KB)
• 📥 /llms-full.txt — every page concatenated into one file (55 KB, 21 pages)

Paste it into ChatGPT/Claude and say "show me how to add 1pass login" — that's it.

1pass.dev