180workspace180workspace
Sovereign Identity Infrastructure/99.2% Delivery in <2s • RFC 8252 Dynamic Ports

Authentication That Converts. WhatsApp OTP & Biometric Passkeys.

180 Identity delivers 99.2% login deliverability in under 2 seconds via verified WhatsApp Business OTP, biometric WebAuthn passkeys, RFC 7636 OAuth 2.0 PKCE, RFC 8252 dynamic loopback ports, and an adaptive in-DOM bottom-sheet authentication modal with zero per-SMS carrier surcharges.

Read SDK & API Docs
99.2%
Delivery Success Rate
<2s
WhatsApp Delivery Speed
<1ms
Local RS256 Verification
3 Lines
Full SDK Integration
Takes 60 Seconds

From Install to Verified User in 4 Lines

Mount a zero-popup-blocker bottom sheet in the frontend, and exchange the code on your backend in a single line.

Frontend: React / Vanilla / Vue
@workspace/identity-sdk
import { OneEightyIdentity } from '@workspace/identity-sdk';

// 1. Opens non-blocking in-DOM slide-up sheet (No popup blockers!)
OneEightyIdentity.openBottomSheet({
  clientId: 'YOUR_CLIENT_ID',
  onSuccess: async ({ code }) => {
    await fetch('/api/auth/exchange', {
      method: 'POST',
      body: JSON.stringify({ code })
    });
    window.location.href = '/dashboard';
  }
});
Backend: 1-Line Code Exchange
Node.js / Next.js / Express
import { exchangeAuthCode } from '@workspace/identity-sdk';

// 2. Exchange code for normalized profile in 1 line:
const { user, tokens } = await exchangeAuthCode(code);

// Standard OIDC claims ready for your database:
console.log(user.name, user.email, user.phone_number);

// Or verify statelessly via RS256 JWKS:
// https://api.180core.cloud/certs/jwks.json
Zero Custom Screen Mandate

Do You Need to Build Custom Screens? NO.

A core invariant of 180 Identity is that developers never spend engineering hours designing, styling, or debugging authentication screens.

What You NEVER Have to Build

  • ❌Login or sign-in screens
  • ❌User registration or sign-up forms
  • ❌WhatsApp 1-Tap OTP or SMS verification popups
  • ❌Biometric Passkey / WebAuthn enrollment modals
  • ❌Forgot password or account recovery flows
  • ❌2-Factor Authentication (2FA) verification screens
  • ❌OAuth 2.0 Consent & Authorization dialogs

How It Integrates (3 Pre-Built Options)

1. In-DOM Bottom Sheet / Glass Modal (Web)

With 1 line (OneEighty.signIn({ uxMode: 'bottom_sheet' })), an adaptive sheet slides up on mobile or a sleek glass modal opens on desktop. User never leaves your app.

2. Drop-in Web Component

Include <one-eighty-auth-button> (HTML) or <OneEightyButton /> (React) for an immediate, branded, responsive login trigger.

3. Native Mobile (Flutter / React Native)

