Public Preview · All product capabilities included free during launch

One local control point for every AI agent

Give agents access.Keep your secrets.

Agent Master Key keeps your provider credentials encrypted on your Mac, then gives each AI agent one scoped key you can approve, audit, revoke, or kill.

  • Provider keys stay on your Mac
  • One scoped key per agent
  • Revoke access instantly

macOS 14+ · Apple Silicon · no account or email · open DMG → Applications

LOCAL BROKER · 127.0.0.1LIVE
Real app footage
PROVIDER SECRETEncrypted locally
AGENT RECEIVESOne scoped key
Official download pageCurrent release · distribution statusInstall details & SHA-256
45connectors in the current catalog
1key per agent
0provider secrets handed to agents
agents during the free launch

The old way is backwards

Your agent needs access. It doesn't need your keys.

Pasting a raw provider token into an agent gives it the real secret, wherever that key is stored and everywhere it works. AMK puts a local policy layer in the middle.

WITHOUT AMK

One agent. A pile of permanent secrets.

sk-proj-••••••••••••••••github_pat_••••••••••••rk_live_•••••••••••••••
  • Real credentials land in agent config files
  • Every secret has its own scope and cleanup path
  • A leaked log can expose the underlying account key
WITH AMK

One scoped key. Control stays with you.

AMKamk_live_••••••••••••
  • Provider secrets stay encrypted on your Mac
  • Each agent sees only the connectors and actions you allow
  • Approvals, audit history, revocation, and a kill switch

Built for agents that do real work

If your agent can touch an account, AMK belongs in the middle.

01

Mac-first agent users

Running Codex, Claude, Cursor, Hermes, or another MCP client against real tools.

02

Consultants & agencies

Separating client systems from the credentials and agents used to operate them.

03

AI-native teams

Giving multiple agents useful access without scattering provider keys across configs.

04

Builders & operators

Needing a visible approval boundary, local audit trail, and one emergency stop.

Four moves. You're in control.

Scroll through the handoff.

One provider secret goes into your local vault. One scoped key comes out for the agent. Follow the route.

AGENT MASTER KEYLOCAL
Agent Master Key showing a connected Codex agent
AMKSCOPED AGENT KEYamk_live_••••••••
Provider credential encrypted locallyCodex detected and ready to connectConnector and action scope appliedRequest allowed · secret stayed in vault
  1. 01 · VAULTConnect a provider.

    Bring a scoped API key. AMK encrypts it in the vault on your Mac—outside the agent's config and context.

  2. 02 · AGENTChoose who gets access.

    Connect Codex, Claude, Cursor, Hermes, or another MCP client without pasting the provider secret into it.

  3. 03 · SCOPEDraw the boundary.

    Choose the connectors and actions this agent can reach. Anything outside that scope is denied.

  4. 04 · CONTROLApprove. Audit. Kill.

    Safe calls can run, risky writes can ask first, and one switch can stop every scoped request.

Real app. Real flows.

Proof, not promises.

These short previews use the actual Agent Master Key macOS app with isolated demo data—no customer secrets and no concept UI.

01

Turn on your local vault

AMK runs the broker on your Mac. Your provider credentials stay in an AES-256-GCM encrypted local vault.

02

Connect your agent

Give Codex, Claude, Cursor, Hermes, or another MCP agent one scoped Master Key instead of every provider secret.

03

Bad credentials stop here

Invalid credentials stay masked and get a clear denial. The real key is never copied into the agent.

04

One switch stops every agent

Pause scoped calls immediately without deleting the provider credentials stored in your vault.

Local-first by design

The secret never needs to leave your Mac.

The local broker uses your real provider credential only for an allowed outbound request. The agent gets a scoped amk_live_…key, not the underlying secret.

Read the plain-English custody model
YOUR PROVIDERSGitHub · OpenAI · AWSreal scoped credentials
encrypted
ON YOUR MACAMK Local VaultAES-256-GCM · 127.0.0.1
scoped
YOUR AGENTSCodex · Claude · Cursorone revocable key each
01

Local custody

No Agent Master Key cloud vault sits in the loop. Provider secrets remain on your machine.

02

Least privilege

Grant an agent only the connectors and actions it needs. Unscoped calls are denied.

03

Human approvals

Risky actions can stop for your decision. Notifications and audit entries are redaction-aware.

04

Instant control

Revoke one agent or pause them all without rotating every provider credential.

Bring the tools you already use

One control plane. A whole stack of possibilities.

Start with the 45-connector catalog, or bring your own scoped key for a custom provider. Every route still passes through the same local broker and policy layer.

GitHub
Claude
OpenAI
Notion
Slack
Linear
Stripe
Cloudflare
Gemini
Perplexity
1Password
Firecrawl
Sentry
Supabase
Discord
AWS
Vercel
HubSpot
GitHub
Claude
OpenAI
Notion
Slack
Linear
Stripe
Cloudflare
Gemini
Perplexity
1Password
Firecrawl
Sentry
Supabase
Discord
AWS
Vercel
HubSpot
+45 connectors
and your own

No fine-print theater

Questions people ask first.

What does my AI agent actually get?+

One scoped, revocable amk_live_… key that works through the local broker. It can reach only the connectors and actions you allowed—not your underlying provider credentials.

Does Agent Master Key upload my provider keys?+

No. The provider credentials live in an AES-256-GCM encrypted vault on your Mac and are used by the broker running on 127.0.0.1.

Is the Public Preview really free?+

Yes. During the current launch window, all product capabilities are included and no account or email is required. Future material changes are announced by Agent Master Key.

What security boundary should I understand?+

AMK limits what a scoped key can do, keeps real provider secrets out of agent configs, and gives you approvals, audit, revocation, and a kill switch. It does not claim to isolate malicious programs already running as the same macOS user. For hard OS-level separation, use separate macOS user accounts.

What Mac do I need?+

The current Public Preview supports Apple Silicon Macs running macOS 14 or later. Download the DMG, drag Agent Master Key to Applications, and connect your first agent.

Access, not secrets.

Stop handing AI agents your real keys.

Download the full Agent Master Key Public Preview and take back control of every connection.

FREE PUBLIC PREVIEWDownload free

macOS 14+ · Apple Silicon · free during the launch window

Agent Master KeyFree · Apple Silicon MacDownload free