Grok Bot Vault scores 7.6 out of 10 from me: the way it hides secrets from the Bot is excellent, while account-wide access and the saved-card checkout rule hold it back.
I scored it from xAI's primary documentation only: the Vault page, the approvals, security and privacy page, the Team Bots page and the computer and apps page.
Every rating below carries the line from those docs that drove it.
If you'd like my team's view on which agent tools to adopt first, book a free SEO strategy session.
The short verdict
Vault is a well-designed credential layer for an AI agent.
Passwords, card numbers and security codes are filled into pages without the Bot seeing them, and saved values can never be read back.
The weak spots are about control, not secrecy.
Every Bot on an account can use every item, and a saved card pays at checkout with no per-use approval setting.
Fix the second point with your own settings and Vault becomes easy to recommend.
Grok Bot Vault scorecard
These ratings are my editorial judgement from the documentation, not lab tests.
A 9 means the docs describe behaviour I'd trust as written; a 5 means it works but most teams will need a workaround.
| Criterion | Rating | Why |
|---|---|---|
| Secret isolation | 9/10 | Vault and Secure Form values are filled straight into the page and not shown to the Bot. |
| Write-only storage | 9/10 | Passwords stay hidden, cards show four digits, and secrets can only be replaced. |
| Import | 8/10 | CSV import covers six password managers and browsers, read locally, under 5 MB, desktop only. |
| Sign-in coverage | 8/10 | Vault, then a connected manager such as 1Password, then a Secure Form, with hand-over for passkeys and SSO. |
| Per-Bot control | 5/10 | Items are account-wide; you can't limit one to a single Bot. |
| Payment control | 6/10 | A saved card fills at checkout without asking each time; approval needs a workaround. |
| Team support | 8/10 | Team Bots get their own manager-only logins and Secrets, separate from personal Vaults. |
| Mobile parity | 8/10 | Vault opens on phones, but cards can't be edited there yet and one iPhone version had a login bug. |
The average of those eight rows is 7.6.
What I based the ratings on
I used four xAI pages and nothing else.
Where a behaviour wasn't written down, it didn't earn points.
The Vault page does not name an encryption method, a storage location or any certification, so none of those factor into the score.
The X Subscription page confirms Grok Bot comes with Premium, Super and Ultra, and not with Plus; the Vault page doesn't tie the feature to a single plan.
Strength: the Bot works blind on secrets
This is the core design choice, and it's the right one.
The Bot can see your contact info and the list of logins you've saved, which lets it pick an entry.
The secret parts stay out of its view.
The same holds for new accounts: when a Bot signs up for a site and you let it choose the password, Vault generates and stores it, and the Bot never learns it.
API keys follow the same pattern through the masked secure secret card.
That earns secret isolation a 9.
Strength: nothing can be read back out
Write-only storage is a feature many tools skip.
After you save, Vault keeps passwords hidden, and a card displays only its final four digits.
The secure card footer says the value is never shown to your Bot, and Team Bot Secrets list only a name and a description.
To change anything you choose Replace and paste a new value.
The trade-off is that you need the original elsewhere if you ever want to see it again.
๐ฅ Want the agent tools I'd actually set up first? Inside the AI Profit Boardroom you get step-by-step video trainings, the installable Agent OS, four coaching calls a week and 3,400+ members testing setups together. โ Join the AI Profit Boardroom
Strength: import and sign-in fallbacks
Getting logins in is painless on desktop.
Six sources are covered, from browsers such as Chrome, Edge, Safari and Firefox to managers such as 1Password, Bitwarden and LastPass, all through a CSV that never leaves your computer.
Duplicates are skipped and broken rows are dropped instead of half-imported.
For sites not in Vault, the Bot falls back to a connected password manager, then to a Secure Form that names the site it fills.
Steps that no form can handle, like a QR code or bank card verification, are passed to you with Take over and handed back with I'm done.
That's a complete chain, which is why sign-in coverage gets an 8.
Secure Forms: clear wording at the moment it matters
When a page needs a value only you should supply, the Bot raises a Secure Form, one per step.
The form states which site it fills, and its answers go into that page without passing through the Bot.
Afterwards it confirms the result in plain words, or says it could not fill the page because the page moved; in that case the docs say the values still weren't shown to the Bot.
The save option is the part to read carefully.
A box labelled "Securely save to Bot's vault" keeps the value for later if ticked and limits it to that chat if not, while a form without the box saves straight into Vault.
That last rule is easy to miss, and it's one reason payment control doesn't score higher.
Resilience: what survives a reset
Agent computers get updated, recovered and reset.
According to the docs, a reset or update clears the apps and packages on the Bot's computer, and any key someone typed into a config file or shell profile can disappear along with them.
Values stored in Vault, the secure card or Team Bot Secrets are kept separately and aren't affected.
The page also covers a missing Team Bot secret: if the name still shows under Secrets, the value is still stored, and a blank Shell output doesn't prove otherwise.
Clear recovery guidance like this is part of why write-only storage earns a 9 rather than an 8.
Limit: no per-Bot scoping
The docs are clear: everything you save is available to every Bot on your account.
Hints such as "Use for work purchases" steer which entry a Bot chooses, but they're guidance, not a lock.
If you run a research Bot and a buying Bot on one account, both can use the same card.
That's the reason per-Bot control scores a 5.
Limit: saved cards pay without asking
A card stored in Vault fills in at checkout, and the docs say no setting requires approval for every use.
The workaround is documented: leave "Securely save to Bot's vault" unticked on the Secure Form so the card lasts for one chat, or remove the card.
You can also write an Ask first rule for payments, since those rules always stop a matching action and win over Allow rules.
With that rule in place I'd move payment control from 6 to 8, lifting the average to 7.9.
This site's Grok Bot shopping verdict rates the order cards that sit on top of this.
Limit: small mobile gaps
You can open Vault on a phone, and wallets show under Payments there.
But saved cards can't be edited on the phone yet.
And iPhone 1.18.0 on iOS 26 or later couldn't save a typed login, a bug fixed in iPhone 1.19.0.
These are minor, which is why mobile still gets an 8.
Vault versus connecting 1Password alone
You don't have to choose one.
Vault is checked first, and a connected 1Password account is the next stop.
With 1Password, you approve each login inside 1Password and it fills the Bot's browser; the docs list version 8.12.42 or later and logins from the Personal vault only.
1Password does not fill payment cards, so Vault or a Secure Form still handles checkout.
My pick: keep the handful of logins a Bot uses daily in Vault, and let 1Password cover the long tail.
Team Bots: the strongest part for small companies
Team support scores an 8 because the separation is clean.
Your personal Vault isn't available on a Team Bot, so a teammate's chat can't reach your cards.
Instead, owners and managers add Bot's vault login entries from the Bot's own settings, and only managers can view or change them.
Shared keys go under Secrets, where the Bot sees a name and description and never the value.
The one caution in the docs: Team Bot secrets work in every teammate's chat, so only add keys the whole team may use.
Company-wide licence keys for setup scripts belong to a team admin as Team Secrets on the Enterprise dashboard, which never reach Bots directly.
Who Grok Bot Vault suits, and who should wait
Use it if you are
- Solo operators who want a Bot to sign in to a few portals every day.
- Small teams that can put shared tools on a Team Bot with manager-only logins.
- Anyone who currently pastes passwords into chat and needs to stop.
Hold back if you are
- Accounts with several Bots that each need strictly separate access, since items can't be scoped.
- Owners who need sign-off on every payment but don't want to manage Secure Forms or Ask first rules.
- Teams that need a documented encryption method or certification, because the Vault page doesn't list one.
๐ Choosing between agent tools for your team? Book a free SEO strategy session and my team will help you shortlist the right ones. โ Get your free session
Final verdict
Vault does the hard part well: it lets an agent use credentials it can't see.
Its gaps are policy gaps, and two settings from you close most of them.
Turn it on, keep cards out until your Ask first rules are written, and put team logins on a Team Bot.
Then revisit the scorecard after a month of real use, because the two weakest rows are the ones your own settings control.
If both rules are in place and every login carries a hint, Vault is one of the better-documented parts of Grok Bot.
For the walkthroughs behind these settings, join the AI Profit Boardroom.
Also On Our Network
- ๐ The eight-step order I'd follow to fill Vault on a fresh account
- ๐ What shops, service firms and agencies should save in Vault, and what not to
- ๐ Five copy-paste prompts that make Vault the key cabinet of your Agent OS
- ๐ Which GoldieBench models to pair with Vault for access maps and onboarding pages
FAQ: Grok Bot Vault Verdict
Is Grok Bot Vault worth using?
Yes for most solo users and small teams. It hides passwords and card numbers from the Bot, but you should add an Ask first rule before saving a card.
What is the weakest part of Grok Bot Vault?
Control. Every Bot on an account can use every item, and a saved card pays at checkout without asking each time.
Does the Vault page say how data is encrypted?
No. The Vault page does not name an encryption method, storage location or certification, so this review does not score one.
Should I use Vault or 1Password with Grok Bot?
Both work together. Vault is checked first, then a connected password manager such as 1Password, which does not fill payment cards.
Can I see a password after saving it in Vault?
No. Saved values are write-only, so you can only replace them with a new value.
๐บ Video notes + links to the tools ๐
๐ฅ Learn how I make these videos ๐
๐ Get a FREE AI Course + Community + 1,000 AI Agents ๐
About Julian
I'm Julian Goldie, an SEO entrepreneur, author and founder of the AI Profit Boardroom, which has 3,400+ members.
I help business owners scale with AI agents, automation and SEO.
- I've built a 7-figure SEO and link building agency, Goldie Agency, with a team of 70+ SEO experts.
- I've grown a YouTube channel to 400,000+ subscribers.
- I wrote "Link Building Mastery".
- My Udemy courses have taught over 29,000 students.
โ Get my best AI training inside the AI Profit Boardroom
Set the payment rule before you save a card, then talk to my team or join the AI Profit Boardroom to get more out of Grok Bot Vault.











