Skip to main content
Your users sign in and verify on Proofable, then return to your product with a proof ID. You never build passkey, OAuth, or wallet screens.
Send people to Proofable for sign-in, a check, or checkout, then back to your app.
Read the proof ID from qHash on the return URL. Pass mode: 'popup' and origin to keep people on your page. Hosted verification

What your users get

Users keep their proofs. When they reach another product that accepts them, they don’t start over.

Who pays

Published gates bill the gate owner by default. When your server creates proofs with verifyFromApp, pass your access key to bill your builder profile. Agent setup bills whoever signs each step. Pricing

Keep credentials on the server

Access keys and other secrets never belong in browser code. Call Proofable from your backend when you need more than the SDK exposes in the browser.

Next

Server integrations

Create proofs from your backend.

Hosted verification

Every parameter for the hosted flow.

Agents in the SDK

Create agents for your users with owner approval.

HTTP API

Endpoints, paging, and raw requests.
Last modified on September 12, 2026