Brex StrawberryThe Brex (Staging) transactions nobody wants to work through
Your Brex (Staging), worked while you do something else: 2 reads to go through it, 3 writes to change it, and a card in front of every one of those changes.
Open the transaction. Check it against something else. Write the change. Move to the next one. That is the Brex (Staging) afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a transaction until you approve it.
What it can do is exactly what Brex (Staging) exposes to an account you authorise and nothing beyond it: 5 operations, 2 reads and 3 writes. In practice that means it can set a limit for user, invite an user and create a card, and work across the transactions, cards and limits.
The Brex (Staging) API stops at Brex (Staging). A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.
Does it read the transactions or ask you for them?
2 of the 5 operations are reads. Your account, not a guess at it: a companion can list transactions for selected cash account and list transactions for primary card account, and the full list below is the whole list, with nothing inferred from Brex (Staging)'s documentation.
The transactions are what most of this inventory is about, alongside the cards. A companion can hold all 5 of these operations and forty open tabs in the same pass, which is how an afternoon of Brex (Staging) admin becomes a queue you review.
- List Transactions for Selected Cash Account
- List Transactions for Primary Card Account
Who signs off on a new card?
All 3 write operations wait for you. A companion can set a limit for user, invite an user and create a card, and each one is staged on an approval card first: you see the transaction, the field and the new value before it lands in Brex (Staging).
Nothing in Brex (Staging) is sent, changed or deleted on your behalf without that click, and a rejected card leaves the transaction exactly as it was. The gate is the same one on every surface, described at security.
- Set Limit for User
- Invite User
- Create Card
Does the transaction sweep have to be asked for every time?
Yes. Saved as a routine, the Brex (Staging) transactions pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.
The operations playbook catalogues the other recurring shapes of store admin, the Brex (Staging) transactions sweep among them, and finished runs are published at real runs.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents