Skip to main content
Most products use Hosted Verify for people and a server key for backend calls. Creating a proof uses credits; sign-in and checks against existing proofs are free. Pricing

Hosted Verify (default)

Send people to https://proofable.me/verify (Hosted Verify). With a gateId, your credits cover the checks unless the listing charges visitors a price.

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. The official CLI is npx -y @proofable/sdk. Request only the scopes you need: See Add Proofable to any MCP client and MCP OAuth.

Server keys

Access keys (npk_*) carry full profile access. Use them for servers, CI, and MCP automation, and keep them out of 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 November 5, 2026