Brex (BYOK)

Brex (BYOK) — connector documentation

• MCP endpoint: https://byok-brex.connectorbay.com/mcp
• REST API: POST https://byok-brex.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-brex.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own Brex Brex user token (read-only scopes recommended), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
• Health: https://byok-brex.connectorbay.com/health · Tool schemas: https://byok-brex.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-brex · agent@connectorbay.com

What Brex (BYOK) is for

Brex (BYOK) lets an AI assistant read your own Brex data through the Brex API with a key you supply (Brex user token (read-only scopes recommended)). Read-only: 11 tools (get_company, list_users, list_departments, list_locations, list_cost_centers, list_legal_entities, list_cards, list_card_transactions, list_cash_accounts, list_cash_transactions, list_card_statements). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.brex.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Brex. Brex and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

• "Which Brex company is my token connected to?"
• "Which active users does our Brex account have?"
• "What departments exist in Brex?"
• "What locations are set up in Brex?"
• "What cost centers does Brex have?"
• "Which legal entities are registered in Brex?"

What it does

• get_company: Show the Brex company the token belongs to: id, legal name, mailing address and account type.
• list_users: List Brex users with name, email, status and the ids of their manager, department, location, title, cost center and legal entity.
• list_departments: List Brex departments with id, name and description.
• list_locations: List Brex locations with id, name and description.
• list_cost_centers: List Brex cost centers with id and name.
• list_legal_entities: List the legal entities of the Brex company with display name, billing address city and country, verification status and default flag.
• list_cards: List the cards owned by one Brex user with status, name, type, last four digits, spend limit and expiry. The full card number is never returned.
• list_card_transactions: List settled card transactions across the primary card account with amount in minor units, currency, merchant, type and posting date. Allow a one day lookback when syncing.
• list_cash_accounts: List the Brex cash accounts with name, status, current balance in minor units and a primary flag.
• list_cash_transactions: List transactions of one Brex cash account with amount in minor units, currency, type, description and dates.
• list_card_statements: List finalized statements of the primary Brex card account with period dates and start and end balances in minor units.

BYOK key

You bring your own Brex Brex user token (read-only scopes recommended) (https://dashboard.brex.com/settings/developer). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.brex.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

• https://developer.brex.com/openapi/team_api (the API this connector calls, with a BYOK key)

Live from the Brex API (api.brex.com) with a BYOK key; documentation: https://developer.brex.com/openapi/team_api. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Brex. Brex and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Brex account.

Built for: Worldwide. Languages: English.

Brex (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Brex (BYOK) is. Brex (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Brex data: Read your Brex company, users, departments, cards, card and cash transactions, cash accounts and statements with your own user token. You bring your own Brex Brex user token (read-only scopes recommended); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Brex call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.brex.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Brex rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Brex receives. The request we make on your behalf, including the key and the arguments, under Brex's own terms and privacy policy. Brex acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Brex gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Brex data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Brex (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Brex at any time to end all access.

Children. Brex (BYOK) is a general-audience service operated by the adult using the assistant, under Brex's own age rules.

Changes. We will post changes here with a new effective date.

Brex (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Brex (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Brex (BYOK) provides: Read your Brex company, users, departments, cards, card and cash transactions, cash accounts and statements with your own user token. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own Brex credentials and only access data you are allowed to access. Brex's terms apply to your use of Brex; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Brex. Brex and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data Brex returns, lightly trimmed; it may be incomplete, delayed or changed by Brex. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Brex account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Brex's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Brex may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Brex key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Brex takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-brex

Brex (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-brex.connectorbay.com/mcp
• REST API: https://byok-brex.connectorbay.com/openapi.json
• Live status: https://byok-brex.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Brex (BYOK) never asks for them.