Skip to main content
Pick the path that matches your caller. Most products use Hosted Verify for people and a profile access key for servers. Credits apply to checks and saved results, not to hosted session sign-in. See Trust stack and Pricing. Server integration: Integrations.

​
Hosted Verify (default)

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

​
MCP OAuth

MCP clients authenticate via OAuth 2.0 Authorization Code with PKCE. Register https://mcp.proofable.me/mcp and click Connect in the host. Official CLI: npx -y -p @proofable/sdk proofable. Request only the scopes you need: Profile access keys (npk_*) are a full-profile server credential. See Connect Proofable and MCP OAuth.

​
Profile access 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 Integrations. Separate from creating a listing under profile → Listings, 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 September 8, 2026