agentura.

Your keys stay locked: how Agentura protects your passwords and API keys

A glowing safe holding a single key

Written by

in

Your agents need keys to do real work: the password to your shop, the key to your email tool, the account for your AI model. On Agentura they can use those keys all day without ever seeing them.

A hotel safe, not a sticky note

Plenty of tools keep your passwords the way people keep sticky notes on a monitor: anyone who reaches the screen can read them. Agentura works more like a hotel safe. When you save a key, in a connector’s settings or in your company’s API Keychain, it is locked away immediately, with a lock that belongs to your company alone. Another company’s lock can’t open yours, and the stored copy is just scrambled text to anyone looking at it.

Your agent asks, Agentura opens the door

This is the part that matters most. When an agent needs to check an order, send an email or call an AI model, it doesn’t get your key. It asks Agentura to make the call. Agentura takes the key out of the safe and attaches it to that one request on its way out. The agent only gets the answer back. The key never enters the agent’s conversation, so it never ends up in an AI model’s memory, in a chat history, or in a summary someone reads later.

A robot hand receives an envelope of light through a slot in a sealed door, while the key stays behind the door
The agent gets the answer. The key stays behind the door.

For keys in your API Keychain we go one step further. Some websites accidentally repeat your key back in their answer. When that happens, Agentura blanks it out before the agent sees the reply. If it can’t be completely sure the key is gone, it holds the reply back.

Your agents can use a key all day long and still never know what it is.

You decide who may use what

A row of boxes, each with its own glowing padlock, and a hand of light choosing which small robots may approach which box
Every key has its own lock, and you choose who may use it.
  • Only the agents you choose. Each key in the API Keychain can be restricted to named agents. The others simply can’t use it.
  • Budgets and expiry. Give a key a spending limit and an end date, so a forgotten key doesn’t keep working forever.
  • A record of every use. Each time an agent uses a Keychain key, Agentura notes which agent, which service and when, so you can look back. The key itself is never written in that record.
  • Only people can look. If you need to see a saved key again, you can, once you’re signed in. Agents can’t, however they ask.
  • No quiet detours. An agent can’t point a saved key at a different website or change how it’s sent.

One habit that helps

All of this protection applies once a key is stored in the right place. So we ask one thing of you: don’t paste a password or key into a chat. Anything you type in a conversation is read by the AI. Put it in the connector’s settings or in your API Keychain instead. It takes the same ten seconds, and from then on it stays locked away.

Give your agents real keys, safely →

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *