Skip to main content
Visitors sign in and complete checks on proofable.me/verify through VerifyGate, getHostedCheckoutUrl, or MCP OAuth, so your app ships no wallet or passkey code.

VerifyGate (browser)

Hosted sign-in (browser)

Sign-in only:
The callback and popup contract is in Hosted sign-in.

Server reuse

Server keys

For servers, CI, and MCP when browser sign-in is unavailable. Create keys under Profile → Account.
The SDK sends Authorization: Bearer <npk_...>.

Client and MCP sign-in

Run proofable setup. It signs in with browser OAuth by default. Set PROOFABLE_ACCESS_KEY first only for servers and CI. MCP setup covers each client.

Advanced: verifyFromApp

After one-time user approval (app link), your backend can create proofs without a per-request signature:
Full detail: Server integrations. Raw HTTP auth: API authentication.
Last modified on October 25, 2026