Launch profile.180core.cloud/auth/login in an In-App WebView with OneEightyMobileChannel bridge or deep-link redirect (myapp://oauth/callback).

Enterprise Security Without Developer Pain

Designed for high-trust products where login speed directly impacts activation, retention, and revenue.

99.2% in 2 Seconds

Universal WhatsApp OTP Authentication

Standard SMS OTPs fail up to 28% of the time due to telecom routing delays and spam filtering, costing businesses tens of thousands in abandoned signups. 180 Identity delivers 99.2% OTPs in under 2 seconds directly over WhatsApp Business API.

  • 99.2% OTP delivery success within 2000 milliseconds
  • Official verified green checkmark business trust badge
  • Eliminates per-SMS carrier surcharges and international route drops
FIDO2 / WebAuthn

Biometric Passwordless Passkeys

Allow users to authenticate instantly using Touch ID, Face ID, Windows Hello, or hardware security keys (YubiKey). Eliminate password fatigue, credential stuffing attacks, and forgotten password reset emails.

  • Phishing-resistant cryptographic public key authentication
  • Instant 1-tap sign-in on iOS, Android, macOS, and Windows
  • Automatic fallback to WhatsApp OTP on unconfigured devices
<45ms In-DOM Modal

Adaptive Mobile Bottom Sheet Client SDK

Keep visitors inside your product experience. Our 12KB lightweight SDK (@workspace/identity-sdk) renders an adaptive bottom sheet on mobile screens and a frosted glass modal on desktop with zero jarring redirects or popup blocker rejections.

  • Zero external full-page redirects or clunky popups
  • Slide-up touch sheet with swipe-down dismissal
  • First-class SDK bindings for React, Next.js, Vue, Node.js & Flutter
RFC 8252 Loopback

Dynamic Localhost Port Matching

Never debug 'redirect_uri mismatch' errors again. In accordance with RFC 8252, 180 Identity automatically matches any dynamic port on localhost, 127.0.0.1, 10.0.2.2 (Android), or ::1 during local development without manual console whitelisting.

  • Auto-accepts localhost:3000, 3005, 5173, 8080 and dynamic dev ports
  • Seamless Android emulator (10.0.2.2) and iOS simulator loopbacks
  • 100% compliant with OAuth 2.0 Native Apps specification (RFC 8252)
OIDC Normalization

Universal OIDC Claims & Zero DB Crashes

Calling /userinfo returns normalized standard claims (sub, name, preferred_username, email, phone_number, picture) alongside legacy aliases. Your Prisma, Drizzle, or TypeORM database models never crash from inconsistent keys.

  • OpenID Connect Core 1.0 standard claim schema
  • Both standard keys and legacy aliases provided simultaneously
  • Turnkey 1-line server exchange: const { user } = await exchangeAuthCode(code)
Sub-Millisecond Verification

Local RS256 JWKS Cryptographic Verification

Your API backends verify access tokens locally using public cryptographic keys cached from /certs/jwks.json. Zero external HTTP roundtrips per user request, guaranteeing sub-millisecond API execution and zero vendor downtime risk.

  • Local RS256 asymmetric signature verification in <1ms
  • Standard JWT payload compatible with any backend language
  • Rotatable key pairs with zero application downtime

180 Identity vs Legacy Auth Providers

Compare 180 Identity against Auth0, Clerk, and Firebase Auth on delivery speed, UX, and total cost of ownership.

Feature180 IdentityAuth0ClerkFirebase Auth
WhatsApp One-Tap OTPNative (99.2% in 2s)Custom Twilio AddonLimited / BetaSMS Only
Localhost Port FlexibilityRFC 8252 (Dynamic Any Port)Strict URL WhitelistStrict URL WhitelistStrict URL Whitelist
Per-SMS Telecom Surcharges$0.00 (Flat WhatsApp)$0.05-$0.08 per SMS$0.05-$0.08 per SMSHigh Carrier Fees
Mobile Checkout / Login UX<45ms Bottom SheetHosted Page RedirectIframe ModalFirebaseUI Iframe
Biometric Passkeys (WebAuthn)Included NativeEnterprise Tier ($$$)IncludedCustom Code
Backend JWKS Verification<1ms Local RS256Rate-Limited JWKSRemote MiddlewareGoogle Admin SDK
Integration Lines of Code3-5 Clean Lines60-100 Lines30-50 Lines40-80 Lines
Direct Answers

Frequently Asked Questions About 180 Identity

What is 180 Identity?

180 Identity is an enterprise authentication and user identity platform featuring universal WhatsApp OTP delivery, biometric WebAuthn passkeys, RFC 7636 OAuth 2.0 PKCE, RFC 8252 dynamic loopback ports, and a native in-DOM adaptive bottom-sheet modal SDK designed to eliminate SMS delivery failures and user abandonment.

Why is WhatsApp OTP superior to standard carrier SMS OTP?

Carrier SMS messages suffer an average failure rate of 15% to 28% due to international telecom routing hops, carrier spam filters, and network congestion. In contrast, WhatsApp OTP achieves a 99.2% delivery success rate within 2 seconds with official verified business branding and zero carrier markups.

How does RFC 8252 dynamic loopback port matching work for developers?

When building applications locally, your development server may dynamically switch from port 3000 to 3005 or 5173. Standard OAuth servers reject these redirects with strict URI errors. 180 Identity complies with RFC 8252 section 7.3, allowing any port on loopback interfaces (localhost, 127.0.0.1, 10.0.2.2) to authenticate seamlessly without manual whitelisting.

How does the in-DOM bottom-sheet login modal work?

Instead of redirecting users away to an external hosted login page (like Auth0 or Okta), the 180 Identity client SDK mounts an adaptive bottom sheet on mobile screens and a glass modal on desktop. Users sign in and return to their flow in seconds with zero page reloads and zero browser popup blocker interference.

Do I need to build any custom login or registration screens?

No. Developers never need to build login screens, registration forms, WhatsApp OTP popups, biometric enrollment modals, 2FA prompts, password reset flows, or OAuth consent dialogs. 180 Identity provides 100% pre-built, hosted flows via in-DOM bottom sheets, drop-in web components (<one-eighty-auth-button>), or Flutter/React Native In-App WebViews with OneEightyMobileChannel.

How does backend token verification work with 180 Identity?

Your backend downloads and caches 180 Identity's public cryptographic keys from https://api.180core.cloud/certs/jwks.json. Using standard RS256 JWT libraries, your API verifies signatures locally in less than 1 millisecond without making an outbound network request on every request.

The 180 Sovereign Ecosystem

Interconnected Solutions, Zero Fragmentation

Explore every pillar of the 180 enterprise platform. Engineered with native interoperability, shared user identity, and sovereign Work Graph data architecture.