OSINTverseDocs

Sign in with OSINTverse

Let people sign in to your app with their OSINTverse account. Standard OpenID Connect with PKCE, identity only.

Markdown version

Sign in with OSINTverse is an OpenID Connect provider. Add it to your app the same way you would add any other OIDC login: point your library at the discovery document, register a redirect URI, and request openid profile email.

Your app learns who the person is (a stable sub, their name, and their email). It never sees their searches, cases, wallet, or API keys, and it cannot spend credits. For data access, use the API with the person's own key or connect an agent over MCP.

How it works

  1. Create an app on Dashboard → Developer. Choose Web app with a server (gets a client secret), Single-page app (public, PKCE), or CLI, desktop, or device (public, PKCE or the device flow).
  2. Configure your OIDC library with the client ID and the issuer https://osintverse.com/api/auth. Everything else comes from discovery:
https://osintverse.com/api/auth/.well-known/openid-configuration
  1. Sign in yourself, and add up to ten testers by email. Only you and your testers can sign in while the app is in testing.
  2. Submit it for review. Once approved, anyone with an OSINTverse account can sign in.

What people see

People sign in on osintverse.com the way they normally do, then see a consent screen with your app's name, logo, homepage, and the details it will receive. Approved apps carry a Reviewed by OSINTverse badge; apps in testing say so. People can sign out of your app at any time from Settings → Connected apps, which deletes every token your app holds for them.

Endpoints

All endpoints are listed in discovery. Do not hardcode them.

WhatValue
Issuerhttps://osintverse.com/api/auth
Discoveryhttps://osintverse.com/api/auth/.well-known/openid-configuration
JWKShttps://osintverse.com/api/auth/jwks
ID token signingEdDSA (Ed25519). Make sure your library supports it.
PKCERequired for every client (S256)

On this page