This page describes AAES Govern’s controls. AAES Operate has private-work permissions, operational reviews and recorded-spend limits; it does not include Govern. About AAES Govern
Before you enable this package
Budgets apply to the amount declared in the task, not to the amount the provider actually sends or moves. Card issuance creates spending power; the spend limit is set at the provider, not in this pack. CARD_ID is a placeholder to replace before enabling.
Read each action's effects and exclusions below. Before installation, also read the complete package requirements, including credential issuance, scope, expiry, and provider permissions. These are deployment prerequisites, not capabilities this package supplies.
Capabilities (5)
Each capability below is one registered operation. The complete package JSON includes its exact network destination allowlist. The repository stores it at packs/brex.json and embeds a copy in the release binary.
Risk tiers. R0 is the minimum for reads. R2 is the minimum for write, create, update, execute, and invoke. R3 is the minimum for delete, send, pay, deploy, approve, share, and transfer. Operators can raise these levels. A minimum tier does not measure the operation's business or confidentiality risk.
On supported execution paths routed through AAES Govern, the R3 actions listed below require approval by an authorized person. Bypass paths and observation-only registrations are outside that guarantee. A provider's restoration feature does not remove this approval requirement. A provider-side approval, such as approving a GitLab merge request, is also separate from AAES Govern human approval. The capability matrix shows which execution paths are implemented, restricted to lab use, or refused at startup. Live compatibility must be tested in your environment.
Field guide. Endpoint is the service address and request method. Connector is the adapter that makes the call. Custody describes how the credential is held; the credential reference identifies the value to resolve. Data class sets handling requirements: pii means personal data, financial means financial records, and internal means internal organizational data.
brex.transactions.read v1.0.0R0
- Kind
- tool
- Action
- read
- Endpoint
GET https://api.brex.com/v2/transactions/card/primary- Connector
- http
- Custody
- customer_vault
- Credential ref
secret-ref-brex-api-token- Data class
- financial
Read transactions.
Read the account's primary card transactions.
brex.users.read v1.0.0R0
- Kind
- tool
- Action
- read
- Endpoint
GET https://api.brex.com/v2/users- Connector
- http
- Custody
- customer_vault
- Credential ref
secret-ref-brex-api-token- Data class
- pii
Read users.
Read the account's users: names, emails and roles, which are personal data.
brex.payments.create v1.0.0R3
- Kind
- tool
- Action
- pay
- Endpoint
POST https://api.brex.com/v1/transfers- Connector
- http
- Custody
- customer_vault
- Credential ref
secret-ref-brex-api-token- Data class
- financial
Create payments.
Create a transfer, which is Brex's payment endpoint: money moves, so the action is pay at the minimum R3 tier; pay is one of the designated actions requiring human approval.
The registered cost ceiling is a budget control on the declared amount: the gateway refuses a declared amount above it and commits the ceiling against the task budget; it does not bound the amount the provider request encodes.
On supported execution paths mediated by AAES Govern, the declared irreversible actions require an authorized person’s approval. Observation-only and bypass calls cannot be stopped by this control.
brex.cards.create v1.0.0R2
- Kind
- tool
- Action
- create
- Endpoint
POST https://api.brex.com/v2/cards- Connector
- http
- Custody
- customer_vault
- Credential ref
secret-ref-brex-api-token- Data class
- financial
Create cards.
Issue a card.
Issuance creates spending power rather than moving money, and a card can be terminated, so the action is create at R2, the action's floor — a lower bound, not a proof that issuance is reversible. Review the spend limits the integration may request: the limit is set at the provider, not in this pack.
brex.cards.terminate v1.0.0R3
- Kind
- tool
- Action
- delete
- Endpoint
POST https://api.brex.com/v2/cards/CARD_ID/terminate- Connector
- http
- Custody
- customer_vault
- Credential ref
secret-ref-brex-api-token- Data class
- financial
Terminate cards.
Terminate a card. A terminated card is not un-terminated — a replacement is a new card — so the action is delete at the minimum R3 tier; delete is one of the designated actions requiring human approval. CARD_ID is a placeholder to replace before enabling.
On supported execution paths mediated by AAES Govern, the declared irreversible actions require an authorized person’s approval. Observation-only and bypass calls cannot be stopped by this control.
Credential reference
The credential field names a reference rather than containing credential material. Packs are designed not to contain secrets; the format checks cover only known credential formats and cannot prove that arbitrary text contains no secrets. Installing a package registers its capabilities. Configure the provider credentials, endpoints, and network access, then test the integration in your environment before enabling it.
- Reference
secret-ref-brex-api-token- Custody
- customer_vault
- Injection
- header (Authorization)
Configure the value and injection format specified in the package. Assign responsibility for credential rotation and revocation, restrict provider permissions, and keep credential material out of logs and responses.
Complete credential requirements
A Brex API token held in the client's own secret manager. The stored material must be the complete Authorization header value (scheme included). The token's scopes are chosen at Brex, and the minimum that makes these capabilities work is the required set: a token that may create payments should not also carry account-administration scopes this pack never names.
Resources
brex-account(api, financial):https://api.brex.com
Technical package and review record
Complete provider requirements and exclusions
Use a Brex API token with only the scopes these capabilities need; the pack does not create one. Creating a payment moves money, so it carries the pay action at the minimum R3 tier, and pay is one of the designated actions requiring human approval; the registered cost ceiling and a policy budget are the second control. Card issuance is create at R2, the action's floor — a card can be terminated, but the tier is a lower bound, not a risk assessment; terminating a card is registered as delete at R3 because a terminated card is not un-terminated — a replacement is a new card.
The current API host is api.brex.com: Brex's older hostnames still answer, but the pack registers the documented host. Brex's payment rail is the transfers API (POST /v1/transfers, which carries its own transfers scope), and card transactions are read from /v2/transactions/card/primary. The Brex API's payments coverage depends on the account's enabled products and markets, and CARD_ID is a placeholder to replace before enabling. AAES has not been certified by Brex; the endpoints here are configuration to review and test; the vendor has not endorsed it.
Download the complete package JSON for exact network allowlists, credential requirements, exclusions, and setup notes. Read these requirements before installation.
The full documentation review record is supplied in the evaluation package. The evaluation package runs in your environment and comes only with the paid design partnership. This page reproduces the source links and review block; the full record is available for evaluation. Discuss a design partnership to inspect it before installation.
Review block
This section reproduces the review block recorded in the pack file. The evidence and approval record is separate: for a reviewed pack, it is in the evaluation materials and in the release binary's embedded assets.
Review completed: 2026-09-23
9 sources, retrieved 2026-09-20, 2026-09-23
- https://developer.brex.com/openapi/transactions_api (retrieved 2026-09-20)
- https://developer.brex.com/guides/quickstart (retrieved 2026-09-20)
- https://developer.brex.com/examples/payments_examples (retrieved 2026-09-20)
- https://developer.brex.com/changelog (retrieved 2026-09-20)
- https://developer.brex.com/openapi/team_api (retrieved 2026-09-23)
- https://developer.brex.com/examples/team_examples (retrieved 2026-09-23)
- https://developer.brex.com/examples/transactions_examples (retrieved 2026-09-23)
- https://developer.brex.com/openapi/team_api/users/listusers (retrieved 2026-09-23)
- https://developer.brex.com/openapi/team_api/cards/terminatecard (retrieved 2026-09-23)
Current documentation links are navigation aids. They do not change the package, its historical sources or its review date. Review dates describe a documentation review, not a live integration test. No package is provider-endorsed or yet tested against a live provider tenant.
Release identity
SHA-256 of the pack file bytes: 724d90da9e94d72a6386cdad9c9abec0b7c7038733116e4e682f5f3d7454d864
Distributable: yes, digest matches the release manifest. Editing a package changes its release identity. A deployment plan checks its own file digests; it does not restore reviewed status or authenticate approval.