> ## Documentation Index
> Fetch the complete documentation index at: https://docs.proofable.me/llms.txt
> Use this file to discover all available pages before exploring further.

# Authentication

> Authenticate servers and apps to the Proofable API with OAuth, server keys, or wallet-signed requests.

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](../pricing).

| Need | Mechanism | Wallet code in your app |
| - | - | - |
| Sign-in for your app | Hosted Verify + `intent=login` + `returnUrl` | No |
| Access or checkout (default) | `VerifyGate` / Hosted Verify + `gateId` | No |
| MCP client sign-in | OAuth 2.0 + PKCE | No |
| Server automation as your profile | Bearer `npk_*` access key | No |
| Server creates proofs for an approved user | App link + `verifyFromApp` | No |
| Sign inside your page | SDK `verify` + `wallet` | Yes. Rare |

Server integration: [Server integrations](../integrations/server).

## Hosted Verify (default)

`https://proofable.me/verify` for [Hosted Verify](../verification/hosted).

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:

| Scope | What it allows |
| - | - |
| `neus:core` | Public protocol tools |
| `neus:profile` | Signed-in profile context |
| `neus:secrets` | Portable encrypted secrets |
| `offline_access` | Refresh token |

Server keys (`npk_*`) are a full-profile credential.

See [Add Proofable to any MCP client](../mcp/setup) and [MCP OAuth](../mcp/oauth).

## Server keys

[Access keys](https://proofable.me/profile?tab=account) 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](../integrations/server). Separate from [creating a listing](https://proofable.me/profile/portals/new), which bills hosted verification to your account.

## Signing inside your app

[Signing format](../verification/signing-format) and `signMessage` from `@proofable/sdk`

## Raw HTTP

`POST /api/v1/verification/standardize` → sign `signerString` → `POST /api/v1/verification`. [Signing format](../verification/signing-format).

[MCP Auth](../mcp/auth) and [SDK Authentication](../sdks/authentication)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.