Integrations · Brex
Guild agents read and write your Brex account: locking or terminating cards, adding employees, and updating organizational structures like departments and cost centers. Guild stores the Brex user token server-side so agent code never sees it. Credential policies let you restrict which operations each agent may call before any request reaches Brex.
Book a demo
See how teams govern agents that use Brex.
Talk to sales
Get access to Guild, then connect Brex to your first agent.
What the Brex tools cover
The tools reach the Brex Team API. They cover users (add, invite, update, list, retrieve), corporate cards (create, lock, unlock, terminate, update, retrieve numbers, email card details), and organizational records including departments, locations, titles, cost centers, and legal entities. Company-level data is also readable through the tools.How it works
1
Open Credentials in Guild
Go to Access & setup > Credentials in your Guild account. This is where workspace, member, and agent-scoped credentials are managed.
2
Connect the Brex integration
Click Connect, select brex-openapi, and paste your Brex user token into the API Key field. Guild sends it as a bearer token in the Authorization header on every request.
3
Add tools to your agent
Import BrexOpenapiTools from the @guildai-services/guildai~brex-openapi package and spread it into your agent’s tools object. Use pick() to include only the specific tools your agent needs.
Why Brex access needs governing
Brex tools can lock or terminate cards, add employees, and delete departments. Guild’s credential proxy enforces credential policies before any request reaches Brex. You write ALLOW and DENY rules scoped to specific agents, workspaces, or operations. A rule that denies terminate_card or delete_department blocks those calls regardless of any other ALLOW rules, and agents cannot bypass the check because the credential is injected server-side only after the policy passes. See credential policies for rule syntax. Credentials can be scoped to an account, a single workspace, a member, or one agent. A credential dedicated to an agent serves only that agent and no other workspace. By contrast, an account-level credential serves every workspace the account owns unless the workspace is restricted to its own credentials. Scoping limits the blast radius of a misconfigured agent. See credentials for scope options.About the Brex integration
This integration gives agents access to the Brex Team API using a Brex user token. Agents can create, update, and delete organizational structures such as departments, locations, titles, and cost centers. They can also manage employee users and corporate cards, including locking, unlocking, terminating, and retrieving card details. The integration isguildai~brex-openapi.
Authentication
- Type: API key
- Header: Guild sends the key as a bearer token in the
Authorizationheader
Setup
1
Connect Brex
In Guild, go to Access & setup > Credentials, click Connect, select brex-openapi, and paste the key into API Key.
Usage
Selecting specific tools
Tools are named with thebrex_openapi_ prefix. Use pick() to include only what your agent needs.
Tools
Tools in the latest published version ofguildai~brex-openapi:
All 35 tools
All 35 tools
Frequently asked questions
Can an agent retrieve full card numbers including CVV?
Can an agent retrieve full card numbers including CVV?
Yes. The brex_openapi_get_card_number tool retrieves the card number, CVV, and expiration date of a card by ID. The brex_openapi_email_card_number tool sends those details to a specified email address via a secure email instead.
Does the integration support webhook events from Brex?
Does the integration support webhook events from Brex?
No. The catalog entry for guildai~brex-openapi lists no webhook events, so the integration does not receive event-driven triggers from Brex.
Can I stop one agent from terminating cards while another can?
Can I stop one agent from terminating cards while another can?
Yes. Credential policies let you write a DENY rule scoped to a specific agent that blocks the brex_openapi_terminate_card operation, while a separate rule allows another agent to call it. Guild’s proxy enforces the rules before any request reaches Brex.
Does my agent code ever see the Brex token?
Does my agent code ever see the Brex token?
No. Guild stores the token and adds it as a bearer token in the Authorization header server-side. The agent code only calls the tool; it never receives or handles the credential directly.
Put a governed agent on Brex this week
Book a demo
See how teams govern agents that use Brex.
Talk to sales
Get access to Guild, then connect Brex to your first agent.