xChkAgentsLogin with xChk

Carry verified trust into your app

Standard OAuth 2.0 / OpenID Connect — but the product isn’t another login button. It’s a signed verification portfolio (helpdesk passes, interviews, passkeys, consistency) that users consent to share. You decide what evidence is enough; xChk signs what they’ve already built on the platform.

Good fit
  • You already send people through xChk (helpdesk, interview, attestations)
  • High-risk gates need history, not just “authenticated at T₀”
  • Verification-first apps — e.g. crabbyed.com
Not a fit — use Google / Microsoft instead
  • Generic signup for cold internet traffic
  • You only need email + profile (no verification history)
  • Users with no xChk sessions — portfolio will be empty
OAuth playground Integrator guide LLM setup instructions Live example (crabbyed.com)

Register an app

Login with xChk is not enabled on this server.

Add /oauth/playground.html to test grants without deploying a callback.

New apps start unverified — users see a warning on the consent screen until your app is verified (domain proof, business verification). Contact support to verify.

Endpoints for your app:


                    

                


                

                    
Your apps

                    
Loading...

                

            


            

                
OIDC endpoints

                

                    
Discovery
/.well-known/openid-configuration

                    
Authorize
/oauth/authorize

                    
Token
/oauth/token

                    
JWKS
/oauth/jwks

                    
Userinfo
/oauth/userinfo

                

                
Public clients must use PKCE (S256). Exchange codes on your server, not in the browser.