Skip to content

Verify end-user JWT claims directly at your AI endpoint

Let web or mobile apps pass Auth0, Clerk, or Supabase JWTs straight to APIkit—verifying signatures and claims without a proxy server.

Copy the prompt and paste it into the AI assistant you already use.

Steps to secure browser calls with JWT auth

  1. 01

    Configure exact JWKS and issuer

    Lock verification to your exact issuer URL and audience string so foreign tokens fail validation.

  2. 02

    Require short token lifetimes

    Reject expired JWTs strictly and avoid disabling clock-skew tolerances beyond brief seconds.

  3. 03

    Map verified claims to quotas

    Key per-user rate limits on the verified sub or org_id claim rather than unverified headers.

  4. 04

    Combine JWT auth with strict CORS

    Pair token validation with explicit allowed browser origins for defense in depth.

Common questions

Can a React app safely call APIkit directly with an end-user JWT?

Yes. Because no long-lived APIkit secret is embedded in frontend code—only the signed user session JWT—calling directly is secure.

Which identity providers work with JWKS verification?

Any standard OIDC/JWT provider publishing a JWKS endpoint works out of the box, including Clerk, Auth0, Supabase, Cognito, and Firebase.

What if a user alters the role claim in their token?

Tampered tokens immediately fail cryptographic signature verification against your provider's public JWKS keys.