Encrypted custody for API keys

Share the use.
Keep the key.

How it works Try the demo

How it works

Six steps, from your key to an answered call.

Key owner

Owns the key.

1

KiLocker

Keeps the key.

2
key4

User

Person, app or agent.

3 5 6

Service

The API the key belongs to.

  1. Key to KiLocker, once.
  2. You and KiLocker give a user an access pass.
  3. The user sends a request.
  4. KiLocker checks the pass and adds the key.
  5. Request and key reach the service.
  6. The service answers the user.
key access pass request / response request + key

Try the demo

Play owner and user. Watch one call from three sides. Runs in your browser with a fake key.

1 · Store a key Owner

Give KiLocker your key.
Stored. Key ID

2 · Grant access Owner

Who, how many, how fast, how long.
gets access pass
Works only at KiLocker.
calls left

3 · Send a request User

As the user.
User sends
—
KiLocker adds
—
Service gets
—

4 · Watch & revoke Owner

Every call, live.
No activity yet.

Works with

Any API with a header key. First up:

OpenAIAnthropicAWS BedrockOpenRouterMore soon