Secure digital agency for AI

Let your AI act.
Keep your credentials private.

Authorize ChatGPT, Claude and other capable agents to actually do things for you across the services you choose. API Vault brokers APIs, OAuth accounts and signed-in browser sessions while keeping passwords, provider keys and session credentials behind the vault boundary.

Open API Vault Connect an AI Android app

Raw secret access: off OAuth 2.0 + PKCE Authenticated browser delegation Revocable authority

Connect

One authority layer. Every capable agent.

API Vault exposes a vendor-neutral MCP + OAuth surface. You decide which services and action classes each AI may exercise; underlying credentials remain inside API Vault.

Universal MCP endpoint https://api-vault-gpp.vercel.app/mcp

Browser fallback

If there is no API, your AI does not have to stop.

Run the API Vault browser worker on a computer you control. You sign in personally in a visible browser, then explicitly hand the authenticated session to an authorized AI.

You authenticate

Passwords, passkeys, CAPTCHA, MFA and hardware-key prompts stay human-controlled. API Vault never asks the AI to type your password.

The session stays local

Cookies, browser storage and the persistent Chromium profile remain on your worker machine rather than being exported to the AI.

You grant bounded control

Choose the AI, allowed sites, authority mode, uploads/downloads and whether financial, security, destructive or external-communication actions are permitted.

Lock or revoke

Put a profile back into human-login mode or revoke the browser session. New AI work is blocked until a signed-in profile is explicitly marked ready.

Security model

Maximum facility without credential disclosure.

The AI receives revocable capabilities and authorized results, not the provider credentials that make those actions possible.

Server-side and local credentials

API keys and OAuth credentials remain server-side. Browser authentication material remains on the user-controlled worker.

Scoped through owner-equivalent

Use granular, provider-wide or explicitly acknowledged owner-equivalent authority while retaining financial, security, destructive and communication switches.

Short-lived OAuth

Public connectors use PKCE, one-time authorization codes, short-lived child capabilities and rotating refresh tokens.

Auditable and revocable

Connector identity, operation and result metadata can be audited without logging raw authorization headers or secret values. Authority can be revoked independently.

Live status

Public connector plane.

These checks read only non-secret OAuth and MCP discovery metadata.

MCP protected resource

Checking…

OAuth authorization server