Skip to main content

Stop leaked API keys from becoming incidents.

VaultProof Active Key Protection keeps raw provider keys out of apps and deployment workflows, with usage visibility and fast revocation when something looks wrong.

14-day trial · Works with supported SDKs · Setup varies by provider

See Active Key Protection in 60 seconds

See how VaultProof protects the API keys your apps and AI agents use.

VaultProof Your API key.
A safer request path.
Watch the introduction 60 seconds
Read the video summary

Protect the API keys your agents use. Copies of a raw provider key can spread across apps, laptops, pipelines, and agents. A leaked key can still work until you revoke it.

VaultProof keeps the raw provider key out of your app. Your app uses a project token instead, through the protected request path. Project tokens are still sensitive: keep them private.

See provider, route, and status in API activity. Revoke a leaked project token. Your agents keep working while raw keys stay out of their code. Setup depends on the supported provider and SDK.

Why fewer copies matter.

18.1M
API keys and tokens observed in criminal data during 2025
SpyCloud · 2026
74%
of 10,000 live secrets on public GitHub still valid after 31 days
Truffle Security
≤ 5 min
to observed abuse of an exposed AWS IAM credential in EleKtra-Leak
Unit 42

Your API keys are copied into every system you run

Apps, build systems, laptops, and AI agents often hold the same live provider credential. Every copy creates another place to leak. If one copy escapes, it may grant direct provider access from anywhere.

A leaked key still works until you revoke it

Your team may still be searching repositories, logs, laptops, and running environments when the key must be rotated. The exposed credential remains usable during that gap.

Attackers can reach the provider before you see the leak

Attackers automate secret discovery, validation, and provider requests. The first unauthorized request can arrive before the exposure reaches the team that owns the key.

Reduce raw-key exposure before the next leak

Repository scanning helps find credentials that have already reached source control. VaultProof Active Key Protection reduces the raw provider-key copies held by supported application runtimes.

Find existing exposure

Scan repositories for credentials that have already reached source control.

Scan for exposed keys
Reduce future copies

Move supported provider keys out of application configuration.

Set up Active Key Protection

Know where your provider key exists and when it is used

From your app to the provider

Illustrated protection flow · not live activity

  1. Your applicationvp-proj-…A runtime value, not the raw provider key
  2. Separate storage
    Encrypted share AEncrypted share B
    Two authenticated ciphertext shares
  3. Provider requestKey reconstructed inside the proxy request pathActivity: provider · route · status · latency

Application

Your app holds a VaultProof project value

VaultProof supplies a vp-proj-… value and a provider-compatible base URL. Depending on the provider and SDK, configure environment variables or update your client initialization code to route requests through VaultProof.

App holdsvp-proj-…

Open setup guide

Custody

The provider key is split before storage

VaultProof stores two authenticated ciphertext shares separately. Normal application flows cannot retrieve the raw provider key.

StorageTwo separate encrypted shares

Review the security model

Runtime

The proxy reconstructs the key for the provider request

The proxy authenticates the outbound request. Raw key material stays inside the proxy request path while VaultProof records safe operational metadata.

Activity recordprovider · route · status · latency

Review Activity Logs

Protect one provider key from your terminal

curl -fsSL https://vaultproof.dev/install | sh
Open setup guide

Confirm the protected request

Example Activity Log
Provider
openai
Route
/v1/chat/completions
Status
200
Latency
50 ms

Protect your first provider key

  1. Install

    Use Node.js 18 or newer. Install the CLI with the command above, follow the installer’s PATH instructions if needed, then open your app directory.

  2. Inspect

    Run vaultproof-init --dry-run to see supported provider keys without rewriting a file.

  3. Apply

    Run vaultproof-init and review its prompts. Apply the generated runtime value and base URL. Follow any provider-specific instructions to update your SDK’s client configuration or application code, then restart or redeploy.

  4. Verify

    Make one real provider request and confirm that the protected route appears in Activity Logs.

Let ChatGPT inspect protection without accessing provider keys

VaultProof's remote Model Context Protocol server gives ChatGPT ten read-only tools for project status, protected credential metadata, usage, activity, alerts, integration health, and MCP connections. Public tools cannot return credentials, scan source code, modify your app, manage billing, or call providers.

Public tools
10
Authorization
OAuth + PKCE S256
Access
Read only · revocable

Requires an existing VaultProof account. ChatGPT Developer Mode availability depends on account and workspace policy.

