Passwords
Signing in, without handing over the password.
Some forms sit behind a sign-in. There are two ways to get an assistant through it. Both work today, side by side.
Give the password in the call
The password is typed into that one form and nowhere else. It is never written to our database, our logs or our backups, and it is never shown back in an answer. It is gone when the session closes.
Or keep it in your own 1Password
If you would rather not put a password in a call at all, keep it in your 1Password. The assistant names where the login is kept, never the password. The service reads it from your 1Password at the moment it is needed and types it into the form. The assistant is never handed the password, or the key that reads it.
Set it up, once
- Make a vault for the assistant. A new one, for this and nothing else. 1Password does not let a service account into your Personal, Private or Employee vault.
- Put the logins it may use in that vault. Only those. Whatever is in the vault can be typed into any form the assistant opens, so keep it small.
- Create a service account that can read that vault and nothing else. On 1Password.com: Developer, then Directory, then Other, then Create a Service Account. Or with 1Password’s own command-line tool:
op vault create "Assistant" op service-account create "SettleOn forms" --vault "Assistant:read_items"
1Password shows the token once. What a service account may reach cannot be changed afterwards. - Put the token in the connection’s header, beside your SettleOn key. The header is
X-1Password-Token. For an assistant, set it where the connection tohttps://mcp.settleon.ai/mcpis set up. For a program, send it with each fill:curl https://api.settleon.ai/v1/sessions/ses_.../fill \ -H "Authorization: Bearer so_live_..." \ -H "X-1Password-Token: $OP_SERVICE_ACCOUNT_TOKEN" \ -H "Content-Type: application/json" \ -d '{"values": [ {"field": {"name": "Email"}, "value": "dana@example.com"}, {"field": {"name": "Password"}, "value": {"from_1password": "op://Assistant/Acme/password"}} ]}'Never paste the token into a conversation with an assistant. No tool takes it. - Name a login by its reference. A reference is 1Password’s own way of writing where a value is kept:
op://vault/item/field. For a one-time code, end it with?attribute=otp.
What happens to it
- It is read at the moment of typing, for that one call. The token is used for that call and kept nowhere.
- It is never said back. Not in the answer to the fill, not in a later reading of the form, not in a picture of the page.
- All or nothing. If one login cannot be read, nothing is filled, and the answer says which and why.
- You hold the key. It reads one vault and nothing else, 1Password keeps its own record of each use, and you can cancel it in 1Password at any time.
One thing said plainly: either way, the password passes through the service for the moment it is typed. What 1Password changes is that it is never in a call, a conversation or an assistant’s hands.
More on what the service keeps and does not keep is on the Security page. The calls are on the page For developers.