Ramp vs Brex

Accounting sync

1. finance leadTransactions sync to QuickBooks, NetSuite, or Xero with GL account, class, and department mappings I control

   weight 3 · round to Ramp
   Ramp~partialclaimed6/10

   Ramp documents native QuickBooks, NetSuite, and Xero integrations with transaction sync, GL account coding, and reconciliation/matching tools (ramp-docs-25, ramp-docs-26, ramp-docs-27, ramp-docs-28, ramp-docs-32), plus multi-entity sync (ramp-docs-24). However, none of the evidence explicitly describes finance-lead control over class or department dimension mappings, only general GL account coding and reconciliation. Missing for 10: explicit documentation of class/department mapping configuration and user control over those field mappings during sync.

   • [claimed-docs] “Sync your transaction and reimbursement data to multiple entities in a single step, for less work.”
   • [claimed-docs] “Eliminate manual verification with Ramp's 3-way matching of purchase orders, receipts, and invoices”
   • [claimed-docs] “Gain confidence in your numbers with Ramp's built-in reconciliation tool that verifies balances between both platforms”
   • [claimed-docs] “Process vendor bills from start to finish: initiate your process in either NetSuite or Ramp, and complete it with Ramp payments”
   • [claimed-docs] “initiate your process in either Xero or Ramp and complete it with Ramp payments”
   • [claimed-docs] “the receipt is captured automatically, coded to the correct GL account, and auto-approved because it's within policy — no expense report fil…”

   proof ↗⚑ flag

   Brex—none0/10

   The evidence pack shows Brex has a one-click accounting sync feature, but it is documented only as syncing to Puzzle (brex-docs-17, 18, 40), with no mention of QuickBooks, NetSuite, or Xero, nor any documentation of finance-lead-controlled GL account, class, or department mapping for such syncs. Cost-center/department fields exist in the user API filters (brex-docs-19, 33) but these aren't tied to any accounting-sync mapping capability.

   • [claimed-docs] “Prepared expense data sync automatically to eliminate manual set up or matching between Brex and Puzzle.”
   • [claimed-docs] “Get global card and a treasury product that earns yield†, plus modern accounting from Puzzle.”
   • [claimed-docs] “Set up your accounting system in one click.”
   • [claimed-docs] “Added filter query parameters to List users: `name`, `email[]`, `status[]`, `manager_id[]`, `department_id[]`, `location_id[]`, `title_id[]`…”
   • [claimed-docs] “Added filter query parameters to List users: `name`, `email[]`, `status[]`, `manager_id[]`, `department_id[]`, `location_id[]`, `title_id[]`…”

   proof ↗⚑ flag

Close

1. finance leadSpend is coded as it happens — merchant, category, memo, receipt — so month-end close is a review, not an archaeology dig

   weight 2 · round drawn
   Ramp✓fullclaimed8/10

   Ramp documents real-time receipt capture, auto-fill of merchant/category/memo at swipe, GL coding, and auto-approval within policy (ramp-docs-8, ramp-docs-32, ramp-docs-21), plus reconciliation/3-way matching tools for close (ramp-docs-25, ramp-docs-26). This directly matches the story of spend being coded at time-of-swipe rather than reconstructed later. Missing for 10: independent/hands-on verification of accuracy claims and no explicit end-to-end month-end close workflow walkthrough beyond marketing copy.

   • [claimed-docs] “As soon as you swipe your card, Ramp captures the receipt and fills in memos and categories. Make edits and submit via SMS, Slack, or Micros…”
   • [claimed-docs] “the receipt is captured automatically, coded to the correct GL account, and auto-approved because it's within policy — no expense report fil…”
   • [claimed-docs] “Ramp gives you infinite teammates who work around the clock—flagging fraud, coding expenses, and enforcing policy.”
   • [claimed-docs] “Eliminate manual verification with Ramp's 3-way matching of purchase orders, receipts, and invoices”
   • [claimed-docs] “Gain confidence in your numbers with Ramp's built-in reconciliation tool that verifies balances between both platforms”
   • [claimed-docs] “Set submission requirements, enforce spend limits, and block risky merchants or categories all before spend happens.”

   proof ↗⚑ flag

   Brex✓fullclaimed8/10

   Brex documents real-time spend coding at point of transaction: receipt auto-matching to expenses (brex-docs-7, brex-docs-27), AI agents auto-categorizing/approving and writing memos (brex-docs-23, brex-docs-16, brex-docs-41), policy/budget enforcement applied per transaction (brex-docs-8, brex-docs-15, brex-docs-36), and explicit close-in-real-time messaging (brex-docs-37) plus one-click accounting sync (brex-docs-17, brex-docs-40). This directly maps to merchant/category/memo/receipt capture happening automatically rather than at month-end. Missing for 10: independent/hands-on verification that AI-drafted memos and auto-categorization are accurate in practice, and no third-party case study confirming reduced close time.

   • [claimed-docs] “The uri will be a pre-signed S3 URL allowing you to upload the receipt securely... we will try to match the receipt with existing expenses.”
   • [claimed-docs] “Upload receipt and match automatically.”
   • [claimed-docs] “AI assistants do employees' expenses for them, writing memos, fetching receipts, offering policy help, even filing reimbursements automatica…”
   • [claimed-docs] “Your review agent auto-approves low-risk expenses and requests, escalates exceptions, and follows up with anyone out of compliance.”
   • [claimed-docs] “Stop waiting for people to categorize, review, or approve spend. Let AI agents do it instantly, based on your policies and with total transp…”
   • [claimed-docs] “Set rules for how employees can spend, what they need to document, and who needs to approve. Brex AI applies them to every transaction.”
   • [claimed-docs] “Your audit agent monitors company expenses according to your internal processes and categorizes potential violations by risk level.”
   • [claimed-docs] “Automatically block out-of-policy purchases, with preset rules and limits.”
   • [claimed-docs] “Manage global spend and close the books in real time — with unmatched automation of manual expense work.”
   • [claimed-docs] “Prepared expense data sync automatically to eliminate manual set up or matching between Brex and Puzzle.”
   • [claimed-docs] “Set up your accounting system in one click.”

   proof ↗⚑ flag

Multi entity

