Can AI agents automate Brex?

Brex is automatable today through its REST API. This record is Brex corporate cards, expenses, banking, bills, travel, and accounting integration, including the vendor-hosted MCP at https://api.brex.com/mcp. It is not Ramp, Pleo, or SAP Concur. The production API host is https://api.brex.com. Account or card admins who accept the Developer API agreement mint a dashboard user token and send it as Authorization Bearer. Unused tokens expire after 90 days. Partners use OAuth 2.0 / OpenID Connect against https://accounts-api.brex.com/oauth2/default, with authorization-code for customer accounts and client-credentials for the onboarding API. Partner access tokens last 3,600 seconds. Documented families include Expenses, Team, Transactions, Payments, Budgets, Accounting, Fields, Travel, Onboarding, and Webhooks. GET /v1/expenses lists expenses; PUT /v1/expenses/card/{expense_id} updates a card expense. Webhooks register at POST /v1/webhooks and verify HMAC-SHA256 signatures. Opened webhook events cover referrals, transfers, and user updates, not the full expense catalog. First-party MCP is beta. An admin must enable Brex in AI assistants after accepting the Developer API agreement. Clients use OAuth with Dynamic Client Registration, or a Bearer API token. Tools cover users, expenses, cards, banking, bills, vendors, accounting, and travel. Approvals and card management are not yet available via MCP. Official language SDKs, a general-purpose CLI, and iPaaS catalogs were not established from the opened pages. Computer-use viability is unassessed. API scores 8 and is the best path because MCP is a beta subset that excludes approvals and card management.

Best path today: api · Overall automatability: 8/10