Skip to main content
Pick the path that matches your caller. Most products use Hosted Verify for people and a server key for backend calls. Credits apply to checks and saved results, not to hosted session sign-in. See Docs and Pricing. Server integration: Server integrations.

​
Hosted Verify (default)

https://proofable.me/verify for Hosted Verify. Send users to your checkout with gateId; the enforcement policy bills your app’s credits.

​
MCP OAuth

MCP clients authenticate via OAuth 2.0 Authorization Code with PKCE. Register https://mcp.proofable.me/mcp and finish the sign-in your client opens. Only Claude connectors and Devin render a control called Connect. Official CLI: npx -y @proofable/sdk. Request only the scopes you need: Server keys (npk_*) are a full-profile credential. See Add Proofable to any MCP client and MCP OAuth.

​
Server keys

Access keys for servers, CI, and MCP automation. Never in browser bundles.

​
Backend proofs

For backend-created proofs after a user approves your product once, see Server integrations. Separate from creating a listing, which bills hosted verification to your account.

​
Signing inside your app

Signing format and signMessage from @proofable/sdk

​
Raw HTTP

POST /api/v1/verification/standardize → sign signerString → POST /api/v1/verification. Signing format. MCP Auth and SDK Authentication
Last modified on October 5, 2026