Commerce & finance · wired today
Brex, wired into your agent workforce
Money data demands the strictest governance of anything agents touch. The Brex connector is one of 205 executable connectors and gives agents 4 read-only tools, with the credential held in the vault and every call receipted.
Connecting Brex takes one credential
You provide API token from your Brex account; Quox sends it as a bearer token. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Where to get it: Brex's own API documentation ↗ covers creating and scoping the credential.
What agents can run against Brex
list_accountsList the Brex cash accounts on the team, with balances (the account IDs every cash transaction call is scoped by)
list_transactionsList transactions on one Brex cash account (get the account_id from list_accounts)
list_usersList the users on the Brex team (names, emails, status and department/location IDs)
list_cardsList the Brex cards on the team with their owner, status and spend limit. Card numbers and last-four digits are deliberately not returned
Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.
How proven is this?
This connector was blind shape-proven against the real Brex API: every endpoint it declares answered measurably differently from a deliberately bogus control request, without any account or credential involved. It is Beta: proven against the live API surface, not yet run with a real credential.
Brex integration FAQ
What can Quox agents do with Brex?
Agents can run 4 read-only tools against Brex: list accounts, list transactions, list users, list cards. Every call is receipted in the evidence trail.
What does the Brex integration need?
You provide API token from your Brex account; Quox sends it as a bearer token. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Do agents see my Brex credentials?
No. Credentials live encrypted in the Quox vault and are resolved server-side at call time. Agents invoke tools; they never receive the underlying secret.
How proven is the Brex connector?
This connector was blind shape-proven against the real Brex API: every endpoint it declares answered measurably differently from a deliberately bogus control request, without any account or credential involved. It is Beta: proven against the live API surface, not yet run with a real credential.