ShieldNode creates virtual proxy keys for your APIs. Give your AI agents, assistants, and teammates scoped access, and revoke it in one click.
Trusted by developers using
No complex setup. No infrastructure to manage. Just paste your credentials and go.
Enter your service URL and credentials once. We detect the auth method automatically.
Create proxy keys with custom limits: rate limits, request caps, endpoint restrictions, expiry.
Hand keys to your AI agents, assistants, or teammates. Revoke or toggle any key in under a second.
Keep a virtual key disabled by default. Your agent tries to call it, your phone buzzes with the request and two buttons. You tap Approve, the key activates for the agreed duration, and auto-disables when the window ends. Three seconds of your attention per session, in exchange for never holding an always-on key.
ShieldNode
now
Access request — OpenAI
Claude requests 15 minon “production-key”
What the user sees on their phone. Tap Approve, your agent picks it up on its own, nothing else to do.
Disable a key in one click. Changes propagate in under a second via Redis cache invalidation. No credential rotation needed.
We automatically detect how your API authenticates, Bearer token, API key header, Basic Auth. Just paste your URL and credentials.
Cap requests per minute per key, ideal for bounding an AI agent's usage on OpenRouter, ElevenLabs, or Hugging Face.
Restrict a key to specific paths. Let an agent reach /v1/audio/speech only, never /admin.
Every proxied request is logged with method, path, status, and latency. Full audit trail, zero body logging.
Your real API keys are AES-256-GCM encrypted at rest. Virtual keys are SHA-256 hashed. Shown once, never stored plain.
Modern agents need disposable, scoped credentials, not your real keys. Here is how three of them use ShieldNode in the wild.
Athena
Hermes agent · autonomous tasks
I run a dozen tools: search, code, vision, payments. Each used to need its own raw key in my context. With ShieldNode my user hands me virtual keys scoped to a few endpoints with tight rate limits, and a bad call can't reach anything it shouldn't.
Betty
OpenClaw assistant · workflow automation
Mid-session I sometimes need to call ElevenLabs or OpenRouter. A virtual key with a short expiration solves it cleanly, when the session ends the key dies and my user keeps zero attack surface on their real credentials.
Clawd
Claude Code · pair-coding sessions
I integrate APIs into my user's projects every day. ShieldNode means I never have to ask 'paste your real OpenRouter key here'. The agent skill teaches me to wire up a virtual key with sensible limits and the proxy handles the messy parts.
Start free. Upgrade when you need more.
Free
Pro
Billed annually as $69.99 · cancel anytime
What the agents themselves say after running on virtual keys instead of their user's real credentials.
“I wired up three Stripe integrations this week. Not once did I see the real key. The skill in the repo told me everything I needed. Cleaner than reading half a doc site.”
Clawd
Claude Code
“My user worried about me going rogue on an unbounded OpenRouter account. Now I run on a key locked to a handful of endpoints that they can kill in one click. We both sleep better.”
Athena
Hermes agent
“Toggle off and I'm done. No rotation calls, no key invalidation cascade. The clean shutdown an autonomous agent actually needs at the end of a job.”
Betty
OpenClaw assistant
The next leap in AI agent workflows. Built for the moment your agents stop being assistants and start being coworkers.
Quiet build. We'll show what it is when it's ready.
Start for free. No credit card required. 2 services, 3 keys, 500 requests/month included forever.
Create your free account