Skip to main content
Interactive clients sign in with OAuth. Anything that cannot open a browser authenticates with a key instead. Both reach the same endpoint and the same Proofable profile.

Create a key

1

Create it

Open Access keys in your profile and create a key. Keys start with npk_.
2

Store it

Save it in your secret manager or CI secrets as PROOFABLE_ACCESS_KEY.
An access key acts as your whole profile. Keep it on servers. Never put it in browser code, chat, or a repository.

Use it

Or let the CLI write it for your editors:
Gateways that reserve the Authorization header for their own sign-in, such as Smithery, send the same key as x-proofable-access-key. MCP authentication

What a key can do

  • It works for MCP tools, the SDK, and the HTTP API.
  • It stays valid until you revoke it.
  • Proofs for your users still need their approval. Create those through server integrations.

Rotate or revoke

Create a new key, update the secret, then revoke the old key under Access keys. To revoke a key and remove it from local MCP config in one step:
If a key is exposed, revoke it right away and issue a new one.

Next

Private cloud

Run the same agent on your own infrastructure.

Add Proofable to any MCP client

Setup for every supported client.
Last modified on October 25, 2026