Production endpoint https://mcp.vaultproof.dev/mcp
10 READ-ONLY TOOLS
01
vaultproof.credentials.list

Lists protected credential labels, providers, projects, and states without key values.

credentials:metadata:read
02
vaultproof.integration.guide

Returns safe guidance for placing VaultProof at the server-side provider boundary.

integrations:read

Response boundary Raw credentials, token values, internal IDs, source files, mutations, and provider execution are excluded from the public tool surface.

Answers developers need before setup

What changes in my application?

VaultProof replaces the raw provider-key value used by your app and routes supported requests through a provider-compatible proxy URL. Some integrations use environment variables; others require changes to the SDK’s base URL, client initialization, or application code. Follow the setup instructions for your provider and SDK, then verify a real request in Activity Logs.

Where does the provider key exist?

VaultProof stores it as two separate authenticated ciphertext shares. The proxy reconstructs the key inside the request path to authenticate the outbound provider request.

What if a vp-proj-… value leaks?

It cannot reveal the original provider key through raw retrieval, but it may authorize proxy traffic until origin, rate, or revocation controls stop it. Treat it as a runtime credential.

Does VaultProof replace secret scanning?

No. Scanning finds credentials that reached source control. Active Key Protection reduces the raw provider-key copies held by supported application runtimes. They address different parts of the exposure problem.

Can I preview setup before changing my app?

Yes. After installing the CLI, run vaultproof-init --dry-run from your app directory to inspect supported provider keys without rewriting files. Review the output before running setup. The CLI requires Node.js 18 or newer. See the setup guide for the full steps.

How do I check that protection is working?

After updating your provider configuration, restart or redeploy your app and make one real provider request. Check Activity Logs for the routed request, including its provider, status and latency. Installing the CLI alone does not route your application’s requests through VaultProof.

Can ChatGPT read my API keys or change my account?

The public MCP tools cannot return raw provider keys or token values. They give ChatGPT read-only access to protection metadata, usage, activity and integration guidance. They cannot modify your app, manage billing or call providers. Review the MCP access boundaries before connecting.

Does every provider use the same setup?

No. Setup depends on the provider and SDK. Some integrations use environment variables; others need a different base URL or changes to client initialization. Follow the instructions for your supported integration and verify a request before relying on it in production.

Choose your Gateway plan.

Prices are in USD and exclude applicable tax. Annual billing costs the equivalent of ten monthly payments. API-provider charges are separate.

Calls and active-key allowances are shared across your account. Unlimited projects do not multiply those allowances.

Starter

For a small protected workload.

$19/ month

or $190 / year

  • Protected calls50k / mo
  • Active protected keys20
  • ProjectsUnlimited
  • Activity history30 days
  • Account users1
  • Selected-plan trial14 days

Builder

Featured plan

For growing applications and agents.

$49/ month

or $490 / year

  • Protected calls250k / mo
  • Active protected keys50
  • ProjectsUnlimited
  • Activity history1 year
  • Account users1
  • Selected-plan trial14 days

Pro

For higher-volume protected traffic.

$99/ month

or $990 / year

  • Protected calls1M / mo
  • Active protected keys100
  • ProjectsUnlimited
  • Activity history1 year
  • Account users1
  • Selected-plan trial14 days

Core protection in every plan.

  • CLI setup with a dry-run preview before changes
  • Managed runtime values and provider-compatible routes
  • Provider-key splitting before upload
  • Separate authenticated ciphertext shares at rest
  • Credential reconstruction inside the proxy request path
  • Safe activity metadata for protected calls
  • Key rotation, token deletion, and access revocation controls
  • Configurable website-origin restrictions for project proxy requests
  • Allowed server IPs on developer-key proxy requests only

Origin restrictions check request headers and complement other access controls; they are not standalone authentication. Server-IP restrictions do not apply to the project-proxy path.

Trial and billing.

Choose a monthly or annual subscription after trying the plan that fits your workload.

Do I need a card to start?

No. Your one-time 14-day trial includes the features and limits of the plan you select, without a card or automatic charge.

What happens when the trial ends?

Protected calls pause until you purchase a subscription. There is no permanent free plan.

How do annual plans work?

Starter is $190, Builder $490, and Pro $990 per year, billed annually. Protected-call allowances remain monthly.

Are API-provider charges included?

No. Your API provider bills its usage separately. Your VaultProof subscription covers Gateway access and the allowances shown above.

Move one raw API key out of your app

Start your selected-plan 14-day trial, protect one supported provider, and verify the first routed request in Activity Logs.