1. finance leadRun multiple legal entities and currencies in one account with consolidated reporting and per-entity books

   weight 2 · round to Ramp
   Ramp~partialclaimed5/10

   Ramp has a dedicated multi-entity page indicating it can sync transactions and reimbursement data across multiple entities in one step, and reimbursements support 70+ countries/40 currencies, suggesting multi-entity/multi-currency support. However, the evidence pack lacks detail on consolidated reporting dashboards or explicit per-entity books/chart-of-accounts separation. Missing for 10: explicit consolidated reporting evidence, per-entity ledger/books detail, multi-currency accounting (not just reimbursement) specifics.

   • [claimed-docs] “Sync your transaction and reimbursement data to multiple entities in a single step, for less work.”
   • [claimed-docs] “Reimburse employees with confidence in more than 70 countries and 40 currencies, knowing they can be paid in two days or less in their local…”

   proof ↗⚑ flag

   Brex~partialclaimed3/10

   Evidence shows Brex's API supports a `legal_entity_id` field for filtering users, implying some multi-entity data modeling exists, and general mentions of 'global spend'/'more currencies' support, but there is no documentation of consolidated cross-entity reporting or dedicated per-entity books for finance close workflows. missing for 10: consolidated reporting across entities, per-entity books/ledgers, multi-currency accounting close workflow, any first-party or independent confirmation of multi-entity account structure.

   • [claimed-docs] “Added filter query parameters to List users: `name`, `email[]`, `status[]`, `manager_id[]`, `department_id[]`, `location_id[]`, `title_id[]`…”
   • [claimed-docs] “Added filter query parameters to List users: `name`, `email[]`, `status[]`, `manager_id[]`, `department_id[]`, `location_id[]`, `title_id[]`…”
   • [claimed-docs] “Manage global spend and close the books in real time — with unmatched automation of manual expense work.”
   • [claimed-docs] “Create a virtual card instantly to pay by card and earn rewards. Send ACH, checks, and wires from any bank account or a Brex business accoun…”
   • [claimed-docs] “Get global card and a treasury product that earns yield†, plus modern accounting from Puzzle.”

   proof ↗⚑ flag

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round drawn
   Ramp✓fullprobed9/10

   Ramp hosts a live, HTTP-200 llms.txt index (ramp-probe-1) plus a full suite of llms-guides/*.txt agent-oriented docs covering getting started, auth, webhooks, CLI, and MCP for AI agents (ramp-docs-1 through ramp-docs-6), directly matching the story of pointing an agent at machine-readable docs. Missing for 10: independent third-party confirmation that agents actually consume/parse this index successfully in practice.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.ramp.com/llms.txt # Ramp Developer API Machine-readable index for Ramp's Developer API documentati…”
   • [claimed-docs] “You'll create an access token and call the Transactions API to retrieve transaction data.”
   • [claimed-docs] “Ramp MCP allows you to securely connect Ramp with AI assistants like ChatGPT and Claude, so you can query Ramp data and take actions with na…”
   • [claimed-docs] “Give an AI agent read access, action authority, and (with approval) real purchasing power on Ramp — through MCP, the Ramp CLI, or both.”

   proof ↗⚑ flag

   Brex✓fullprobed9/10

   Brex hosts a live llms.txt at developer.brex.com/llms.txt (confirmed via HTTP 200 probe) that provides a structured table of contents for AI agents, and it also documents an official MCP server for agentic access to Brex data, showing clear agent-oriented documentation design. Missing for 10: independent third-party confirmation that agents actually consume llms.txt successfully in practice.

   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.brex.com/llms.txt # Brex Developer API > APIs to build on top of the Brex financial OS. ## T…”
   • [claimed-docs] “The Brex MCP server lets AI assistants interact directly with your Brex account: manage expenses, look up users, check cards, review banking…”
   • [probe] “official MCP server documented at https://developer.brex.com/docs/mcp”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round drawn
   Ramp~partialprobed6/10

   Ramp exposes a public API (OAuth token auth) and an official CLI that can be scripted 'from your terminal or AI agent' (ramp-docs-1, ramp-docs-2, ramp-docs-4, ramp-probe-3), which supports headless/automated use, and webhooks enable event-driven automation (ramp-docs-3). However, there is no explicit documentation of running Ramp in a CI pipeline, no CI/CD examples, and no mention of non-interactive auth flows suited for CI (e.g., service accounts) — missing for 10: explicit CI/CD usage examples, headless auth flow documentation for automated pipelines, independent confirmation of CLI use in CI.

   • [claimed-docs] “You'll create an access token and call the Transactions API to retrieve transaction data.”
   • [claimed-docs] “Ramp uses OAuth 2.0 for secure API access, providing granular permission control through scopes and supporting multiple authorization flows …”
   • [claimed-docs] “Authenticate with OAuth, manage expenses, approve bills, book travel, and more from your terminal or AI agent.”
   • [claimed-docs] “Webhooks allow your application to receive real-time notifications about events that occur in your Ramp account.”
   • [probe] “official CLI documented at https://github.com/ramp-public/ramp-cli”

   proof ↗⚑ flag

   Brex~partialclaimed6/10

   Brex exposes a full REST API with token-based auth (no interactive login required), webhook subscriptions, and Postman/Zapier/Workato/Pipedream automation examples (bulk card creation, scheduled exports), all of which support headless, non-interactive use suitable for scripted/CI-style automation. However there is no explicit mention of CI/CD pipelines, SDKs, or headless test/deploy tooling — missing for 10: explicit CI/CD integration docs, official SDKs for scripting, and confirmation of non-interactive token refresh/rotation suitable for unattended pipelines.

   • [claimed-docs] “Sign in to dashboard.brex.com as an account admin or card admin... Click Create Token. Create a name for your token... Choose what level of …”
   • [claimed-docs] “generate a user token from your Brex dashboard and pass it along in your API call headers”
   • [claimed-docs] “Register a URL to receive the webhooks using the [register webhook] endpoint.”
   • [claimed-docs] “Register an endpoint to start receiving selected webhook events”
   • [claimed-docs] “go to the Brex developer workspace which has collections for all of the Brex APIs”
   • [claimed-docs] “we’ll show you how to bulk create virtual cards for your employees”
   • [claimed-docs] “Monthly Export of Brex Card Transactions to CSV in Google Drive”
   • [claimed-docs] “Workato...to enable various use cases including bulk creating users, setting monthly limits for users, issuing virtual cards, and sending ve…”

   proof ↗⚑ flag

3. ai-native userConnect an agent via an official MCP server

   weight 3 · round to Ramp
   Ramp✓fullprobed9/10

   Ramp documents an official MCP server ('Ramp MCP') letting users connect AI assistants like ChatGPT and Claude to query data and take actions, with a dedicated support article and docs page confirming it exists and works (e.g., locking a card, finding missing receipts). This is corroborated by both first-party docs and a support-article walkthrough with concrete example prompts. Missing for 10: independent third-party (non-Ramp) hands-on review of the MCP server's reliability.

   • [claimed-docs] “Ramp MCP allows you to securely connect Ramp with AI assistants like ChatGPT and Claude, so you can query Ramp data and take actions with na…”
   • [claimed-docs] “Give an AI agent read access, action authority, and (with approval) real purchasing power on Ramp — through MCP, the Ramp CLI, or both.”
   • [claimed-docs] “Find transactions with missing receipts or memos in the last 14 days and draft reminder messages I can send to the team.”
   • [claimed-docs] “Lock my card — I can't find it.”
   • [probe] “official MCP server documented at https://support.ramp.com/hc/en-us/articles/45516494479891-Ramp-MCP”

   proof ↗⚑ flag

   Brex✓fullprobed8/10

   Brex is not itself an AI agent but a financial platform, so publishing an official MCP server is a fair ecosystem capability, and Brex documents a first-party MCP server letting AI assistants manage expenses, users, cards, transactions, and bills. Missing for 10: independent/hands-on confirmation of setup and reliability beyond vendor docs.

   • [claimed-docs] “The Brex MCP server lets AI assistants interact directly with your Brex account: manage expenses, look up users, check cards, review banking…”
   • [claimed-docs] “The Brex MCP server lets AI assistants interact directly with your Brex account: manage expenses, look up users, check cards, review banking…”
   • [probe] “official MCP server documented at https://developer.brex.com/docs/mcp”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round to Ramp
   Ramp✓fullprobed8/10

   Ramp documents an official CLI (docs.ramp.com/llms-guides/cli.txt and github.com/ramp-public/ramp-cli) explicitly designed for AI-native use, allowing OAuth authentication, expense management, bill approval, and travel booking 'from your terminal or AI agent,' and positions it alongside MCP for agentic workflows. Missing for 10: independent/hands-on verification of CLI usage and more detail on command coverage/maturity beyond first-party docs.

   • [claimed-docs] “Authenticate with OAuth, manage expenses, approve bills, book travel, and more from your terminal or AI agent.”
   • [claimed-docs] “Give an AI agent read access, action authority, and (with approval) real purchasing power on Ramp — through MCP, the Ramp CLI, or both.”
   • [probe] “official CLI documented at https://github.com/ramp-public/ramp-cli”

   proof ↗⚑ flag

   Brex—none0/10

   Evidence pack shows Brex's developer platform (APIs, Postman collection, MCP server, Zapier/Pipedream/Workato integrations) but no mention of an official CLI tool anywhere in docs or changelog.

   • [claimed-docs] “go to the Brex developer workspace which has collections for all of the Brex APIs”
   • [claimed-docs] “we’ll show you how to bulk create virtual cards for your employees”
   • [claimed-docs] “Monthly Export of Brex Card Transactions to CSV in Google Drive”
   • [claimed-docs] “Workato...to enable various use cases including bulk creating users, setting monthly limits for users, issuing virtual cards, and sending ve…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.brex.com/llms.txt # Brex Developer API > APIs to build on top of the Brex financial OS. ## T…”

   proof ↗⚑ flag

5. ai-native userDrive the product through a documented public API

   weight 3 · round to Ramp
   Ramp✓fullprobed9/10

   Ramp documents a public REST API (Transactions, OAuth 2.0 authorization, webhooks) with a machine-readable llms.txt index, plus a CLI and MCP server explicitly built for driving Ramp actions programmatically or via AI agents. This covers documented public API access comprehensively across auth, data retrieval, and actions. Missing for 10: independent third-party developer reports/hands-on confirmation of API robustness beyond Ramp's own docs.

   • [claimed-docs] “You'll create an access token and call the Transactions API to retrieve transaction data.”
   • [claimed-docs] “Ramp uses OAuth 2.0 for secure API access, providing granular permission control through scopes and supporting multiple authorization flows …”
   • [claimed-docs] “Webhooks allow your application to receive real-time notifications about events that occur in your Ramp account.”
   • [claimed-docs] “Authenticate with OAuth, manage expenses, approve bills, book travel, and more from your terminal or AI agent.”
   • [claimed-docs] “Ramp MCP allows you to securely connect Ramp with AI assistants like ChatGPT and Claude, so you can query Ramp data and take actions with na…”
   • [claimed-docs] “Give an AI agent read access, action authority, and (with approval) real purchasing power on Ramp — through MCP, the Ramp CLI, or both.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.ramp.com/llms.txt # Ramp Developer API Machine-readable index for Ramp's Developer API documentati…”
   • [probe] “official MCP server documented at https://support.ramp.com/hc/en-us/articles/45516494479891-Ramp-MCP”
   • [probe] “official CLI documented at https://github.com/ramp-public/ramp-cli”

   proof ↗⚑ flag

   Brex✓fullprobed8/10

   Brex has extensive documented public REST APIs (transactions, budgets, expenses, payments, onboarding, webhooks) with authentication via dashboard-generated tokens, Postman collections, and a llms.txt developer index, giving AI-native users a clear path to programmatically drive the product. Missing for 10: a live discoverable OpenAPI spec (probe found 404s on standard OpenAPI paths) and independent/hands-on third-party corroboration of API robustness beyond vendor docs.

   • [claimed-docs] “Sign in to dashboard.brex.com as an account admin or card admin... Click Create Token. Create a name for your token... Choose what level of …”
   • [claimed-docs] “The transactions API lets you view your transactions, accounts, and statements.”
   • [claimed-docs] “The budgets API lets you manage your Brex Budgets and Spend Limits.”
   • [claimed-docs] “The uri will be a pre-signed S3 URL allowing you to upload the receipt securely... we will try to match the receipt with existing expenses.”
   • [claimed-docs] “generate a user token from your Brex dashboard and pass it along in your API call headers”
   • [claimed-docs] “go to the Brex developer workspace which has collections for all of the Brex APIs”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.brex.com/llms.txt # Brex Developer API > APIs to build on top of the Brex financial OS. ## T…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.brex.com/openapi.json, https://developer.brex.com/swagger.json, https://developer.…”

   proof ↗⚑ flag

6. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round to Ramp
   Ramp✓fullprobed8/10

   Ramp's OAuth 2.0 implementation provides granular scoped permissions for API access (ramp-docs-2), and dedicated Agent Cards plus MCP/CLI docs show explicit support for issuing scoped credentials/action authority to AI agents specifically (ramp-docs-6, ramp-docs-7, ramp-docs-5). This directly matches the least-privilege-for-agents story. Missing for 10: independent/hands-on verification of scope granularity in practice and explicit documentation of per-agent credential revocation/audit trails.

   • [claimed-docs] “Ramp uses OAuth 2.0 for secure API access, providing granular permission control through scopes and supporting multiple authorization flows …”
   • [claimed-docs] “Give an AI agent read access, action authority, and (with approval) real purchasing power on Ramp — through MCP, the Ramp CLI, or both.”
   • [claimed-docs] “Issue cards, attach controls, and watch spend in real time — physical for employee in-person spend, virtual for reusable payment details, or…”
   • [claimed-docs] “Ramp MCP allows you to securely connect Ramp with AI assistants like ChatGPT and Claude, so you can query Ramp data and take actions with na…”
   • [probe] “official MCP server documented at https://support.ramp.com/hc/en-us/articles/45516494479891-Ramp-MCP”

   proof ↗⚑ flag

   Brex✓fullprobed7/10

   Brex's developer docs show admins can create named API tokens and choose specific data-access scopes at creation time (brex-docs-2, brex-docs-26), which is a direct least-privilege credentialing mechanism that would apply to any API consumer, including an AI agent calling the API or via the documented MCP server (brex-docs-3, brex-probe-3). Missing for 10: an explicit enumerated list of available scopes, agent-specific credential guidance, per-agent revocation/audit trail details, and independent corroboration of scope enforcement in practice.

   • [claimed-docs] “Sign in to dashboard.brex.com as an account admin or card admin... Click Create Token. Create a name for your token... Choose what level of …”
   • [claimed-docs] “generate a user token from your Brex dashboard and pass it along in your API call headers”
   • [claimed-docs] “The Brex MCP server lets AI assistants interact directly with your Brex account: manage expenses, look up users, check cards, review banking…”
   • [probe] “official MCP server documented at https://developer.brex.com/docs/mcp”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round drawn
   Ramp—none0/10

   Evidence shows Ramp offers a REST API, OAuth, webhooks, a CLI, and an MCP server, but nowhere mentions official client SDKs (e.g., Python, JS, Go libraries) for building against Ramp's API. Missing for 10: any documentation of official SDKs/client libraries in specific languages, package registry listings, or SDK-specific quickstart guides.

   • [claimed-docs] “You'll create an access token and call the Transactions API to retrieve transaction data.”
   • [claimed-docs] “Ramp uses OAuth 2.0 for secure API access, providing granular permission control through scopes and supporting multiple authorization flows …”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.ramp.com/llms.txt # Ramp Developer API Machine-readable index for Ramp's Developer API documentati…”
   • [probe] “official CLI documented at https://github.com/ramp-public/ramp-cli”

   proof ↗⚑ flag

   Brex—none0/10

   Brex documents REST APIs (OpenAPI specs), authentication, webhooks, a Postman workspace, and third-party integrations (Pipedream, Zapier, Workato), but nowhere in the evidence pack is there mention of official client-library SDKs (e.g., Node.js, Python, Java packages) that AI-native developers could build against.

   ⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Ramp✓fullclaimed8/10

   Ramp docs explicitly describe webhooks for real-time event notifications from a Ramp account, directly matching the story. Missing for 10: no details on event types/payload schema, delivery guarantees, or independent/hands-on verification of webhook reliability.

   • [claimed-docs] “Webhooks allow your application to receive real-time notifications about events that occur in your Ramp account.”

   proof ↗⚑ flag

   Brex✓fullclaimed8/10

   Brex documents a dedicated webhooks API and guide for registering endpoints and receiving selected events, including examples like referral activation, indicating genuine subscribe-to-event support. missing for 10: no independent/hands-on corroboration of webhook delivery reliability, and no explicit AI-native/agent-triggered subscription workflow shown.

   • [claimed-docs] “Register a URL to receive the webhooks using the [register webhook] endpoint.”
   • [claimed-docs] “you can receive a webhook when a referral you made has activated”
   • [claimed-docs] “Register an endpoint to start receiving selected webhook events”

   proof ↗⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round drawn
   Ramp✓fullprobed7/10

   Ramp Intelligence and related features surface AI-generated recommendations (recommended actions on spend requests, auto-coding of expenses, fraud flagging, contract parsing) directly inside the product, and Ramp MCP lets users query data and get AI-driven suggestions like drafting reminders for missing receipts. missing for 10: independent/hands-on validation of insight quality and a fuller first-party doc detailing the breadth of proactive insights beyond the marketing snippets and MCP examples.

   • [claimed-docs] “All spend requests come with a recommended action grounded in your policies, budgets, and funds, so you can approve or reject in seconds.”
   • [claimed-docs] “Ramp gives you infinite teammates who work around the clock—flagging fraud, coding expenses, and enforcing policy.”
   • [claimed-docs] “Drop in a contract or screenshot and Ramp's AI parses details and auto-fills the request form”
   • [claimed-docs] “Find transactions with missing receipts or memos in the last 14 days and draft reminder messages I can send to the team.”
   • [claimed-docs] “the receipt is captured automatically, coded to the correct GL account, and auto-approved because it's within policy — no expense report fil…”
   • [probe] “official MCP server documented at https://support.ramp.com/hc/en-us/articles/45516494479891-Ramp-MCP”

   proof ↗⚑ flag

   Brex✓fullclaimed7/10

   Brex AI features (audit agent, review agent, policy-based auto-approval, PO/payment matching suggestions) are documented as generating insights and suggestions directly from account/expense data. Evidence is first-party marketing/docs only, with no independent hands-on corroboration of these AI insight features in practice. missing for 10: independent/hands-on verification of AI insight quality, UI examples showing generated suggestions in context.

   • [claimed-docs] “Your audit agent monitors company expenses according to your internal processes and categorizes potential violations by risk level.”
   • [claimed-docs] “Your review agent auto-approves low-risk expenses and requests, escalates exceptions, and follows up with anyone out of compliance.”
   • [claimed-docs] “Brex AI will capture every itemized detail, suggest the matching PO, and draft a payment.”
   • [claimed-docs] “AI assistants do employees' expenses for them, writing memos, fetching receipts, offering policy help, even filing reimbursements automatica…”
   • [claimed-docs] “Stop waiting for people to categorize, review, or approve spend. Let AI agents do it instantly, based on your policies and with total transp…”
   • [claimed-docs] “Set rules for how employees can spend, what they need to document, and who needs to approve. Brex AI applies them to every transaction.”

   proof ↗⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round to Brex
   Ramp~partialprobed5/10

   Ramp offers webhooks, an API, MCP server, and CLI that agents can use to take actions like locking cards or drafting reminders, which supports agentic workflows, but these are largely triggered interactions rather than documented autonomous/scheduled background automations that run without a prompting event. Rules-based workflows (e.g., procurement routing, policy enforcement) run automatically but are conditional business rules, not general-purpose autonomous agent automations. missing for 10: explicit support for scheduled/recurring autonomous agent runs, evidence of persistent background agent execution without user-initiated trigger, and independent confirmation of such autonomous operation.

   • [claimed-docs] “Webhooks allow your application to receive real-time notifications about events that occur in your Ramp account.”
   • [claimed-docs] “Ramp MCP allows you to securely connect Ramp with AI assistants like ChatGPT and Claude, so you can query Ramp data and take actions with na…”
   • [claimed-docs] “Give an AI agent read access, action authority, and (with approval) real purchasing power on Ramp — through MCP, the Ramp CLI, or both.”
   • [claimed-docs] “Find transactions with missing receipts or memos in the last 14 days and draft reminder messages I can send to the team.”
   • [claimed-docs] “Lock my card — I can't find it.”
   • [claimed-docs] “Rules-based workflows route requests to the right stakeholders automatically based on vendor type, spend category, or dollar amount”
   • [probe] “official MCP server documented at https://support.ramp.com/hc/en-us/articles/45516494479891-Ramp-MCP”
   • [probe] “official CLI documented at https://github.com/ramp-public/ramp-cli”

   proof ↗⚑ flag

   Brex✓fullclaimed7/10

   Brex documents autonomous background agents (audit agent monitoring expenses, review agent auto-approving low-risk items and escalating exceptions) plus webhook events and third-party automation platforms (Zapier, Workato, Pipedream) that can run unattended once configured, and an MCP server for AI assistant integration. This covers the core 'runs autonomously in background' story via policy-driven agents and event-driven webhooks/automations. missing for 10: independent/hands-on verification that these agents truly run unattended without human triggers, and technical detail on scheduling/trigger architecture beyond marketing copy

   • [claimed-docs] “Your audit agent monitors company expenses according to your internal processes and categorizes potential violations by risk level.”
   • [claimed-docs] “Your review agent auto-approves low-risk expenses and requests, escalates exceptions, and follows up with anyone out of compliance.”
   • [claimed-docs] “Stop waiting for people to categorize, review, or approve spend. Let AI agents do it instantly, based on your policies and with total transp…”
   • [claimed-docs] “Register a URL to receive the webhooks using the [register webhook] endpoint.”
   • [claimed-docs] “Register an endpoint to start receiving selected webhook events”
   • [claimed-docs] “The Brex MCP server lets AI assistants interact directly with your Brex account: manage expenses, look up users, check cards, review banking…”
   • [claimed-docs] “Workato...to enable various use cases including bulk creating users, setting monthly limits for users, issuing virtual cards, and sending ve…”
   • [claimed-docs] “we’ll show you how to bulk create virtual cards for your employees”

   proof ↗⚑ flag

3. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round to Brex
   Ramp~partialprobed5/10

   Ramp offers agentic automation ('infinite teammates' handling fraud flagging, coding, policy enforcement) and lets users delegate tasks via natural language through its MCP integration (e.g., 'Find transactions with missing receipts...', 'Lock my card'), but these delegated-task examples run through external AI assistants (ChatGPT, Claude) connected via MCP rather than a native, built-in conversational assistant inside the Ramp product itself. Missing for 10: evidence of an in-app chat/assistant UI natively embedded in Ramp (not via MCP to third-party LLMs), and independent confirmation of task delegation working end-to-end within the product.

   • [claimed-docs] “Ramp MCP allows you to securely connect Ramp with AI assistants like ChatGPT and Claude, so you can query Ramp data and take actions with na…”
   • [claimed-docs] “Give an AI agent read access, action authority, and (with approval) real purchasing power on Ramp — through MCP, the Ramp CLI, or both.”
   • [claimed-docs] “Ramp gives you infinite teammates who work around the clock—flagging fraud, coding expenses, and enforcing policy.”
   • [claimed-docs] “Find transactions with missing receipts or memos in the last 14 days and draft reminder messages I can send to the team.”
   • [claimed-docs] “Lock my card — I can't find it.”
   • [probe] “official MCP server documented at https://support.ramp.com/hc/en-us/articles/45516494479891-Ramp-MCP”

   proof ↗⚑ flag

   Brex✓fullclaimed7/10

   Brex documents built-in AI agents (audit agent, review agent, Brex AI) that autonomously categorize expenses, auto-approve low-risk spend, write memos, fetch receipts, and file reimbursements, allowing users to delegate financial tasks directly within the product. This is distinct from the MCP server (which is for external AI clients) and represents genuine in-product agentic delegation. Missing for 10: independent/hands-on verification of these AI agent features actually working, and more detail on how users configure/invoke the assistant.

   • [claimed-docs] “Your audit agent monitors company expenses according to your internal processes and categorizes potential violations by risk level.”
   • [claimed-docs] “Your review agent auto-approves low-risk expenses and requests, escalates exceptions, and follows up with anyone out of compliance.”
   • [claimed-docs] “AI assistants do employees' expenses for them, writing memos, fetching receipts, offering policy help, even filing reimbursements automatica…”
   • [claimed-docs] “Stop waiting for people to categorize, review, or approve spend. Let AI agents do it instantly, based on your policies and with total transp…”
   • [claimed-docs] “Set rules for how employees can spend, what they need to document, and who needs to approve. Brex AI applies them to every transaction.”
   • [claimed-docs] “Brex AI will capture every itemized detail, suggest the matching PO, and draft a payment.”

   proof ↗⚑ flag

4. ai-native userOperate the product with natural-language commands

   weight 2 · round to Ramp
   Ramp✓fullprobed8/10

   Ramp ships an official MCP server and CLI explicitly designed for natural-language operation ("query Ramp data and take actions with natural language"), with documented examples like locking a card or drafting reminder messages via plain-English commands, plus a CLI usable directly by AI agents. Missing for 10: independent/hands-on validation beyond vendor docs and no broad third-party confirmation of reliability across all agentic actions.

   • [claimed-docs] “Ramp MCP allows you to securely connect Ramp with AI assistants like ChatGPT and Claude, so you can query Ramp data and take actions with na…”
   • [claimed-docs] “Give an AI agent read access, action authority, and (with approval) real purchasing power on Ramp — through MCP, the Ramp CLI, or both.”
   • [claimed-docs] “Find transactions with missing receipts or memos in the last 14 days and draft reminder messages I can send to the team.”
   • [claimed-docs] “Lock my card — I can't find it.”
   • [claimed-docs] “Authenticate with OAuth, manage expenses, approve bills, book travel, and more from your terminal or AI agent.”
   • [probe] “official MCP server documented at https://support.ramp.com/hc/en-us/articles/45516494479891-Ramp-MCP”
   • [probe] “official CLI documented at https://github.com/ramp-public/ramp-cli”

   proof ↗⚑ flag

   Brex~partialprobed7/10

   Brex documents a first-party MCP server explicitly built so 'AI assistants interact directly with your Brex account... through natural language' for expenses, cards, banking, and bills, plus AI agents (audit/review) that act on policies automatically. This directly supports natural-language operation for AI-native users, though it's vendor-documented only. Missing for 10: independent/hands-on evidence of the MCP server's natural-language commands working reliably, and detail on command coverage limits.

   • [claimed-docs] “The Brex MCP server lets AI assistants interact directly with your Brex account: manage expenses, look up users, check cards, review banking…”
   • [claimed-docs] “The Brex MCP server lets AI assistants interact directly with your Brex account: manage expenses, look up users, check cards, review banking…”
   • [claimed-docs] “AI assistants do employees' expenses for them, writing memos, fetching receipts, offering policy help, even filing reimbursements automatica…”
   • [claimed-docs] “Stop waiting for people to categorize, review, or approve spend. Let AI agents do it instantly, based on your policies and with total transp…”
   • [probe] “official MCP server documented at https://developer.brex.com/docs/mcp”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round to Brex
   Ramp—none0/10

   Evidence shows Ramp has API docs, OAuth guides, webhooks, and a machine-readable llms.txt index, but nothing describes an interactive API reference with runnable/live code examples (e.g., a Swagger/Postman-style explorer). Missing for 10: any mention of an interactive console or runnable example feature in the docs.

   • [claimed-docs] “You'll create an access token and call the Transactions API to retrieve transaction data.”
   • [claimed-docs] “Ramp uses OAuth 2.0 for secure API access, providing granular permission control through scopes and supporting multiple authorization flows …”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.ramp.com/llms.txt # Ramp Developer API Machine-readable index for Ramp's Developer API documentati…”

   proof ↗⚑ flag

   Brex~partialprobed4/10

   Brex provides detailed API reference docs (openapi/*.md pages) and a Postman workspace with collections for all APIs, which allows some hands-on exploration, but there's no evidence of an interactive in-browser API reference with embedded runnable examples (e.g., a Swagger/OpenAPI explorer); a probe for standard openapi.json/swagger endpoints returned 404s. Missing for 10: an embedded interactive console/try-it feature, confirmation of runnable code snippets directly in docs, and independent corroboration of hands-on use.

   • [claimed-docs] “go to the Brex developer workspace which has collections for all of the Brex APIs”
   • [claimed-docs] “The transactions API lets you view your transactions, accounts, and statements.”
   • [claimed-docs] “The budgets API lets you manage your Brex Budgets and Spend Limits.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.brex.com/openapi.json, https://developer.brex.com/swagger.json, https://developer.…”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round to Brex
   Ramp~partialprobed3/10

   Ramp exposes a machine-readable llms.txt index for its Developer API docs, which is AI-native friendly, but there's no evidence of an actual OpenAPI/Swagger spec file being published or downloadable. Missing for 10: an explicit OpenAPI/Swagger spec document, a documented download endpoint, or third-party confirmation that the API schema is available in a standard machine-readable spec format.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.ramp.com/llms.txt # Ramp Developer API Machine-readable index for Ramp's Developer API documentati…”
   • [claimed-docs] “You'll create an access token and call the Transactions API to retrieve transaction data.”

   proof ↗⚑ flag

   Brex~partialprobed4/10

   Brex publishes API reference docs under an /openapi/ path pattern (transactions_api.md, budgets_api.md, expenses_api.md, etc.) and offers a Postman collection covering all Brex APIs, both of which imply structured, machine-readable spec data. However, a direct probe for standard OpenAPI/Swagger JSON files (openapi.json, swagger.json, etc.) returned 404s, meaning there is no confirmed single downloadable OpenAPI spec file. Missing for 10: a discoverable raw OpenAPI/Swagger JSON or YAML file, and confirmation that the Postman collection is exported in OpenAPI format.

   • [claimed-docs] “The transactions API lets you view your transactions, accounts, and statements.”
   • [claimed-docs] “The budgets API lets you manage your Brex Budgets and Spend Limits.”
   • [claimed-docs] “The uri will be a pre-signed S3 URL allowing you to upload the receipt securely... we will try to match the receipt with existing expenses.”
   • [claimed-docs] “go to the Brex developer workspace which has collections for all of the Brex APIs”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.brex.com/openapi.json, https://developer.brex.com/swagger.json, https://developer.…”

   proof ↗⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round drawn
   Ramp—none0/10

   No evidence of a sandbox/test environment for Ramp's API, CLI, or MCP integrations; all docs reference live transactions, cards, and production data flows. Missing for 10: any mention of a sandbox/test mode, test API keys, or non-production environment for developers/AI agents.

   ⚑ flag

   Brex—none0/10

   No evidence of a sandbox/test environment separate from production data; the docs pack covers authentication, webhooks, MCP server, and API endpoints but never mentions a sandbox mode or test credentials. Missing for 10: any mention of a sandbox environment, test API keys, or documentation distinguishing test vs. production data.

   ⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Ramp—none0/10

   Evidence shows Ramp has an API, OAuth, webhooks, CLI, and MCP server, but nothing in the pack documents API versioning practices or a formal deprecation policy. missing for 10: versioning scheme documentation, deprecation policy/notice process, changelog or migration guidance for breaking changes.

   ⚑ flag

   Brex—none0/10

   The evidence shows a changelog tracking feature additions (e.g., new filter params, policy fields) but nothing documenting API versioning scheme or a deprecation policy for breaking changes. No mention of version numbers, sunset timelines, or backward-compatibility guarantees appears anywhere in the pack.

   • [claimed-docs] “Added `policy` to booking objects, exposing whether a booking was out of policy and which travel policy rules it violated.”
   • [claimed-docs] “Added filter query parameters to List users: `name`, `email[]`, `status[]`, `manager_id[]`, `department_id[]`, `location_id[]`, `title_id[]`…”
   • [claimed-docs] “Added filter query parameters to List users: `name`, `email[]`, `status[]`, `manager_id[]`, `department_id[]`, `location_id[]`, `title_id[]`…”

   proof ↗⚑ flag

Ai coding

1. ai-native userAI codes and audits expenses for me — reading receipts, suggesting categories and memos, and catching duplicates or fraud

   weight 2 · round drawn
   Ramp✓fullclaimed8/10

   Ramp's docs show automatic receipt capture with AI-filled memos/categories (ramp-docs-8, ramp-docs-32), OCR line-item accuracy (ramp-docs-16), fraud flagging and expense coding via 'infinite teammates' AI (ramp-docs-21), duplicate/missing-item detection via MCP prompts (ramp-docs-29), and policy/match-based auditing (ramp-docs-17, ramp-docs-25, ramp-docs-9). This covers reading receipts, categorization/memo suggestion, and fraud/duplicate catching across first-party marketing and support docs. Missing for 10: independent/hands-on verification of accuracy claims and explicit named 'duplicate detection' feature documentation beyond marketing copy.

   • [claimed-docs] “As soon as you swipe your card, Ramp captures the receipt and fills in memos and categories. Make edits and submit via SMS, Slack, or Micros…”
   • [claimed-docs] “Ramp's OCR captures each detail and line item with 99% accuracy.”
   • [claimed-docs] “Ramp checks every line item with two and three-way matching, so you know if something's off before sending.”
   • [claimed-docs] “Ramp gives you infinite teammates who work around the clock—flagging fraud, coding expenses, and enforcing policy.”
   • [claimed-docs] “Find transactions with missing receipts or memos in the last 14 days and draft reminder messages I can send to the team.”
   • [claimed-docs] “the receipt is captured automatically, coded to the correct GL account, and auto-approved because it's within policy — no expense report fil…”
   • [claimed-docs] “Set submission requirements, enforce spend limits, and block risky merchants or categories all before spend happens.”

   proof ↗⚑ flag

   Brex✓fullclaimed8/10

   Brex AI explicitly offers audit and review agents that read receipts, categorize/flag violations by risk level, auto-approve low-risk expenses, and write memos/fetch receipts/file reimbursements automatically, matching the story closely. missing for 10: independent/hands-on verification of accuracy (duplicate/fraud catching specifically) and no third-party corroboration beyond vendor marketing copy.

   • [claimed-docs] “Your audit agent monitors company expenses according to your internal processes and categorizes potential violations by risk level.”
   • [claimed-docs] “Your review agent auto-approves low-risk expenses and requests, escalates exceptions, and follows up with anyone out of compliance.”
   • [claimed-docs] “AI assistants do employees' expenses for them, writing memos, fetching receipts, offering policy help, even filing reimbursements automatica…”
   • [claimed-docs] “Stop waiting for people to categorize, review, or approve spend. Let AI agents do it instantly, based on your policies and with total transp…”
   • [claimed-docs] “The uri will be a pre-signed S3 URL allowing you to upload the receipt securely... we will try to match the receipt with existing expenses.”

   proof ↗⚑ flag

Ai policy

1. ai-native userAn AI assistant enforces policy conversationally — chasing missing receipts, explaining declines, and answering "can I expense this?" before the spend happens

   weight 2 · round to Ramp
   Ramp✓fullprobed7/10

   Ramp's MCP/AI assistant explicitly chases missing receipts with drafted reminders (ramp-docs-29, ramp-docs-13), and policy enforcement happens conversationally with recommended actions and pre-spend policy visibility (ramp-docs-9, ramp-docs-10, ramp-docs-18). This covers the core of the story, though 'explaining declines' and answering 'can I expense this?' pre-spend are only indirectly evidenced via policy-status/recommended-action features rather than a direct conversational decline-explanation example. Missing for 10: independent/hands-on confirmation of the assistant explaining a specific decline conversationally, and an explicit pre-spend Q&A example beyond travel-booking policy status.

   • [claimed-docs] “Find transactions with missing receipts or memos in the last 14 days and draft reminder messages I can send to the team.”
   • [claimed-docs] “Let Ramp send reminders for missing items or request repayments for you.”
   • [claimed-docs] “Set submission requirements, enforce spend limits, and block risky merchants or categories all before spend happens.”
   • [claimed-docs] “All spend requests come with a recommended action grounded in your policies, budgets, and funds, so you can approve or reject in seconds.”
   • [claimed-docs] “See policy status for every option. No digging through static policy PDFs or wondering if trips will get rejected.”
   • [claimed-docs] “Ramp MCP allows you to securely connect Ramp with AI assistants like ChatGPT and Claude, so you can query Ramp data and take actions with na…”
   • [probe] “official MCP server documented at https://support.ramp.com/hc/en-us/articles/45516494479891-Ramp-MCP”

   proof ↗⚑ flag

   Brex~partialclaimed7/10

   Brex explicitly markets AI agents that follow up on out-of-compliance spend, fetch receipts, and offer policy help ('AI assistants do employees' expenses... fetching receipts, offering policy help' and 'review agent... follows up with anyone out of compliance'), plus an MCP server letting assistants query expenses/policy conversationally. However, there's no concrete evidence of the assistant proactively answering 'can I expense this?' before spend occurs or explaining specific decline reasons conversationally. Missing for 10: documented pre-spend conversational policy checks, explicit decline-explanation flows, and independent/hands-on confirmation of these AI behaviors in practice.

   • [claimed-docs] “Your audit agent monitors company expenses according to your internal processes and categorizes potential violations by risk level.”
   • [claimed-docs] “Your review agent auto-approves low-risk expenses and requests, escalates exceptions, and follows up with anyone out of compliance.”
   • [claimed-docs] “AI assistants do employees' expenses for them, writing memos, fetching receipts, offering policy help, even filing reimbursements automatica…”
   • [claimed-docs] “Stop waiting for people to categorize, review, or approve spend. Let AI agents do it instantly, based on your policies and with total transp…”
   • [claimed-docs] “The Brex MCP server lets AI assistants interact directly with your Brex account: manage expenses, look up users, check cards, review banking…”
   • [claimed-docs] “Set rules for how employees can spend, what they need to document, and who needs to approve. Brex AI applies them to every transaction.”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round to Brex
   Ramp~partialclaimed4/10

   Ramp's API/MCP/CLI let users query and act on data programmatically (e.g., finding all transactions missing receipts across the last 14 days) and sync data to multiple entities in one step, suggesting some bulk-style automation. However, there is no explicit documentation of true bulk endpoints (e.g., batch update/create across many items) or bulk card issuance/approval workflows via API. Missing for 10: explicit bulk API endpoints, batch transaction/approval operations, and independent confirmation of bulk-scale automation.

   • [claimed-docs] “Sync your transaction and reimbursement data to multiple entities in a single step, for less work.”
   • [claimed-docs] “Find transactions with missing receipts or memos in the last 14 days and draft reminder messages I can send to the team.”
   • [claimed-docs] “You'll create an access token and call the Transactions API to retrieve transaction data.”
   • [claimed-docs] “Ramp MCP allows you to securely connect Ramp with AI assistants like ChatGPT and Claude, so you can query Ramp data and take actions with na…”
   • [claimed-docs] “Authenticate with OAuth, manage expenses, approve bills, book travel, and more from your terminal or AI agent.”

   proof ↗⚑ flag

   Brex✓fullclaimed8/10

   Brex documents explicit bulk operations via automation platforms (bulk create virtual cards via Pipedream, bulk create users/set limits via Workato) and supports filtering/listing at scale via API query params, plus bulk-friendly endpoints for users, cards, vendors, and expenses. This is corroborated by first-party developer docs across multiple integration guides, not just a single mention. Missing for 10: no native in-product bulk-action UI evidence or independent hands-on confirmation of bulk API throughput/limits.

   • [claimed-docs] “we’ll show you how to bulk create virtual cards for your employees”
   • [claimed-docs] “Workato...to enable various use cases including bulk creating users, setting monthly limits for users, issuing virtual cards, and sending ve…”
   • [claimed-docs] “Added filter query parameters to List users: `name`, `email[]`, `status[]`, `manager_id[]`, `department_id[]`, `location_id[]`, `title_id[]`…”
   • [claimed-docs] “Added filter query parameters to List users: `name`, `email[]`, `status[]`, `manager_id[]`, `department_id[]`, `location_id[]`, `title_id[]`…”
   • [claimed-docs] “go to the Brex developer workspace which has collections for all of the Brex APIs”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Ramp
   Ramp✓fullclaimed8/10

   Ramp supports webhooks for real-time event notifications, rules-based workflows that automatically route requests based on vendor/category/amount, spend limits and merchant blocking enforced pre-spend, automatic reminders/repayment requests, and auto-approval of in-policy transactions without manual filing — collectively demonstrating rule-driven automatic actions on events across its expense/procurement/card platform. Missing for 10: a documented general-purpose 'if-this-then-that' custom rule builder exposed to end users (vs. built-in policy categories) and independent/hands-on corroboration of these automation flows working as described.

   • [claimed-docs] “Webhooks allow your application to receive real-time notifications about events that occur in your Ramp account.”
   • [claimed-docs] “Set submission requirements, enforce spend limits, and block risky merchants or categories all before spend happens.”
   • [claimed-docs] “Create personalized workflows that only notify the right people, based on spend amount or team role, and keep visibility high.”
   • [claimed-docs] “Let Ramp send reminders for missing items or request repayments for you.”
   • [claimed-docs] “Rules-based workflows route requests to the right stakeholders automatically based on vendor type, spend category, or dollar amount”
   • [claimed-docs] “the receipt is captured automatically, coded to the correct GL account, and auto-approved because it's within policy — no expense report fil…”

   proof ↗⚑ flag

   Brex~partialclaimed7/10

   Brex offers webhooks that fire on events (brex-docs-1, brex-docs-25, brex-docs-35) plus built-in policy rules that auto-trigger actions like blocking out-of-policy spend, auto-approving low-risk expenses, and escalating exceptions (brex-docs-8, brex-docs-9, brex-docs-16, brex-docs-36, brex-docs-41). Third-party integrations (Zapier, Workato, Pipedream) extend this into custom event-triggered automations (brex-docs-30, brex-docs-31, brex-docs-32). Missing for 10: a native no-code rule-builder UI for arbitrary custom triggers/actions beyond preset expense/travel/approval policies, and independent hands-on confirmation that webhook-to-action automations work reliably in practice.

   • [claimed-docs] “Register a URL to receive the webhooks using the [register webhook] endpoint.”
   • [claimed-docs] “Set rules for how employees can spend, what they need to document, and who needs to approve. Brex AI applies them to every transaction.”
   • [claimed-docs] “Create limits for stipends, travel, procurement, and more. Auto-enforced controls empower employees to spend with confidence.”
   • [claimed-docs] “Your review agent auto-approves low-risk expenses and requests, escalates exceptions, and follows up with anyone out of compliance.”
   • [claimed-docs] “Automatically block out-of-policy purchases, with preset rules and limits.”
   • [claimed-docs] “Stop waiting for people to categorize, review, or approve spend. Let AI agents do it instantly, based on your policies and with total transp…”
   • [claimed-docs] “we’ll show you how to bulk create virtual cards for your employees”
   • [claimed-docs] “Monthly Export of Brex Card Transactions to CSV in Google Drive”
   • [claimed-docs] “Workato...to enable various use cases including bulk creating users, setting monthly limits for users, issuing virtual cards, and sending ve…”
   • [claimed-docs] “Register an endpoint to start receiving selected webhook events”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Brex
   Ramp—none0/10

   Ramp's automation is event-driven (webhooks) or rules-based (route requests, reminders, auto-rebooking) rather than a documented recurring-job/scheduler capability that an AI agent could invoke via API, MCP, or CLI. No evidence of cron-like or interval-based scheduling for workflows.

   ⚑ flag

   Brex~partialclaimed3/10

   Brex offers webhooks for event-driven automation and third-party integration examples (Zapier, Workato, Pipedream) that can implement recurring workflows like a 'Monthly Export of Brex Card Transactions to CSV', but there is no native Brex scheduling/cron API for recurring jobs — the scheduling logic lives entirely in external tools. Missing for 10: a first-party recurring-job/schedule API or documented native cron-like trigger, and any hands-on evidence that AI-native users actually configure recurring automations directly through Brex rather than third-party platforms.

   • [claimed-docs] “Monthly Export of Brex Card Transactions to CSV in Google Drive”
   • [claimed-docs] “Workato...to enable various use cases including bulk creating users, setting monthly limits for users, issuing virtual cards, and sending ve…”
   • [claimed-docs] “we’ll show you how to bulk create virtual cards for your employees”
   • [claimed-docs] “Register a URL to receive the webhooks using the [register webhook] endpoint.”
   • [claimed-docs] “Register an endpoint to start receiving selected webhook events”

   proof ↗⚑ flag

4. ai-native userVersion, review, and roll back my automations

   weight 1 · round drawn
   Ramp—none0/10

   Ramp's evidence covers automating expense/spend workflows, MCP/CLI/API access, and policy enforcement, but there is no mention of versioning automations/workflows, reviewing changes, or rolling back to prior configurations. Rules-based workflows (docs-23) and permissioning are described but no version history, diff/audit trail, or rollback mechanism is documented.

   ⚑ flag

   Brex—none0/10

   No evidence of any versioning, review workflow, or rollback mechanism for automations/policies/agents — the docs describe automation features (approvals, expense policies, AI agents, MCP) but nothing about version history, change review, or reverting configurations.

   ⚑ flag

Bill pay

1. finance leadRun accounts payable in the same platform — capture invoices, route approvals, and pay vendors by ACH, check, or wire

   weight 2 · round to Brex
   Ramp~partialclaimed6/10

   Ramp's Bill Pay evidence shows invoice OCR capture (99% accuracy), 2/3-way matching, and rules-based approval routing (ramp-docs-16, ramp-docs-17, ramp-docs-23), plus 'complete it with Ramp payments' in NetSuite/Xero integrations (ramp-docs-27, ramp-docs-28) confirming payment execution within the platform. However, none of the evidence explicitly states support for ACH, check, or wire as distinct payment rails for vendor payments. Missing for 10: explicit documentation of ACH/check/wire payment method options, and independent/hands-on confirmation of the full AP workflow.

   • [claimed-docs] “Ramp's OCR captures each detail and line item with 99% accuracy.”
   • [claimed-docs] “Ramp checks every line item with two and three-way matching, so you know if something's off before sending.”
   • [claimed-docs] “Rules-based workflows route requests to the right stakeholders automatically based on vendor type, spend category, or dollar amount”
   • [claimed-docs] “Process vendor bills from start to finish: initiate your process in either NetSuite or Ramp, and complete it with Ramp payments”
   • [claimed-docs] “initiate your process in either Xero or Ramp and complete it with Ramp payments”

   proof ↗⚑ flag

   Brex✓fullclaimed8/10

   Brex Bill Pay covers invoice capture (AI extracts itemized detail and matches PO), configurable multi-level approval routing by amount/vendor/role, vendor onboarding via secure payment-detail links, and payment via virtual card, ACH, checks, or wires from a Brex or external bank account — all in one platform, backed by both marketing docs and API endpoints (vendor creation, payments API). missing for 10: independent/hands-on verification of AP workflow reliability (only vendor docs, no third-party case study or user report specific to bill pay), and detail on check-payment mechanics/timing.

   • [claimed-docs] “Tailor multi-level approval flows based on amount, vendor, employee role, and more — and Brex will route for you automatically to ensure the…”
   • [claimed-docs] “Enter your vendor's email address and Brex will send a secure link where they can upload their payment details.”
   • [claimed-docs] “Brex AI will capture every itemized detail, suggest the matching PO, and draft a payment.”
   • [claimed-docs] “Create a virtual card instantly to pay by card and earn rewards. Send ACH, checks, and wires from any bank account or a Brex business accoun…”
   • [claimed-docs] “This endpoint creates a new vendor.”
   • [claimed-docs] “Eliminate data entry, automate approvals, and spin up virtual cards in one click to maximize your rewards.”

   proof ↗⚑ flag

Card controls

1. finance leadRestrict cards by category, merchant, and amount — and the platform auto-locks or declines out-of-policy spend at the point of sale

   weight 3 · round to Ramp
   Ramp✓fullclaimed8/10

   Docs explicitly describe issuing cards with attached controls, custom permissions per vendor/category/team, blocking risky merchants or categories before spend happens, and per-vendor spending limits on virtual cards — matching category/merchant/amount restriction and pre-spend enforcement. Missing for 10: independent/hands-on confirmation of real-time point-of-sale decline behavior and explicit 'auto-lock' mechanics beyond policy blocking language.

   • [claimed-docs] “Issue cards, attach controls, and watch spend in real time — physical for employee in-person spend, virtual for reusable payment details, or…”
   • [claimed-docs] “Set submission requirements, enforce spend limits, and block risky merchants or categories all before spend happens.”
   • [claimed-docs] “Create custom virtual cards and set permissions for everything from ad marketplace spend to remote work stipends, for individual teams or yo…”
   • [claimed-docs] “A finance team issues instant virtual cards for each software subscription with per-vendor spending limits, giving real-time visibility into…”
   • [claimed-docs] “the receipt is captured automatically, coded to the correct GL account, and auto-approved because it's within policy — no expense report fil…”

   proof ↗⚑ flag

   Brex✓fullclaimed7/10

   Brex's product docs explicitly describe auto-blocking out-of-policy purchases with preset rules and limits, auto-enforced spend controls, and a Budgets/Spend Limits API for programmatic control, matching the finance-lead story of restricting and declining spend by policy. Missing for 10: explicit documentation of category/merchant-level rule granularity and independent/hands-on confirmation that point-of-sale declines work as described in practice.

   • [claimed-docs] “Automatically block out-of-policy purchases, with preset rules and limits.”
   • [claimed-docs] “Create limits for stipends, travel, procurement, and more. Auto-enforced controls empower employees to spend with confidence.”
   • [claimed-docs] “Set rules for how employees can spend, what they need to document, and who needs to approve. Brex AI applies them to every transaction.”
   • [claimed-docs] “The budgets API lets you manage your Brex Budgets and Spend Limits.”
   • [claimed-docs] “Stop waiting for people to categorize, review, or approve spend. Let AI agents do it instantly, based on your policies and with total transp…”

   proof ↗⚑ flag

Card issuance

1. founderIssue physical and virtual corporate cards to the team in minutes, each with its own spend limit

   weight 3 · round drawn
   Ramp✓fullclaimed8/10

   Ramp docs explicitly describe issuing physical and virtual cards with per-card/per-vendor spend limits, permissions, and real-time visibility (ramp-docs-7, ramp-docs-11, ramp-docs-31), matching the founder story closely. Missing for 10: independent hands-on confirmation of the 'minutes' setup speed and explicit UI walkthrough evidence beyond marketing copy.

   • [claimed-docs] “Issue cards, attach controls, and watch spend in real time — physical for employee in-person spend, virtual for reusable payment details, or…”
   • [claimed-docs] “Create custom virtual cards and set permissions for everything from ad marketplace spend to remote work stipends, for individual teams or yo…”
   • [claimed-docs] “A finance team issues instant virtual cards for each software subscription with per-vendor spending limits, giving real-time visibility into…”
   • [claimed-docs] “Set submission requirements, enforce spend limits, and block risky merchants or categories all before spend happens.”

   proof ↗⚑ flag

   Brex✓fullclaimed8/10

   Brex documents physical and virtual card issuance on Mastercard with instant/one-click virtual card creation, per-card/employee spend limits and budgets, mobile app management, and bulk issuance via Workato/Pipedream integrations for teams. This directly matches the founder story of quickly issuing cards with individual limits. Missing for 10: independent hands-on timing verification ("minutes") and no first-party case study explicitly confirming founder-level self-service issuance speed.

   • [claimed-docs] “Physical and virtual cards issued on the leading worldwide network, Mastercard, with acceptance in 210+ countries and territories.”
   • [claimed-docs] “Get a card limit that keeps pace with your business based on financial factors such as revenue or dollars raised.”
   • [claimed-docs] “Manage your card from your phone. Pay with Apple Pay, cancel your card, and view your spend all in one app.”
   • [claimed-docs] “The budgets API lets you manage your Brex Budgets and Spend Limits.”
   • [claimed-docs] “Create limits for stipends, travel, procurement, and more. Auto-enforced controls empower employees to spend with confidence.”
   • [claimed-docs] “we’ll show you how to bulk create virtual cards for your employees”
   • [claimed-docs] “Workato...to enable various use cases including bulk creating users, setting monthly limits for users, issuing virtual cards, and sending ve…”
   • [claimed-docs] “Eliminate data entry, automate approvals, and spin up virtual cards in one click to maximize your rewards.”

   proof ↗⚑ flag

Virtual cards

1. finance leadCreate single-vendor virtual cards for SaaS subscriptions and procurement so one compromised vendor never exposes shared credit

   weight 2 · round to Ramp
   Ramp✓fullclaimed8/10

   Ramp documents creating custom/virtual cards with per-vendor spend limits explicitly for SaaS subscriptions, avoiding shared card numbers (ramp-docs-31, ramp-docs-11, ramp-docs-7), plus spend controls and merchant blocking (ramp-docs-9). missing for 10: independent/hands-on third-party corroboration beyond vendor marketing copy.

   • [claimed-docs] “A finance team issues instant virtual cards for each software subscription with per-vendor spending limits, giving real-time visibility into…”
   • [claimed-docs] “Create custom virtual cards and set permissions for everything from ad marketplace spend to remote work stipends, for individual teams or yo…”
   • [claimed-docs] “Issue cards, attach controls, and watch spend in real time — physical for employee in-person spend, virtual for reusable payment details, or…”
   • [claimed-docs] “Set submission requirements, enforce spend limits, and block risky merchants or categories all before spend happens.”

   proof ↗⚑ flag

   Brex✓fullclaimed7/10

   Brex documents virtual card creation (docs-14, docs-38), bulk virtual-card issuance for employees/vendors (docs-30, docs-32), and procurement-specific spend limits (docs-9), which together support finance leads creating vendor-specific virtual cards to isolate compromise risk. Missing for 10: explicit documentation of a 'lock card to single vendor' control or vendor-merchant-locking mechanism, and independent/hands-on evidence confirming this containment behavior in practice.

   • [claimed-docs] “Create a virtual card instantly to pay by card and earn rewards. Send ACH, checks, and wires from any bank account or a Brex business accoun…”
   • [claimed-docs] “Eliminate data entry, automate approvals, and spin up virtual cards in one click to maximize your rewards.”
   • [claimed-docs] “we’ll show you how to bulk create virtual cards for your employees”
   • [claimed-docs] “Workato...to enable various use cases including bulk creating users, setting monthly limits for users, issuing virtual cards, and sending ve…”
   • [claimed-docs] “Create limits for stipends, travel, procurement, and more. Auto-enforced controls empower employees to spend with confidence.”
   • [claimed-docs] “Physical and virtual cards issued on the leading worldwide network, Mastercard, with acceptance in 210+ countries and territories.”

   proof ↗⚑ flag

Agent access

1. ai-native userAn agent can pull uncoded transactions via API or MCP, propose categorizations and policy flags, and push clean coding back for review

   weight 3 · round drawn
   Ramp~partialprobed6/10

   Ramp offers both API (Transactions API, OAuth) and MCP access, and MCP examples show pulling uncoded transactions (missing receipts/memos) and drafting messages, plus AI auto-coding of transactions to GL accounts. However, there's no explicit documented workflow showing an agent proposing categorizations/policy flags and pushing 'clean coding back for review' via MCP/API as a distinct human-review step. missing for 10: explicit end-to-end example of agent proposing coding+policy flags and submitting for human review via MCP/API, independent/hands-on confirmation of this workflow.

   • [claimed-docs] “You'll create an access token and call the Transactions API to retrieve transaction data.”
   • [claimed-docs] “Ramp MCP allows you to securely connect Ramp with AI assistants like ChatGPT and Claude, so you can query Ramp data and take actions with na…”
   • [claimed-docs] “Ramp gives you infinite teammates who work around the clock—flagging fraud, coding expenses, and enforcing policy.”
   • [claimed-docs] “Find transactions with missing receipts or memos in the last 14 days and draft reminder messages I can send to the team.”
   • [claimed-docs] “the receipt is captured automatically, coded to the correct GL account, and auto-approved because it's within policy — no expense report fil…”
   • [probe] “official MCP server documented at https://support.ramp.com/hc/en-us/articles/45516494479891-Ramp-MCP”

   proof ↗⚑ flag

   Brex~partialprobed6/10

   Brex offers a Transactions API to pull transaction data, an official MCP server that lets AI assistants 'manage expenses' and 'review banking transactions,' and AI features (audit/review agents) that categorize spend and flag policy violations (policy field on bookings, out-of-policy detection). However, the evidence never shows a specific 'uncoded transactions' filter/endpoint or an explicit write-back/update-category API call that pushes AI-proposed coding for human review — it only shows general expense/transaction read access and rule-based auto-approval. Missing for 10: explicit uncoded-transaction query capability, explicit category/coding update endpoint, and documented human-review workflow tying AI-proposed codes back to approval.

   • [claimed-docs] “The Brex MCP server lets AI assistants interact directly with your Brex account: manage expenses, look up users, check cards, review banking…”
   • [claimed-docs] “The transactions API lets you view your transactions, accounts, and statements.”
   • [claimed-docs] “Added `policy` to booking objects, exposing whether a booking was out of policy and which travel policy rules it violated.”
   • [claimed-docs] “Your audit agent monitors company expenses according to your internal processes and categorizes potential violations by risk level.”
   • [claimed-docs] “Your review agent auto-approves low-risk expenses and requests, escalates exceptions, and follows up with anyone out of compliance.”
   • [claimed-docs] “Stop waiting for people to categorize, review, or approve spend. Let AI agents do it instantly, based on your policies and with total transp…”
   • [probe] “official MCP server documented at https://developer.brex.com/docs/mcp”

   proof ↗⚑ flag

Api access

1. developerPull transactions, expenses, and receipts through a documented REST API with OAuth and scoped tokens

   weight 3 · round to Ramp
   Ramp✓fullprobed8/10

   Ramp documents a Transactions API accessed via access tokens, and OAuth 2.0 with scopes and multiple authorization flows for API access, plus webhooks for event notifications, confirming a documented REST API with scoped OAuth tokens for transaction/expense data. missing for 10: no explicit mention of a dedicated receipts endpoint or independent third-party corroboration of API behavior beyond vendor docs.

   • [claimed-docs] “You'll create an access token and call the Transactions API to retrieve transaction data.”
   • [claimed-docs] “Ramp uses OAuth 2.0 for secure API access, providing granular permission control through scopes and supporting multiple authorization flows …”
   • [claimed-docs] “Webhooks allow your application to receive real-time notifications about events that occur in your Ramp account.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.ramp.com/llms.txt # Ramp Developer API Machine-readable index for Ramp's Developer API documentati…”

   proof ↗⚑ flag

   Brex~partialprobed7/10

   Brex has a documented REST API covering transactions, expenses, receipts (upload/match), budgets, and webhooks, with token-based authentication using scopes (brex-docs-2, brex-docs-4, brex-docs-7, brex-docs-27, brex-docs-19). However, the auth mechanism is described as dashboard-generated 'user tokens' with scopes rather than a full OAuth flow, and an OpenAPI spec could not be located via standard endpoints (brex-probe-2). missing for 10: explicit OAuth 2.0 flow documentation (vs. static token generation), publicly discoverable OpenAPI/swagger spec, and independent developer corroboration of the API working as documented.

   • [claimed-docs] “Sign in to dashboard.brex.com as an account admin or card admin... Click Create Token. Create a name for your token... Choose what level of …”
   • [claimed-docs] “The transactions API lets you view your transactions, accounts, and statements.”
   • [claimed-docs] “The uri will be a pre-signed S3 URL allowing you to upload the receipt securely... we will try to match the receipt with existing expenses.”
   • [claimed-docs] “Upload receipt and match automatically.”
   • [claimed-docs] “Added filter query parameters to List users: `name`, `email[]`, `status[]`, `manager_id[]`, `department_id[]`, `location_id[]`, `title_id[]`…”
   • [claimed-docs] “generate a user token from your Brex dashboard and pass it along in your API call headers”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.brex.com/openapi.json, https://developer.brex.com/swagger.json, https://developer.…”

   proof ↗⚑ flag

Card api

1. developerIssue and manage cards programmatically — create a card with a limit, lock it, update controls — via the public API

   weight 2 · round to Brex
   Ramp~partialprobed3/10

   Ramp's marketing pages describe issuing virtual/physical cards with spend controls (ramp-docs-7, ramp-docs-11) and the MCP integration shows a 'lock my card' action (ramp-docs-30), suggesting the underlying platform supports card issuance/locking, but the developer docs index only explicitly names a Transactions API (ramp-docs-1) and the llms.txt probe doesn't surface a dedicated Cards API with create/lock/update-controls endpoints. Missing for 10: explicit public API reference/endpoints for card creation, locking, and limit/control updates, and any independent confirmation these are callable outside the MCP/CLI natural-language layer.

   • [claimed-docs] “Issue cards, attach controls, and watch spend in real time — physical for employee in-person spend, virtual for reusable payment details, or…”
   • [claimed-docs] “Create custom virtual cards and set permissions for everything from ad marketplace spend to remote work stipends, for individual teams or yo…”
   • [claimed-docs] “Lock my card — I can't find it.”
   • [claimed-docs] “You'll create an access token and call the Transactions API to retrieve transaction data.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.ramp.com/llms.txt # Ramp Developer API Machine-readable index for Ramp's Developer API documentati…”

   proof ↗⚑ flag

   Brex~partialclaimed4/10

   Evidence shows Brex exposes a broad API surface with a Postman workspace for 'all Brex APIs' and third-party integration recipes (Pipedream, Workato) that issue virtual cards and set spend limits/monthly limits, plus a budgets/spend-limits API. However, there is no first-party documentation of a dedicated Cards API (create/lock/update card controls) in the evidence pack — no cards_api.md or explicit lock/update-controls endpoints are cited, only inferred usage via third-party automation platforms. Missing for 10: a documented Cards API reference showing create-with-limit, lock/freeze, and update-controls endpoints, and any independent hands-on confirmation of programmatic card lifecycle management.

   • [claimed-docs] “we’ll show you how to bulk create virtual cards for your employees”
   • [claimed-docs] “Workato...to enable various use cases including bulk creating users, setting monthly limits for users, issuing virtual cards, and sending ve…”
   • [claimed-docs] “The budgets API lets you manage your Brex Budgets and Spend Limits.”
   • [claimed-docs] “Create limits for stipends, travel, procurement, and more. Auto-enforced controls empower employees to spend with confidence.”
   • [claimed-docs] “go to the Brex developer workspace which has collections for all of the Brex APIs”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to Ramp
   Ramp~partialprobed6/10

   Ramp exposes a broad public API, CLI, and MCP server covering many UI actions (transactions, cards, bill approval, travel booking, expense management) per ramp-docs-1,3,4,5,6,29,30, but no documentation explicitly claims full feature parity between API/CLI/MCP and the UI, and several UI-only workflows (e.g., detailed policy configuration, multi-entity setup, procurement OCR flows) are not shown as API-accessible. Missing for 10: an explicit parity statement or exhaustive endpoint list covering all UI functions, and independent confirmation that no UI-only gaps exist.

   • [claimed-docs] “You'll create an access token and call the Transactions API to retrieve transaction data.”
   • [claimed-docs] “Authenticate with OAuth, manage expenses, approve bills, book travel, and more from your terminal or AI agent.”
   • [claimed-docs] “Ramp MCP allows you to securely connect Ramp with AI assistants like ChatGPT and Claude, so you can query Ramp data and take actions with na…”
   • [claimed-docs] “Give an AI agent read access, action authority, and (with approval) real purchasing power on Ramp — through MCP, the Ramp CLI, or both.”
   • [claimed-docs] “Find transactions with missing receipts or memos in the last 14 days and draft reminder messages I can send to the team.”
   • [claimed-docs] “Lock my card — I can't find it.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.ramp.com/llms.txt # Ramp Developer API Machine-readable index for Ramp's Developer API documentati…”
   • [probe] “official MCP server documented at https://support.ramp.com/hc/en-us/articles/45516494479891-Ramp-MCP”
   • [probe] “official CLI documented at https://github.com/ramp-public/ramp-cli”

   proof ↗⚑ flag

   Brex~partialprobed5/10

   Brex exposes a broad public API (transactions, budgets, expenses, users, webhooks) and an official MCP server for AI-assistant access, covering many core UI workflows, but there is no evidence of full parity — e.g. no documented API for bill pay approval routing, travel policy management, or card issuance settings that mirror the UI feature set. missing for 10: explicit parity statement, bill-pay/travel/card-management API endpoints, independent confirmation that all UI actions are API-reachable.

   • [claimed-docs] “Sign in to dashboard.brex.com as an account admin or card admin... Click Create Token. Create a name for your token... Choose what level of …”
   • [claimed-docs] “The Brex MCP server lets AI assistants interact directly with your Brex account: manage expenses, look up users, check cards, review banking…”
   • [claimed-docs] “The transactions API lets you view your transactions, accounts, and statements.”
   • [claimed-docs] “The budgets API lets you manage your Brex Budgets and Spend Limits.”
   • [claimed-docs] “Added filter query parameters to List users: `name`, `email[]`, `status[]`, `manager_id[]`, `department_id[]`, `location_id[]`, `title_id[]`…”
   • [claimed-docs] “Tailor multi-level approval flows based on amount, vendor, employee role, and more — and Brex will route for you automatically to ensure the…”
   • [claimed-docs] “Create a virtual card instantly to pay by card and earn rewards. Send ACH, checks, and wires from any bank account or a Brex business accoun…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.brex.com/llms.txt # Brex Developer API > APIs to build on top of the Brex financial OS. ## T…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.brex.com/openapi.json, https://developer.brex.com/swagger.json, https://developer.…”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round to Brex
   Ramp~partialprobed3/10

   Ramp exposes a Transactions API and OAuth-based developer access that lets a user programmatically pull data, but there is no documented full-account data export/portability feature (e.g., a 'download all my data' or GDPR-style export in open formats). missing for 10: explicit full data export/takeout functionality, confirmation of open-format (CSV/JSON) bulk export, evidence of exporting all data types (bills, cards, reimbursements) not just transactions.

   • [claimed-docs] “You'll create an access token and call the Transactions API to retrieve transaction data.”
   • [claimed-docs] “Ramp uses OAuth 2.0 for secure API access, providing granular permission control through scopes and supporting multiple authorization flows …”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.ramp.com/llms.txt # Ramp Developer API Machine-readable index for Ramp's Developer API documentati…”

   proof ↗⚑ flag

   Brex~partialclaimed4/10

   Brex exposes APIs for transactions, expenses, users, budgets, etc. and a documented Zapier example for CSV export of card transactions, which lets a user pull data out in open formats; but there is no first-party documentation of a comprehensive 'export all your data' feature, bulk archive export, or account-closure data-portability process. missing for 10: a dedicated full-account data export tool, documentation of exporting all data types (not just transactions) in one open format, and any offboarding/portability guidance for leaving the platform.

   • [claimed-docs] “The transactions API lets you view your transactions, accounts, and statements.”
   • [claimed-docs] “Monthly Export of Brex Card Transactions to CSV in Google Drive”
   • [claimed-docs] “Added filter query parameters to List users: `name`, `email[]`, `status[]`, `manager_id[]`, `department_id[]`, `location_id[]`, `title_id[]`…”
   • [claimed-docs] “go to the Brex developer workspace which has collections for all of the Brex APIs”

   proof ↗⚑ flag

Approvals

1. finance leadBuild multi-step approval chains — manager, budget owner, finance — with delegation and escalation when approvers sit on requests

   weight 2 · round to Brex
   Ramp~partialclaimed4/10

   Ramp's docs show rule-based approval routing to stakeholders based on vendor/category/amount and role-based notification workflows, plus policy-grounded recommended approve/reject actions, which supports building structured approval chains. However, there is no evidence of explicit multi-step manager→budget-owner→finance sequencing, delegation of approval authority, or escalation logic when an approver doesn't act. missing for 10: explicit delegation feature, escalation/timeout rules, and multi-tier approval chain configuration details.

   • [claimed-docs] “Rules-based workflows route requests to the right stakeholders automatically based on vendor type, spend category, or dollar amount”
   • [claimed-docs] “Create personalized workflows that only notify the right people, based on spend amount or team role, and keep visibility high.”
   • [claimed-docs] “All spend requests come with a recommended action grounded in your policies, budgets, and funds, so you can approve or reject in seconds.”

   proof ↗⚑ flag

   Brex~partialclaimed5/10

   Brex documents multi-level, rule-based approval routing (by amount, vendor, employee role) and an AI review agent that auto-approves low-risk items and escalates exceptions, which covers the core approval-chain and escalation concept. However there is no explicit documentation of delegation (e.g., proxy approver when someone is OOO) or a named manager→budget-owner→finance sequential chain structure. Missing for 10: explicit delegation/out-of-office reassignment mechanism, documented sequential role hierarchy (manager, budget owner, finance) rather than generic 'role-based routing', and independent/hands-on confirmation of escalation behavior.

   • [claimed-docs] “Set rules for how employees can spend, what they need to document, and who needs to approve. Brex AI applies them to every transaction.”
   • [claimed-docs] “Tailor multi-level approval flows based on amount, vendor, employee role, and more — and Brex will route for you automatically to ensure the…”
   • [claimed-docs] “Your review agent auto-approves low-risk expenses and requests, escalates exceptions, and follows up with anyone out of compliance.”
   • [claimed-docs] “Stop waiting for people to categorize, review, or approve spend. Let AI agents do it instantly, based on your policies and with total transp…”
   • [claimed-docs] “Assign top-line budgets, and track spend instantly, ensuring every dollar is allocated where it has the biggest impact.”

   proof ↗⚑ flag

Audit trail

1. finance leadEvery expense carries a full audit trail — edits, approvals, policy checks — that survives an external audit

   weight 2 · round to Brex
   Ramp~partialclaimed4/10

   Ramp's docs show policy enforcement (submission requirements, spend limits, policy status checks) and approval workflows with recommended actions, plus reconciliation/3-way matching tools that touch on audit-adjacent controls (ramp-docs-9, ramp-docs-10, ramp-docs-17, ramp-docs-26). However, there is no explicit documentation of an immutable audit log, edit history tracking, or export/report designed specifically to survive an external audit review. Missing for 10: explicit audit-trail/edit-history logging feature, statement on audit log immutability or retention, and third-party/independent evidence of audit compliance (e.g., SOC2 audit trail usage).

   • [claimed-docs] “Set submission requirements, enforce spend limits, and block risky merchants or categories all before spend happens.”
   • [claimed-docs] “All spend requests come with a recommended action grounded in your policies, budgets, and funds, so you can approve or reject in seconds.”
   • [claimed-docs] “Ramp checks every line item with two and three-way matching, so you know if something's off before sending.”
   • [claimed-docs] “Gain confidence in your numbers with Ramp's built-in reconciliation tool that verifies balances between both platforms”
   • [claimed-docs] “Create personalized workflows that only notify the right people, based on spend amount or team role, and keep visibility high.”

   proof ↗⚑ flag

   Brex~partialclaimed6/10

   Brex documents policy-violation flags on bookings, multi-level approval routing, budget/spend limits, and a dedicated 'audit agent' that monitors and categorizes policy violations — all elements that would feed an audit trail. However, there is no explicit documentation of an immutable, exportable audit log capturing edit history, approval timestamps, and policy-check results in a form built for external audit review. missing for 10: explicit immutable/exportable audit-log documentation, evidence of edit-history tracking per expense, independent confirmation the trail survives external audit scrutiny.

   • [claimed-docs] “Added `policy` to booking objects, exposing whether a booking was out of policy and which travel policy rules it violated.”
   • [claimed-docs] “Set rules for how employees can spend, what they need to document, and who needs to approve. Brex AI applies them to every transaction.”
   • [claimed-docs] “Tailor multi-level approval flows based on amount, vendor, employee role, and more — and Brex will route for you automatically to ensure the…”
   • [claimed-docs] “Your audit agent monitors company expenses according to your internal processes and categorizes potential violations by risk level.”
   • [claimed-docs] “Your review agent auto-approves low-risk expenses and requests, escalates exceptions, and follows up with anyone out of compliance.”
   • [claimed-docs] “Automatically block out-of-policy purchases, with preset rules and limits.”

   proof ↗⚑ flag

Policy engine

1. finance leadCodify our expense policy — limits by category, role, and context — so in-policy expenses auto-approve and only exceptions reach a human

   weight 3 · round drawn
   Ramp✓fullclaimed8/10

   Ramp docs describe configurable spend limits by category/role/context, submission requirements, and blocking risky merchants/categories before spend happens (ramp-docs-9), plus in-policy auto-approval with GL coding and no expense report needed (ramp-docs-32), and recommended approve/reject actions grounded in policy for exceptions (ramp-docs-10). Custom card permissions and role/team-based notification routing further support codifying policy by role and context (ramp-docs-11, ramp-docs-12). Missing for 10: independent/hands-on verification of policy engine granularity and confirmation that auto-approval works reliably at scale beyond marketing copy.

   • [claimed-docs] “Set submission requirements, enforce spend limits, and block risky merchants or categories all before spend happens.”
   • [claimed-docs] “All spend requests come with a recommended action grounded in your policies, budgets, and funds, so you can approve or reject in seconds.”
   • [claimed-docs] “Create custom virtual cards and set permissions for everything from ad marketplace spend to remote work stipends, for individual teams or yo…”
   • [claimed-docs] “Create personalized workflows that only notify the right people, based on spend amount or team role, and keep visibility high.”
   • [claimed-docs] “the receipt is captured automatically, coded to the correct GL account, and auto-approved because it's within policy — no expense report fil…”

   proof ↗⚑ flag

   Brex✓fullclaimed8/10

   Brex documents policy codification by category, role, vendor, and context (limits, spend rules, multi-level approval routing by amount/vendor/role) and explicit auto-approval of in-policy items with exceptions escalated to humans via its review/audit AI agents. Budgets API and policy-violation flags further support programmatic enforcement. Missing for 10: independent/hands-on verification of auto-approval accuracy and no detailed docs on granular category-level rule configuration UI.

   • [claimed-docs] “Set rules for how employees can spend, what they need to document, and who needs to approve. Brex AI applies them to every transaction.”
   • [claimed-docs] “Create limits for stipends, travel, procurement, and more. Auto-enforced controls empower employees to spend with confidence.”
   • [claimed-docs] “Tailor multi-level approval flows based on amount, vendor, employee role, and more — and Brex will route for you automatically to ensure the…”
   • [claimed-docs] “Your review agent auto-approves low-risk expenses and requests, escalates exceptions, and follows up with anyone out of compliance.”
   • [claimed-docs] “Automatically block out-of-policy purchases, with preset rules and limits.”
   • [claimed-docs] “Stop waiting for people to categorize, review, or approve spend. Let AI agents do it instantly, based on your policies and with total transp…”
   • [claimed-docs] “The budgets API lets you manage your Brex Budgets and Spend Limits.”
   • [claimed-docs] “Added `policy` to booking objects, exposing whether a booking was out of policy and which travel policy rules it violated.”

   proof ↗⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round drawn
   Ramp—none0/10

   No evidence in the pack addresses data residency, regional storage options, or geographic control over where data is stored; evidence only covers API, MCP, CLI, and expense-management features.

   ⚑ flag

   Brex—none0/10

   No evidence pack items mention data residency, regional storage options, or any control over where data is stored; Brex evidence covers financial product features, APIs, and MCP integration only.

   ⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round drawn
   Ramp—none0/10

   No evidence pack item addresses AI training data usage, opt-out controls, or data-privacy policies regarding model training; all evidence concerns product features (cards, expense management, MCP/CLI integrations) rather than data governance for AI training. Missing for 10: any privacy policy statement, opt-out mechanism, or documentation about AI training data usage.

   ⚑ flag

   Brex—none0/10

   No evidence pack item addresses AI training data usage, opt-out settings, or a data-privacy policy regarding model training; the evidence only covers API/product features and unrelated community complaints about account closures.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Ramp—none0/10

   No evidence pack items address data retention policies, deletion controls, or user-configurable data lifecycle settings for AI/agent-related data; the pack focuses on API/MCP/CLI functionality and expense automation, not privacy/retention controls.

   ⚑ flag

   Brex—none0/10

   No evidence pack item discusses data retention, deletion policies, or AI data usage/training controls specific to AI-native workflows; the API, MCP, and product docs focus on functionality (expenses, cards, bill pay) rather than privacy/data lifecycle controls. Missing for 10: any documentation on data retention periods, deletion requests, opt-out of AI training, or data residency/handling policies.

   ⚑ flag

4. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   Ramp—none0/10

   No evidence in the pack addresses telemetry opt-out or usage-tracking controls for AI-native users; Ramp's documentation covers APIs, MCP, CLI, and expense features but nothing about telemetry settings.

   ⚑ flag

   Brex—none0/10

   No evidence in the pack mentions telemetry, usage tracking, or an opt-out/privacy control mechanism for AI-native users; the docs focus on APIs, webhooks, MCP server, and financial products with no privacy-posture disclosures.

   ⚑ flag

Mileage perdiem

1. employeeLog mileage with map-based distance and claim per-diem rates without building the expense by hand

   weight 2 · round to Ramp
   Ramp✓fullclaimed7/10

   Ramp's own docs confirm automatic mileage calculation via Google Maps integration for reimbursements and automatic per-diem rate adjustment based on trip location/duration, directly matching the story's request for map-based mileage and per-diem claims without manual entry. Missing for 10: independent/hands-on verification of the mileage logging UX and per-diem claim flow, and no detail on how these integrate into a single expense submission step.

   • [claimed-docs] “Our integration with Google Maps keeps repayments precise with automatic mileage calculations.”
   • [claimed-docs] “Per diem shows exactly what you can purchase, and automatically adjusts based on trip location and duration.”
   • [claimed-docs] “Reimburse employees with confidence in more than 70 countries and 40 currencies, knowing they can be paid in two days or less in their local…”

   proof ↗⚑ flag

   Brex—none0/10

   No evidence in the pack mentions mileage tracking, GPS/map-based distance calculation, or per-diem rate claims; Brex's expense documentation focuses on card transactions, receipt upload/matching, and policy enforcement but never describes mileage or per-diem automation. This is a fair capability to expect from an expense management product, so absence of evidence means none rather than na.

   • [claimed-docs] “The uri will be a pre-signed S3 URL allowing you to upload the receipt securely... we will try to match the receipt with existing expenses.”
   • [claimed-docs] “Set rules for how employees can spend, what they need to document, and who needs to approve. Brex AI applies them to every transaction.”
   • [claimed-docs] “Upload receipt and match automatically.”
   • [claimed-docs] “Manage global spend and close the books in real time — with unmatched automation of manual expense work.”

   proof ↗⚑ flag

Receipt capture

1. employeeSnap a photo or forward an email and the platform OCRs the receipt and files it against the right transaction

   weight 3 · round to Brex
   Ramp~partialclaimed5/10

   Evidence confirms Ramp automatically captures receipts and applies OCR/coding when a card is swiped, with edits/submission via SMS, Slack, or Teams (ramp-docs-8, ramp-docs-32), and general OCR accuracy claims exist for bill-pay (ramp-docs-16). However, none of the evidence specifically describes an employee snapping a photo of a paper receipt or forwarding an email receipt that gets OCR'd and matched to a transaction — the described flow is card-swipe-triggered capture, not employee-initiated photo/email submission. Missing for 10: explicit documentation of photo-upload or email-forwarding receipt intake and its OCR matching to transactions, plus independent/hands-on confirmation.

   • [claimed-docs] “As soon as you swipe your card, Ramp captures the receipt and fills in memos and categories. Make edits and submit via SMS, Slack, or Micros…”
   • [claimed-docs] “the receipt is captured automatically, coded to the correct GL account, and auto-approved because it's within policy — no expense report fil…”
   • [claimed-docs] “Ramp's OCR captures each detail and line item with 99% accuracy.”

   proof ↗⚑ flag

   Brex~partialclaimed6/10

   Brex supports receipt upload with automatic matching to expenses via API ("Upload receipt and match automatically", pre-signed S3 URL matching to existing expenses) and AI agents that 'fetch receipts' automatically, but there's no explicit evidence of OCR technology, photo-snap mobile capture flow, or email-forwarding-to-receipt-filing as described in the story. missing for 10: explicit OCR mention, mobile photo-capture UX details, email-forwarding ingestion mechanism, independent/hands-on confirmation of accuracy.

   • [claimed-docs] “The uri will be a pre-signed S3 URL allowing you to upload the receipt securely... we will try to match the receipt with existing expenses.”
   • [claimed-docs] “Upload receipt and match automatically.”
   • [claimed-docs] “AI assistants do employees' expenses for them, writing memos, fetching receipts, offering policy help, even filing reimbursements automatica…”

   proof ↗⚑ flag

Receipt matching

1. employeeReceipts match to card transactions automatically — with e-receipts pulled from integrations — and I get nudged only when one is genuinely missing

   weight 2 · round drawn
   Ramp~partialclaimed6/10

   Ramp documents automatic receipt capture and coding at swipe time, auto-approval when in policy, and reminders/nudges only for transactions with missing receipts or memos (ramp-docs-8, ramp-docs-13, ramp-docs-29, ramp-docs-32). However, there's no explicit evidence of e-receipts being pulled in from email/vendor integrations (e.g., Amazon, Lyft, Uber) as the story specifies. Missing for 10: documentation of e-receipt integrations sourcing receipts automatically, and independent/hands-on confirmation that nudges only trigger for genuinely missing receipts.

   • [claimed-docs] “As soon as you swipe your card, Ramp captures the receipt and fills in memos and categories. Make edits and submit via SMS, Slack, or Micros…”
   • [claimed-docs] “Let Ramp send reminders for missing items or request repayments for you.”
   • [claimed-docs] “Find transactions with missing receipts or memos in the last 14 days and draft reminder messages I can send to the team.”
   • [claimed-docs] “the receipt is captured automatically, coded to the correct GL account, and auto-approved because it's within policy — no expense report fil…”

   proof ↗⚑ flag

   Brex~partialclaimed6/10

   Brex's API/docs confirm automatic receipt-to-transaction matching ("Upload receipt and match automatically" and pre-signed S3 upload that tries to match existing expenses), and its AI feature page claims agents can 'fetch receipts' and file expenses automatically, plus a review agent that 'follows up with anyone out of compliance.' However, there's no explicit evidence of e-receipts being pulled automatically from third-party integrations (e.g., travel/vendor e-receipt feeds) nor documentation describing smart nudging logic that only triggers when a receipt is genuinely missing rather than generic compliance follow-ups. missing for 10: explicit e-receipt integration sourcing, documented logic for suppressing false-positive missing-receipt nudges, independent user confirmation of matching accuracy.

   • [claimed-docs] “Upload receipt and match automatically.”
   • [claimed-docs] “The uri will be a pre-signed S3 URL allowing you to upload the receipt securely... we will try to match the receipt with existing expenses.”
   • [claimed-docs] “AI assistants do employees' expenses for them, writing memos, fetching receipts, offering policy help, even filing reimbursements automatica…”
   • [claimed-docs] “Your review agent auto-approves low-risk expenses and requests, escalates exceptions, and follows up with anyone out of compliance.”

   proof ↗⚑ flag

Domestic

1. employeeSubmit an out-of-pocket expense and get reimbursed by direct deposit in days, tracked from submission to payout

   weight 3 · round to Ramp
   Ramp✓fullclaimed7/10

   Ramp explicitly supports out-of-pocket reimbursements paid within two days or less in local currency across 70+ countries (ramp-docs-14), with automated receipt capture, submission via SMS/Slack/Teams, and policy-based auto-approval reducing manual expense reports (ramp-docs-8, ramp-docs-32). Approval workflows and reminders support the submission-to-payout tracking narrative (ramp-docs-10, ramp-docs-13). Missing for 10: explicit end-to-end status tracking UI/dashboard evidence for an individual employee, and independent/hands-on confirmation of the 2-day payout claim.

   • [claimed-docs] “Reimburse employees with confidence in more than 70 countries and 40 currencies, knowing they can be paid in two days or less in their local…”
   • [claimed-docs] “As soon as you swipe your card, Ramp captures the receipt and fills in memos and categories. Make edits and submit via SMS, Slack, or Micros…”
   • [claimed-docs] “the receipt is captured automatically, coded to the correct GL account, and auto-approved because it's within policy — no expense report fil…”
   • [claimed-docs] “All spend requests come with a recommended action grounded in your policies, budgets, and funds, so you can approve or reject in seconds.”
   • [claimed-docs] “Let Ramp send reminders for missing items or request repayments for you.”

   proof ↗⚑ flag

   Brex~partialclaimed5/10

   Brex's docs confirm out-of-pocket expense submission (receipt upload/matching in brex-docs-7/27) and AI-driven automatic reimbursement filing (brex-docs-23), implying an end-to-end expense workflow, but there is no explicit documentation of direct-deposit payout mechanics, reimbursement timing ('days'), or a submission-to-payout tracking status view. missing for 10: explicit direct-deposit reimbursement flow, payout SLA/timing details, and a visible tracking/status dashboard for reimbursement progress.

   • [claimed-docs] “The uri will be a pre-signed S3 URL allowing you to upload the receipt securely... we will try to match the receipt with existing expenses.”
   • [claimed-docs] “AI assistants do employees' expenses for them, writing memos, fetching receipts, offering policy help, even filing reimbursements automatica…”
   • [claimed-docs] “Upload receipt and match automatically.”
   • [claimed-docs] “Set rules for how employees can spend, what they need to document, and who needs to approve. Brex AI applies them to every transaction.”

   proof ↗⚑ flag

International

1. finance leadReimburse employees abroad in their local currency without running a separate international payments process

   weight 2 · round to Ramp
   Ramp✓fullclaimed8/10

   Ramp explicitly advertises reimbursing employees in 70+ countries and 40 currencies with local-currency payout in two days or less, directly matching the story, and this is embedded in its core reimbursement product rather than a separate process. Missing for 10: independent/hands-on verification of actual cross-border payout speed/accuracy and details on FX handling or fees.

   • [claimed-docs] “Reimburse employees with confidence in more than 70 countries and 40 currencies, knowing they can be paid in two days or less in their local…”

   proof ↗⚑ flag

   Brex—none0/10

   Evidence covers global card acceptance (210+ countries), bill pay wires 'in more currencies' for vendor payments, and general 'global spend' messaging, but nothing specifically addresses reimbursing employees abroad in their local currency or eliminating a separate international payments process for reimbursements.

   ⚑ flag

Budgets

1. finance leadAllocate budgets to teams and projects and have card limits and approvals actually enforce them

   weight 2 · round drawn
   Ramp✓fullclaimed8/10

   Ramp's documentation directly supports budget allocation to teams/projects with card controls that enforce them: custom virtual cards with per-team/vendor spend permissions (ramp-docs-11, ramp-docs-31), pre-spend enforcement of limits and blocked merchants/categories (ramp-docs-9), policy-grounded recommended approve/reject actions (ramp-docs-10), and role/amount-based notification workflows (ramp-docs-12). This covers allocation, limit enforcement, and approvals working together. Missing for 10: no independent/hands-on verification of enforcement accuracy, and no explicit 'budget' object/API distinct from card limits shown in evidence.

   • [claimed-docs] “Set submission requirements, enforce spend limits, and block risky merchants or categories all before spend happens.”
   • [claimed-docs] “All spend requests come with a recommended action grounded in your policies, budgets, and funds, so you can approve or reject in seconds.”
   • [claimed-docs] “Create custom virtual cards and set permissions for everything from ad marketplace spend to remote work stipends, for individual teams or yo…”
   • [claimed-docs] “Create personalized workflows that only notify the right people, based on spend amount or team role, and keep visibility high.”
   • [claimed-docs] “A finance team issues instant virtual cards for each software subscription with per-vendor spending limits, giving real-time visibility into…”
   • [claimed-docs] “Issue cards, attach controls, and watch spend in real time — physical for employee in-person spend, virtual for reusable payment details, or…”

   proof ↗⚑ flag

   Brex✓fullclaimed8/10

   Brex documents budgets/spend limits API and dashboard features for assigning top-line budgets, auto-enforced spend limits, policy-based blocking of out-of-policy purchases, and multi-level approval routing, directly matching the finance-lead's need to allocate budgets and have limits/approvals enforce them. missing for 10: independent/hands-on evidence confirming enforcement works reliably in practice (community evidence only covers account closures, not budget/approval enforcement), and no case study showing team/project-level allocation granularity in real use.

   • [claimed-docs] “The budgets API lets you manage your Brex Budgets and Spend Limits.”
   • [claimed-docs] “Set rules for how employees can spend, what they need to document, and who needs to approve. Brex AI applies them to every transaction.”
   • [claimed-docs] “Create limits for stipends, travel, procurement, and more. Auto-enforced controls empower employees to spend with confidence.”
   • [claimed-docs] “Assign top-line budgets, and track spend instantly, ensuring every dollar is allocated where it has the biggest impact.”
   • [claimed-docs] “Tailor multi-level approval flows based on amount, vendor, employee role, and more — and Brex will route for you automatically to ensure the…”
   • [claimed-docs] “Automatically block out-of-policy purchases, with preset rules and limits.”

   proof ↗⚑ flag

Dashboards

1. founderSee company spend in real time — by team, category, and merchant — the day it happens, not when statements land

   weight 3 · round to Ramp
   Ramp✓fullclaimed8/10

   Ramp captures spend in real time at swipe (receipt/memo/category auto-filled), issues cards with real-time spend tracking per team/vendor, and offers Transactions API/webhooks for real-time data feeds by team, category, and merchant. This directly matches the founder's need for same-day visibility rather than waiting on statements. Missing for 10: no independent/third-party corroboration or explicit dashboard screenshot evidence of a unified real-time cross-team/category/merchant view.

   • [claimed-docs] “Issue cards, attach controls, and watch spend in real time — physical for employee in-person spend, virtual for reusable payment details, or…”
   • [claimed-docs] “As soon as you swipe your card, Ramp captures the receipt and fills in memos and categories. Make edits and submit via SMS, Slack, or Micros…”
   • [claimed-docs] “Create custom virtual cards and set permissions for everything from ad marketplace spend to remote work stipends, for individual teams or yo…”
   • [claimed-docs] “A finance team issues instant virtual cards for each software subscription with per-vendor spending limits, giving real-time visibility into…”
   • [claimed-docs] “Webhooks allow your application to receive real-time notifications about events that occur in your Ramp account.”
   • [claimed-docs] “You'll create an access token and call the Transactions API to retrieve transaction data.”

   proof ↗⚑ flag

   Brex✓fullclaimed7/10

   Brex provides real-time spend tracking via the mobile app ("view your spend all in one app"), budgets API tracked instantly by team/cost-center, transactions API for granular transaction-level data, and webhooks for live event notifications, plus marketing claims of managing spend and closing books in real time. Category/department/merchant segmentation is supported via cost_center_id/department_id filters and the transactions API, though merchant-level breakdown isn't explicitly documented as a dashboard feature. Missing for 10: explicit merchant-level dashboard breakdown documentation, independent/hands-on verification that spend updates instantly rather than with delay, and no clear evidence of a dedicated real-time analytics dashboard beyond mobile app spend view.

   • [claimed-docs] “The transactions API lets you view your transactions, accounts, and statements.”
   • [claimed-docs] “The budgets API lets you manage your Brex Budgets and Spend Limits.”
   • [claimed-docs] “Assign top-line budgets, and track spend instantly, ensuring every dollar is allocated where it has the biggest impact.”
   • [claimed-docs] “Manage your card from your phone. Pay with Apple Pay, cancel your card, and view your spend all in one app.”
   • [claimed-docs] “Manage global spend and close the books in real time — with unmatched automation of manual expense work.”
   • [claimed-docs] “Added filter query parameters to List users: `name`, `email[]`, `status[]`, `manager_id[]`, `department_id[]`, `location_id[]`, `title_id[]`…”
   • [claimed-docs] “Register an endpoint to start receiving selected webhook events”

   proof ↗⚑ flag

Booking

1. employeeBook flights and hotels in-platform with travel policy applied at booking time, not expensed and argued about later

   weight 2 · round to Brex
   Ramp✓fullclaimed7/10

   Ramp Travel explicitly shows policy status at time of booking ('See policy status for every option... wondering if trips will get rejected'), applies per diem automatically, and even auto-rebooks hotels when rates drop, indicating in-platform booking with policy enforced upfront rather than post-hoc expense review. This directly matches the story of not having to expense-and-argue later. Missing for 10: independent/hands-on verification of the booking flow UX, and detail on flight booking specifically (most evidence focuses on hotel/per diem) plus confirmation of real-time policy blocking vs. just visibility.

   • [claimed-docs] “See policy status for every option. No digging through static policy PDFs or wondering if trips will get rejected.”
   • [claimed-docs] “Per diem shows exactly what you can purchase, and automatically adjusts based on trip location and duration.”
   • [claimed-docs] “Ramp monitors hotel rates and automatically rebooks if the price decreases by $50+.”

   proof ↗⚑ flag

   Brex✓fullcommunity8/10

   Brex Travel is a first-party product explicitly combining booking with 'global inventory and auto-enforced expense policies on one platform' (brex-docs-39), and the API changelog shows booking objects carry a `policy` field flagging out-of-policy violations at booking time (brex-docs-6), confirming policy is applied during booking rather than after. Community evidence corroborates actual usage of Brex Travel for booking ('Brex Travel was luxurious') (brex-comm-1). Missing for 10: independent review of the booking flow's policy enforcement UX and more detail on flight/hotel inventory breadth.

   • [claimed-docs] “Simplify travel with global inventory and auto-enforced expense policies on one platform.”
   • [claimed-docs] “Added `policy` to booking objects, exposing whether a booking was out of policy and which travel policy rules it violated.”
   • [community] “I really liked the dynamic credit card generator, and Brex Travel was luxurious...”

   proof ↗⚑ flag

Trip expenses

1. employeeA trip's expenses — bookings, cards, receipts — collect themselves into one itinerary-linked report

   weight 1 · round drawn
   Ramp~partialclaimed5/10

   Ramp documents automatic receipt capture and card-based expense coding (ramp-docs-8, ramp-docs-32) and travel-specific policy/per-diem/hotel tools (ramp-docs-18, ramp-docs-19, ramp-docs-20), suggesting trip spend is tracked and can be booked within policy, but there is no explicit documentation that bookings, cards, and receipts are automatically consolidated into a single itinerary-linked expense report for the employee. missing for 10: explicit description of a unified trip/itinerary report view, evidence that booking data auto-links to card transactions and receipts under one trip record, and any hands-on confirmation of this consolidation.

   • [claimed-docs] “As soon as you swipe your card, Ramp captures the receipt and fills in memos and categories. Make edits and submit via SMS, Slack, or Micros…”
   • [claimed-docs] “See policy status for every option. No digging through static policy PDFs or wondering if trips will get rejected.”
   • [claimed-docs] “Per diem shows exactly what you can purchase, and automatically adjusts based on trip location and duration.”
   • [claimed-docs] “Ramp monitors hotel rates and automatically rebooks if the price decreases by $50+.”
   • [claimed-docs] “the receipt is captured automatically, coded to the correct GL account, and auto-approved because it's within policy — no expense report fil…”

   proof ↗⚑ flag

   Brex~partialclaimed5/10

   Brex Travel and expense docs show pieces of this workflow — bookings carry policy metadata (brex-docs-6), corporate cards integrate with the platform (brex-docs-20/21), and receipts auto-match to expenses (brex-docs-7/brex-docs-27) — and the Travel product page claims to "simplify travel with global inventory and auto-enforced expense policies on one platform" (brex-docs-39). However, no evidence explicitly describes a trip/itinerary object that automatically aggregates bookings, card transactions, and receipts into a single itinerary-linked expense report for the employee. Missing for 10: explicit itinerary/trip-report generation feature, documentation of automatic booking-to-card-to-receipt linkage within one report, and any hands-on/independent confirmation of this consolidated view.

   • [claimed-docs] “Simplify travel with global inventory and auto-enforced expense policies on one platform.”
   • [claimed-docs] “Added `policy` to booking objects, exposing whether a booking was out of policy and which travel policy rules it violated.”
   • [claimed-docs] “The uri will be a pre-signed S3 URL allowing you to upload the receipt securely... we will try to match the receipt with existing expenses.”
   • [claimed-docs] “Upload receipt and match automatically.”
   • [claimed-docs] “Physical and virtual cards issued on the leading worldwide network, Mastercard, with acceptance in 210+ countries and territories.”

   proof ↗⚑ flag