Brex vs Ramp

Close automation

1. ai-native userUse AI automations to close my books faster each month

   weight 2 · round to Ramp
   Brex✓fullclaimed7/10

   Brex explicitly documents AI-driven automations aimed at faster month-end close — one-click accrual booking, automated GL coding by entity, AI-powered invoice entry/approval, plus an Accounting API and MCP server for programmatic/AI-assisted access to accounting data. This directly matches the ai-native 'close books faster' story via first-party product documentation. missing for 10: independent/hands-on corroboration that these automations measurably speed up close, no case study or third-party validation of close-time reduction.

   • [claimed-docs] “Book accruals for incomplete expenses with one click to close the books every day and automate GL coding by entity globally.”
   • [claimed-docs] “Save time with AI-powered automation of invoice entry, approval, and payments.”
   • [claimed-docs] “automate GL coding by entity globally”
   • [claimed-docs] “Accounting API: View and manage accounting data”
   • [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] “8 reasons to switch to AI-powered financial operations”

   proof ↗⚑ flag

   Ramp✓fullclaimed8/10

   Ramp documents AI-driven auto-coding, auto-categorization, real-time bidirectional ERP sync eliminating manual journal entries, and dedicated AI agents for auto-coding/fraud/approvals/payments, directly targeting faster book closing; broad accounting integration list (NetSuite, QuickBooks, Sage Intacct, etc.) supports this at scale. Missing for 10: independent/hands-on verification of close-time reduction and no specific 'days to close' benchmark or customer-reported close-cycle metric.

   • [claimed-docs] “Real-time bidirectional sync with ERPs eliminates manual journal entries”
   • [claimed-docs] “Ramp automatically categorizes transactions based on transaction details, historical information, and your team's direct feedback, then sync…”
   • [claimed-docs] “Four AI agents handle auto-coding, fraud prevention, approval routing, and automatic payment”
   • [claimed-docs] “A vendor invoice is dragged into Ramp, automatically matched to its PO, coded to the right GL account, routed for approval, and paid — 7x fe…”
   • [claimed-docs] “Accounting: NetSuite, Sage Intacct, QuickBooks Online, QuickBooks Desktop, Xero, Workday Financial Management, Acumatica, Microsoft Dynamics…”

   proof ↗⚑ flag

2. ai-native userHave AI automatically assign GL codes to transactions across entities to accelerate close

   weight 3 · round to Ramp
   Brex✓fullclaimed7/10

   Brex's own marketing explicitly claims automated GL coding by entity globally with one-click accrual booking to close books daily, directly matching the story (brex-docs-8, brex-docs-14), backed by an Accounting API for managing accounting data across entities (brex-docs-1) and AI-powered automation messaging (brex-docs-7, brex-docs-9). Missing for 10: independent/hands-on verification of GL-coding accuracy across entities and no third-party case study confirming close-acceleration outcomes.

   • [claimed-docs] “automate GL coding by entity globally”
   • [claimed-docs] “Book accruals for incomplete expenses with one click to close the books every day and automate GL coding by entity globally.”
   • [claimed-docs] “Accounting API: View and manage accounting data”
   • [claimed-docs] “Save time with AI-powered automation of invoice entry, approval, and payments.”
   • [claimed-docs] “8 reasons to switch to AI-powered financial operations”

   proof ↗⚑ flag

   Ramp✓fullclaimed8/10

   Ramp documents AI-driven auto-coding of transactions (auto-categorization based on transaction details/history/feedback, syncing to ERP) alongside a dedicated 'auto-coding' AI agent, multi-entity support with consolidated reporting, and real-time bidirectional ERP sync that eliminates manual journal entries — directly supporting cross-entity GL coding to accelerate close. Missing for 10: independent/hands-on evidence specifically validating GL-coding accuracy across multiple entities during a close cycle, and no third-party accounting-team testimonial on close-time reduction.

   • [claimed-docs] “Ramp automatically categorizes transactions based on transaction details, historical information, and your team's direct feedback, then sync…”
   • [claimed-docs] “Four AI agents handle auto-coding, fraud prevention, approval routing, and automatic payment”
   • [claimed-docs] “Multi-entity support with entity-level restrictions and consolidated reporting”
   • [claimed-docs] “Real-time bidirectional sync with ERPs eliminates manual journal entries”
   • [claimed-docs] “A vendor invoice is dragged into Ramp, automatically matched to its PO, coded to the right GL account, routed for approval, and paid — 7x fe…”

   proof ↗⚑ flag

Developer accounting access

1. developerView and manage accounting data through a dedicated API

   weight 1 · round drawn
   Brex✓fullprobed8/10

   Brex documents a dedicated Accounting API ('View and manage accounting data') alongside related APIs (Expenses, Transactions, Payments), and the developer docs are confirmed live via probe. Missing for 10: independent/hands-on corroboration of the Accounting API's functionality and a discoverable OpenAPI schema (404s on standard paths).

   • [claimed-docs] “Accounting API: View and manage accounting data”
   • [claimed-docs] “Expenses API: View and manage card expenses data, receipt match and receipt uploads”
   • [claimed-docs] “Transactions API: View your transactions, accounts, and statements”
   • [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

   Ramp✓fullprobed8/10

   Ramp documents a dedicated Developer API with OpenAPI spec, machine-readable docs (llms.txt, llms-api.txt), and bidirectional ERP sync for accounting data (transactions, coding, GL sync), confirmed by a live probe showing the API docs endpoint is reachable. Missing for 10: no independent developer testimonial or hands-on confirmation of actual accounting-data CRUD via the API, and no detail on specific accounting endpoints/scopes.

   • [claimed-docs] “fetch: /llms.txt (LLM index), /llms-guides.txt (guides index), /llms-guides/<slug>.txt (specific guide), /llms-api.txt (API reference), /llm…”
   • [claimed-docs] “Real-time bidirectional sync with ERPs eliminates manual journal entries”
   • [claimed-docs] “Ramp also supports custom CSV exports and an open API for flexible connectivity.”
   • [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] “Ramp automatically categorizes transactions based on transaction details, historical information, and your team's direct feedback, then sync…”

   proof ↗⚑ flag

Erp sync

1. finance-leadSync transactions and expenses automatically with my accounting software

   weight 3 · round to Ramp
   Brex✓fullclaimed8/10

   Brex documents automated GL coding, accounting API, thousands of native integrations for syncing across finance tools, and one-click accrual booking to close books daily, directly supporting automated transaction/expense sync with accounting software. Missing for 10: named integrations with specific accounting platforms (e.g. QuickBooks/NetSuite) and independent hands-on verification of sync reliability.

   • [claimed-docs] “Accounting API: View and manage accounting data”
   • [claimed-docs] “automate GL coding by entity globally”
   • [claimed-docs] “Book accruals for incomplete expenses with one click to close the books every day and automate GL coding by entity globally.”
   • [claimed-docs] “All your tools synced in one place.”
   • [claimed-docs] “Simplify every task that finance touches with automatic syncing across 1,000s of native integrations.”
   • [claimed-docs] “Make your financial operations more seamless, from card swipe to month-end close.”

   proof ↗⚑ flag

   Ramp✓fullcommunity9/10

   Ramp documents real-time bidirectional ERP sync, automatic categorization/coding synced directly to accounting systems, and a broad list of accounting integrations (NetSuite, QuickBooks, Xero, Sage Intacct, etc.), plus community corroboration of the platform working well for expense tracking. missing for 10: independent hands-on verification specifically of accounting-sync accuracy/reconciliation rather than vendor claims.

   • [claimed-docs] “Real-time bidirectional sync with ERPs eliminates manual journal entries”
   • [claimed-docs] “Ramp automatically categorizes transactions based on transaction details, historical information, and your team's direct feedback, then sync…”
   • [claimed-docs] “Accounting: NetSuite, Sage Intacct, QuickBooks Online, QuickBooks Desktop, Xero, Workday Financial Management, Acumatica, Microsoft Dynamics…”
   • [claimed-docs] “Ramp also supports custom CSV exports and an open API for flexible connectivity.”
   • [community] “It's what we use for tracking expenses and getting comped for travel, meals, software licenses etc - works great in my experience. I can cli…”

   proof ↗⚑ flag

2. finance-leadRely on real-time bidirectional sync with my ERP instead of manual journal entries

   weight 3 · round to Ramp
   Brex~partialclaimed6/10

   Brex documents an Accounting API for viewing/managing accounting data, a Webhooks API for real-time event notifications, automated GL coding by entity, and 'automatic syncing across 1,000s of native integrations' spanning card swipe to month-end close — together implying near-real-time sync that reduces manual journal entry work. However, there is no explicit mention of named ERP systems (e.g., NetSuite, Sage Intacct) or confirmation that sync is truly bidirectional (push AND pull) rather than one-way export/webhook notification, and no independent/hands-on validation of ERP sync reliability. Missing for 10: named major ERP integration specifics, explicit bidirectional sync confirmation, and third-party corroboration of real-time accuracy.

   • [claimed-docs] “Accounting API: View and manage accounting data”
   • [claimed-docs] “Webhooks API: Send real-time notifications based on events”
   • [claimed-docs] “Book accruals for incomplete expenses with one click to close the books every day and automate GL coding by entity globally.”
   • [claimed-docs] “Simplify every task that finance touches with automatic syncing across 1,000s of native integrations.”
   • [claimed-docs] “Make your financial operations more seamless, from card swipe to month-end close.”
   • [claimed-docs] “Brex uses webhooks to send real-time notifications when events happen in the accounts that you manage.”

   proof ↗⚑ flag

   Ramp✓fullclaimed8/10

   Ramp explicitly claims real-time bidirectional sync with ERPs eliminating manual journal entries, backed by auto-categorization and sync to ERP details, plus a broad list of supported ERP integrations (NetSuite, Sage Intacct, QuickBooks, etc.). Missing for 10: independent/hands-on verification of true bidirectional (not just push) sync and any community confirmation of eliminating manual JE work.

   • [claimed-docs] “Real-time bidirectional sync with ERPs eliminates manual journal entries”
   • [claimed-docs] “Ramp automatically categorizes transactions based on transaction details, historical information, and your team's direct feedback, then sync…”
   • [claimed-docs] “Accounting: NetSuite, Sage Intacct, QuickBooks Online, QuickBooks Desktop, Xero, Workday Financial Management, Acumatica, Microsoft Dynamics…”

   proof ↗⚑ flag

Account structure

1. finance-leadView account and routing numbers and generate a bank verification letter anytime

   weight 1 · round drawn
   Brex—none0/10

   Evidence pack shows Transactions/Accounting APIs for viewing accounts and statements, but nothing about viewing account/routing numbers or generating a bank verification letter is documented anywhere in the docs or community evidence.

   • [claimed-docs] “Transactions API: View your transactions, accounts, and statements”
   • [claimed-docs] “Accounting API: View and manage accounting data”

   proof ↗⚑ flag

   Ramp—none0/10

   No evidence in the pack mentions account/routing numbers, bank verification letters, or any similar account-detail retrieval feature for Ramp accounts.

   ⚑ flag

2. finance-leadOpen multiple checking sub-accounts and auto-allocate incoming deposits across them

   weight 2 · round drawn
   Brex—none0/10

   No evidence in the pack of Brex offering multiple checking sub-accounts or auto-allocation of incoming deposits across them; docs cover budgets, expenses, payments, and integrations but nothing about sub-account structuring or deposit-splitting rules.

   ⚑ flag

   Ramp—none0/10

   Evidence shows only auto top-up from a single linked checking account to Ramp's card account with target-balance automation (ramp-docs-6), not the creation of multiple checking sub-accounts or auto-allocation of incoming deposits across them. Missing for 10: any mention of multiple sub-accounts, deposit-splitting/allocation rules, or treasury account structuring.

   • [claimed-docs] “Auto top-up from linked checking accounts with target balance automation and low balance alerts”

   proof ↗⚑ flag

Bill pay

1. ai-native userHave AI read incoming bills and auto-populate payment details for my review

   weight 3 · round to Ramp
   Brex~partialcommunity6/10

   Brex explicitly markets 'AI-powered automation of invoice entry, approval, and payments' and bill pay as part of its unified spend platform, and the MCP server lets AI assistants 'track bills' via natural language, suggesting AI can ingest and populate bill data for review. However, there's no detailed documentation of the specific workflow (OCR/reading incoming bills, field extraction, human-in-loop review step), and general community skepticism about AI reliability in financial workflows (hallucinated/missed expenses) raises caution about accuracy, though not a concrete dispute of the bill-pay feature itself. Missing for 10: explicit documentation of bill-reading/OCR extraction pipeline, a described human-review UI step, and independent verification of accuracy for auto-populated payment details.

   • [claimed-docs] “Save time with AI-powered automation of invoice entry, approval, and payments.”
   • [claimed-docs] “Brex is the first fully unified spend platform — with global corporate cards, expense management, reimbursements, travel, and bill pay.”
   • [claimed-docs] “The Brex MCP server lets AI assistants interact directly with your Brex account: manage expenses, look up users, check cards, review banking…”
   • [community] “This reflects astonishingly poorly on Brex. What customer wants to hear that Brex is using 'a non-deterministic model' for production use ca…”

   proof ↗⚑ flag

   Ramp✓fullclaimed8/10

   Ramp Bill Pay explicitly describes AI reading/matching vendor invoices, auto-coding to GL, PO matching, and routing for approval before payment, directly matching the AP auto-population-for-review story, backed by the four dedicated AI agents (auto-coding, fraud, routing, payment) and ERP sync docs. Missing for 10: independent hands-on verification of invoice-reading accuracy and no third-party review specifically confirming bill-reading AI performance.

   • [claimed-docs] “A vendor invoice is dragged into Ramp, automatically matched to its PO, coded to the right GL account, routed for approval, and paid — 7x fe…”
   • [claimed-docs] “Ramp automatically categorizes transactions based on transaction details, historical information, and your team's direct feedback, then sync…”
   • [claimed-docs] “Four AI agents handle auto-coding, fraud prevention, approval routing, and automatic payment”
   • [claimed-docs] “Real-time bidirectional sync with ERPs eliminates manual journal entries”

   proof ↗⚑ flag

2. finance-leadUpload bills and route them through an approval workflow before paying vendors

   weight 3 · round to Ramp
   Brex~partialcommunity6/10

   Brex explicitly advertises AI-powered invoice entry, approval, and payment automation (bill pay) plus vendor payments via Payments API and procurement approval flows on cards, supporting the core of the story. However, evidence lacks detail on an explicit bill-upload UI/OCR workflow or configurable multi-step approval chains before vendor payment, and community threads raise concerns about AI reliability in financial workflows (though not a direct dispute of this specific bill-approval feature). Missing for 10: detailed documentation of bill upload/OCR ingestion, explicit multi-tier approval routing configuration, and independent hands-on validation of the bill-pay approval flow.

   • [claimed-docs] “Save time with AI-powered automation of invoice entry, approval, and payments.”
   • [claimed-docs] “Payments API: Manage vendors and send ACH, domestic wires, and checks”
   • [claimed-docs] “Issue vendor-specific cards for any teams with per-transaction limits and procurement approval flows.”
   • [claimed-docs] “Brex is the first fully unified spend platform — with global corporate cards, expense management, reimbursements, travel, and bill pay.”
   • [community] “This reflects astonishingly poorly on Brex. What customer wants to hear that Brex is using 'a non-deterministic model' for production use ca…”

   proof ↗⚑ flag

   Ramp✓fullcommunity8/10

   Ramp documents bill upload (drag-and-drop invoices), automatic PO matching and GL coding, dynamic multi-department approval routing, and automated vendor payment (ramp-docs-2, ramp-docs-16, ramp-docs-17), corroborated by a positive hands-on community account of easy approval-to-payment workflows (ramp-comm-2). Missing for 10: independent third-party audit of the full bill-pay approval chain and more granular detail on rejection/exception handling in approvals.

   • [claimed-docs] “A vendor invoice is dragged into Ramp, automatically matched to its PO, coded to the right GL account, routed for approval, and paid — 7x fe…”
   • [claimed-docs] “Dynamic approval routing with parallel workflows across finance, IT, legal, and security”
   • [claimed-docs] “Four AI agents handle auto-coding, fraud prevention, approval routing, and automatic payment”
   • [community] “It's what we use for tracking expenses and getting comped for travel, meals, software licenses etc - works great in my experience. I can cli…”

   proof ↗⚑ flag

3. finance-leadSet up approval permissions so designated teammates can approve and send payments with one click

   weight 2 · round to Ramp
   Brex~partialclaimed5/10

   Evidence shows Brex has bill-pay/invoice approval automation (brex-docs-7), vendor payment sending via Payments API (brex-docs-12), and procurement approval flows for cards (brex-docs-15), implying approval workflows exist, but there is no direct documentation of configuring designated-teammate approval permissions or a one-click approve-and-send payment action for a finance-lead. Missing for 10: explicit docs on setting approval roles/permissions, evidence of a one-click approve-and-send UX, and independent confirmation this works as described.

   • [claimed-docs] “Save time with AI-powered automation of invoice entry, approval, and payments.”
   • [claimed-docs] “Payments API: Manage vendors and send ACH, domestic wires, and checks”
   • [claimed-docs] “Issue vendor-specific cards for any teams with per-transaction limits and procurement approval flows.”
   • [claimed-docs] “Team API: Manage users, locations, departments, and cards”

   proof ↗⚑ flag

   Ramp~partialcommunity6/10

   Ramp docs describe dynamic approval routing across departments and one-click, AI-driven payment flows (vendor invoice matched, coded, routed for approval, and paid), plus AI agents that handle approval routing and automatic payment, implying configurable permissions for who can approve/send. Community evidence corroborates a fast, one-click approve-and-fund experience for expenses. However, there's no explicit documentation of granular permission-setting UI/roles specifically for designating which teammates can approve and send payments with one click. Missing for 10: explicit admin-permission configuration screens/roles documentation, and independent confirmation of one-click send-payment permission setup.

   • [claimed-docs] “A vendor invoice is dragged into Ramp, automatically matched to its PO, coded to the right GL account, routed for approval, and paid — 7x fe…”
   • [claimed-docs] “Dynamic approval routing with parallel workflows across finance, IT, legal, and security”
   • [claimed-docs] “Four AI agents handle auto-coding, fraud prevention, approval routing, and automatic payment”
   • [community] “It's what we use for tracking expenses and getting comped for travel, meals, software licenses etc - works great in my experience. I can cli…”

   proof ↗⚑ flag

4. ai-native userHave vendor invoices automatically matched to purchase orders, coded, and routed for payment

   weight 2 · round to Ramp
   Brex~partialclaimed5/10

   Brex documents AI-powered invoice entry automation, automated GL coding by entity, and payment/vendor APIs (brex-docs-7, brex-docs-8, brex-docs-14, brex-docs-12), which covers invoice coding and routing for payment. However, there is no evidence of purchase-order matching or three-way match capability anywhere in the pack. Missing for 10: explicit PO-to-invoice matching functionality, documentation of approval routing workflow details, and independent/hands-on corroboration of the AI invoice automation working reliably.

   • [claimed-docs] “Save time with AI-powered automation of invoice entry, approval, and payments.”
   • [claimed-docs] “automate GL coding by entity globally”
   • [claimed-docs] “Book accruals for incomplete expenses with one click to close the books every day and automate GL coding by entity globally.”
   • [claimed-docs] “Payments API: Manage vendors and send ACH, domestic wires, and checks”
   • [claimed-docs] “Issue vendor-specific cards for any teams with per-transaction limits and procurement approval flows.”

   proof ↗⚑ flag

   Ramp✓fullclaimed8/10

   Ramp's docs directly describe the exact workflow: invoices dragged in are auto-matched to POs, auto-coded to GL, routed for approval, and paid, with dedicated AI agents for coding, approval routing, and payment execution. This is corroborated by ERP sync and categorization details, though evidence is entirely vendor-sourced with no independent hands-on validation of AP-specific matching accuracy. Missing for 10: independent/community confirmation of invoice-to-PO matching accuracy and edge-case handling.

   • [claimed-docs] “A vendor invoice is dragged into Ramp, automatically matched to its PO, coded to the right GL account, routed for approval, and paid — 7x fe…”
   • [claimed-docs] “Ramp automatically categorizes transactions based on transaction details, historical information, and your team's direct feedback, then sync…”
   • [claimed-docs] “Four AI agents handle auto-coding, fraud prevention, approval routing, and automatic payment”
   • [claimed-docs] “Real-time bidirectional sync with ERPs eliminates manual journal entries”
   • [claimed-docs] “Dynamic approval routing with parallel workflows across finance, IT, legal, and security”

   proof ↗⚑ flag

Invoicing

1. finance-leadCreate and send branded invoices with built-in payment collection

   weight 2 · round drawn
   Brex—none0/10

   Brex's evidence covers cards, expenses, bill pay, budgets, payments (ACH/wires/checks to vendors), and accounting integrations, but there is no mention of creating or sending branded customer-facing invoices with payment collection (i.e., accounts-receivable invoicing) anywhere in the docs or APIs listed.

   ⚑ flag

   Ramp—none0/10

   Ramp's evidence covers expense management, bill pay/AP automation, procurement, and ERP sync, but there is no mention of creating or sending branded customer-facing invoices with payment collection (accounts receivable), which is a distinct capability from bill pay.

   ⚑ flag

Money movement

1. founderSend money abroad that arrives in under a minute

   weight 2 · round to Brex
   Brex~partialclaimed2/10

   Brex markets 'fast global payments' and operations in 120+ countries, and its Payments API sends ACH/domestic wires/checks, but there is no documentation of international wire speed or any sub-minute delivery guarantee for cross-border transfers. missing for 10: explicit international/cross-border payment speed SLA, documentation of same-day or instant global wire capability, independent confirmation of transfer times.

   • [claimed-docs] “Unlock up to 3.70%†, fast global payments, up to 30x higher credit limits, and cash back with a Brex business account.”
   • [claimed-docs] “Modern cards, banking, expenses, accounting, and more — in 120+ countries.”
   • [claimed-docs] “Payments API: Manage vendors and send ACH, domestic wires, and checks”

   proof ↗⚑ flag

   Ramp—none0/10

   No evidence in the pack addresses international money transfer or cross-border payment speed; Ramp's evidence covers cards, bill pay, ERP sync, and vendor integrations but nothing about sending money abroad or transfer time guarantees. missing for 10: any mention of international/cross-border wire or transfer capability, evidence of transfer speed, currency/FX support.

   ⚑ flag

2. finance-leadLock in an exchange rate for a fixed window before completing a transfer

   weight 1 · round drawn
   Brex—none0/10

   No evidence in the pack mentions FX rate locking or forward-rate contracts; Brex's documented capabilities cover payments, expenses, cards, and integrations but not currency rate lock windows for transfers.

   ⚑ flag

   Ramp—none0/10

   No evidence pack item mentions FX rate locking, forward contracts, or fixed-window exchange rate guarantees for international transfers; Ramp's evidence covers expense management, procurement, ERP sync, and integrations but nothing about currency rate hedging or locking.

   ⚑ flag

3. finance-leadSend domestic ACH and wire payments to vendors

   weight 3 · round to Brex
   Brex✓fullclaimed7/10

   Brex's Payments API documentation explicitly states it can 'Manage vendors and send ACH, domestic wires, and checks,' and marketing material references bill pay/invoice payment automation, directly matching the finance-lead story of sending domestic ACH and wire payments to vendors. Missing for 10: independent/hands-on verification of successful payment execution and more detail on approval workflows or transaction limits.

   • [claimed-docs] “Payments API: Manage vendors and send ACH, domestic wires, and checks”
   • [claimed-docs] “Brex is the first fully unified spend platform — with global corporate cards, expense management, reimbursements, travel, and bill pay.”
   • [claimed-docs] “Save time with AI-powered automation of invoice entry, approval, and payments.”
   • [claimed-docs] “Book accruals for incomplete expenses with one click to close the books every day and automate GL coding by entity globally.”

   proof ↗⚑ flag

   Ramp~partialclaimed4/10

   Ramp's docs describe vendor invoices being routed, approved, and 'paid' automatically via a dedicated payment AI agent, implying built-in bill-pay/payment execution, but no evidence explicitly confirms domestic ACH or wire rail support, transfer limits, or same-day options. Missing for 10: explicit mention of ACH/wire payment methods, processing times, and any independent confirmation that payments are actually disbursed via bank rails rather than just approval routing.

   • [claimed-docs] “A vendor invoice is dragged into Ramp, automatically matched to its PO, coded to the right GL account, routed for approval, and paid — 7x fe…”
   • [claimed-docs] “Four AI agents handle auto-coding, fraud prevention, approval routing, and automatic payment”
   • [claimed-docs] “Dynamic approval routing with parallel workflows across finance, IT, legal, and security”

   proof ↗⚑ flag

4. finance-leadSend international payments in local currencies with transparent fees

   weight 3 · round to Brex
   Brex~partialclaimed4/10

   Brex references 'fast global payments' and operations 'in 120+ countries,' and its Payments API supports ACH, domestic wires, and checks, but there is no documentation of sending international payments in local currencies or of transparent/disclosed FX fees. Missing for 10: explicit local-currency international payment support, FX conversion mechanics, and transparent fee disclosure/pricing documentation.

   • [claimed-docs] “Unlock up to 3.70%†, fast global payments, up to 30x higher credit limits, and cash back with a Brex business account.”
   • [claimed-docs] “Modern cards, banking, expenses, accounting, and more — in 120+ countries.”
   • [claimed-docs] “Payments API: Manage vendors and send ACH, domestic wires, and checks”

   proof ↗⚑ flag

   Ramp—none0/10

   No evidence in the pack addresses international payments, local currency support, or FX fee transparency—only US-focused corporate card, expense, and AP automation features are documented.

   ⚑ flag

Multi currency

1. founderHold and manage balances in multiple currencies from one account

   weight 2 · round drawn
   Brex—none0/10

   Evidence shows global card/banking reach in 120+ countries and fast global payments, but nothing describes holding or managing balances in multiple currencies within a single account. Missing for 10: any explicit multi-currency wallet/balance feature, FX conversion mechanics, or account structure supporting simultaneous currency balances.

   • [claimed-docs] “Unlock up to 3.70%†, fast global payments, up to 30x higher credit limits, and cash back with a Brex business account.”
   • [claimed-docs] “Modern cards, banking, expenses, accounting, and more — in 120+ countries.”

   proof ↗⚑ flag

   Ramp—none0/10

   The evidence pack covers card issuance, expense automation, ERP sync, and integrations, but contains no mention of multi-currency account balances or FX holding capabilities. Multi-currency balance management is a fair axis for a corporate finance/spend platform, so absence of evidence yields 'none'.

   ⚑ flag

2. founderReceive payments using local account details in multiple currencies

   weight 2 · round drawn
   Brex—none0/10

   Brex evidence covers corporate cards, spend management, and outbound payments (ACH, wires, checks via the Payments API) but contains no mention of receiving payments via local account details in multiple currencies (e.g., local IBAN/account numbers for USD, EUR, GBP, etc.). The 'fast global payments' and '120+ countries' claims refer to outbound/global card acceptance, not local receiving accounts.

   • [claimed-docs] “Payments API: Manage vendors and send ACH, domestic wires, and checks”
   • [claimed-docs] “Unlock up to 3.70%†, fast global payments, up to 30x higher credit limits, and cash back with a Brex business account.”
   • [claimed-docs] “Modern cards, banking, expenses, accounting, and more — in 120+ countries.”

   proof ↗⚑ flag

   Ramp—none0/10

   Ramp's evidence pack covers cards, expense management, bill pay, ERP sync, and banking integrations, but nothing describes receiving inbound payments via local account details (e.g., local IBAN/ACH/SWIFT receiving accounts) in multiple currencies — this is a receivables/multi-currency collection capability not mentioned anywhere in the pack. Missing for 10: any mention of local currency receiving accounts, multi-currency invoicing/collections, or global payment-in details.

   ⚑ flag

Operational efficiency

1. finance-leadSearch across all transactions, vendors, and cards from one universal search bar and jump straight into initiating a payment

   weight 1 · round drawn
   Brex—none0/10

   The evidence pack documents separate APIs (Transactions, Payments, Expenses, Team) and integrations, but nowhere describes a unified 'universal search bar' UI that lets a finance-lead search transactions, vendors, and cards together and jump into initiating a payment. No product screenshots, docs, or community reports confirm such a consolidated search experience.

   • [claimed-docs] “Payments API: Manage vendors and send ACH, domestic wires, and checks”
   • [claimed-docs] “Transactions API: View your transactions, accounts, and statements”
   • [claimed-docs] “Expenses API: View and manage card expenses data, receipt match and receipt uploads”
   • [claimed-docs] “Team API: Manage users, locations, departments, and cards”

   proof ↗⚑ flag

   Ramp—none0/10

   No evidence pack item describes a universal/global search bar spanning transactions, vendors, and cards, nor any 'jump straight into initiating a payment' from search results. The evidence covers auto-categorization, invoice matching, approval routing, and integrations, but nothing about a unified search UX.

   ⚑ flag

Payment transparency

1. finance-leadSee the exact delivery estimate for an ACH or wire transfer before confirming it

   weight 2 · round drawn
   Brex—none0/10

   Brex's Payments API supports sending ACH, wires, and checks, but no evidence shows a delivery-estimate or ETA feature surfaced to finance leads before confirming a transfer; missing for 10: any documentation of delivery-time estimates, confirmation UI, or timing guarantees for ACH/wire payments.

   • [claimed-docs] “Payments API: Manage vendors and send ACH, domestic wires, and checks”

   proof ↗⚑ flag

   Ramp—none0/10

   No evidence pack item mentions ACH/wire delivery time estimates or any pre-confirmation display of settlement dates for payments; evidence covers card capture, invoice matching, ERP sync, integrations, and dev tools, none of which touch payment delivery estimates.

   ⚑ flag

Agent access

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

   weight 2 · round drawn
   Brex✓fullprobed9/10

   A direct probe confirms Brex serves a proper llms.txt file at developer.brex.com/llms.txt (HTTP 200) with a structured table of contents pointing to agent-friendly docs, and Brex also documents an MCP server for agent interaction, reinforcing an agent-oriented docs strategy. Missing for 10: independent third-party confirmation of an agent actually consuming 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

   Ramp✓fullprobed9/10

   Ramp publishes a documented llms.txt indexing structure (llms.txt, llms-guides.txt, llms-api.txt, llms-full.txt, OpenAPI spec) explicitly designed for LLM/agent consumption, and a live probe confirms HTTP 200 with machine-readable usage instructions. Missing for 10: independent third-party corroboration of an agent actually consuming these files in a real workflow.

   • [claimed-docs] “fetch: /llms.txt (LLM index), /llms-guides.txt (guides index), /llms-guides/<slug>.txt (specific guide), /llms-api.txt (API reference), /llm…”
   • [claimed-docs] “fetch: /llms.txt (LLM index), /llms-guides.txt (guides index), /llms-guides/<slug>.txt (specific guide), /llms-api.txt (API reference)... or…”
   • [claimed-docs] “If the URL is under /developer-api/v1/rate-limiting -> /llms-guides/rate-limiting.txt”
   • [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

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

   weight 2 · round to Ramp
   Brex~partialprobed5/10

   Brex exposes REST APIs (Accounting, Payments, Transactions, Team, Webhooks) and webhooks that can be scripted/automated outside a UI, which supports headless/CI-style automation, and Postman/Pipedream/Zapier integration docs further show programmatic, non-interactive usage patterns. However, there is no explicit documentation of a CLI, SDK, service-account/API-key auth flow for CI pipelines, or any first-party guidance on running Brex workflows in automated/headless CI environments. missing for 10: explicit CI/headless automation guidance, CLI or SDK for scripting, service-account/token auth documentation for non-interactive use, independent confirmation of CI usage.

   • [claimed-docs] “Accounting API: View and manage accounting data”
   • [claimed-docs] “Team API: Manage users, locations, departments, and cards”
   • [claimed-docs] “Webhooks API: Send real-time notifications based on events”
   • [claimed-docs] “Payments API: Manage vendors and send ACH, domestic wires, and checks”
   • [claimed-docs] “Transactions API: View your transactions, accounts, and statements”
   • [claimed-docs] “Postman is a browser or desktop app used for API testing. It gives you a UI to easily test and play around with API calls without having to …”
   • [claimed-docs] “Pipedream is a low-code integration platform that Brex integrates with to enable various use cases including bulk creating users, setting mo…”
   • [claimed-docs] “Monthly Export of Brex Card Transactions to CSV in Google Drive”
   • [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

   Ramp~partialprobed6/10

   Ramp provides a documented official CLI (ramp-cli) and a full REST/OpenAPI developer API plus machine-readable docs (llms.txt, llms-api.txt, openapi/developer-api.json), which together enable scripted/headless automation suitable for CI pipelines. However, there is no first-party or community evidence of actual CI usage, rate-limit guidance for automated pipelines, or examples of running the CLI unattended. Missing for 10: documented CI/CD integration examples, independent confirmation of headless CLI use in production pipelines, and details on authentication/rate limits for automated batch jobs.

   • [probe] “official CLI documented at https://github.com/ramp-public/ramp-cli”
   • [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] “fetch: /llms.txt (LLM index), /llms-guides.txt (guides index), /llms-guides/<slug>.txt (specific guide), /llms-api.txt (API reference), /llm…”
   • [claimed-docs] “fetch: /llms.txt (LLM index), /llms-guides.txt (guides index), /llms-guides/<slug>.txt (specific guide), /llms-api.txt (API reference)... or…”
   • [claimed-docs] “If the URL is under /developer-api/v1/rate-limiting -> /llms-guides/rate-limiting.txt”

   proof ↗⚑ flag

3. ai-native userPlug MCP servers into this product so it can use their tools

   weight 3 · round drawn
   Brex—none0/10

   Evidence shows Brex publishes its own MCP server so external AI assistants can call Brex's tools (brex-docs-21, brex-probe-3) — this is the opposite direction from the story, which asks whether Brex itself can plug in and consume external MCP servers as a client. No evidence exists of Brex acting as an MCP client or letting users attach third-party MCP servers for it to use.

   • [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

   Ramp—none0/10

   Evidence shows Ramp exposes its own official MCP server (ramp-probe-2) for others to connect to, but there is no evidence Ramp itself can act as an MCP client and plug in external MCP servers to extend its AI agents' toolset. Missing for 10: any documentation of Ramp's AI agents consuming external MCP servers, any client-side MCP configuration UI, or user guides for adding third-party MCP tool providers.

   • [probe] “official MCP server documented at https://support.ramp.com/ramp-mcp”
   • [claimed-docs] “Four AI agents handle auto-coding, fraud prevention, approval routing, and automatic payment”

   proof ↗⚑ flag

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

   weight 3 · round to Brex
   Brex✓fullprobed8/10

   Brex documents an official MCP server (developer.brex.com/docs/mcp) that lets AI assistants manage expenses, look up users, check cards, review transactions, and track bills via natural language, confirmed by both docs and a probe. Missing for 10: independent hands-on community corroboration of the MCP server itself (community evidence found is unrelated to MCP) and details on auth/security model.

   • [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

   Ramp✓fullprobed7/10

   Ramp is a finance SaaS platform (not itself an agent), so shipping an official MCP server is a fair, applicable axis, and evidence confirms one exists at support.ramp.com/ramp-mcp alongside machine-readable LLM/API docs and an open API for connectivity. Missing for 10: detailed documentation of MCP server capabilities/tools, and independent/hands-on confirmation that the MCP server works as advertised.

   • [probe] “official MCP server documented at https://support.ramp.com/ramp-mcp”
   • [claimed-docs] “fetch: /llms.txt (LLM index), /llms-guides.txt (guides index), /llms-guides/<slug>.txt (specific guide), /llms-api.txt (API reference), /llm…”
   • [claimed-docs] “Ramp also supports custom CSV exports and an open API for flexible connectivity.”

   proof ↗⚑ flag

5. ai-native userUse an official CLI

   weight 2 · round to Ramp
   Brex—none0/10

   No evidence of an official Brex CLI tool; developer docs mention APIs, Postman, Pipedream, Zapier, and an MCP server, but no CLI is documented.

   ⚑ flag

   Ramp✓fullprobed7/10

   A probe confirms an official CLI repo at github.com/ramp-public/ramp-cli, satisfying the core ask for an AI-native official CLI. Missing for 10: no first-party docs describing CLI features/usage in depth, no independent hands-on review or community corroboration of the CLI's capabilities.

   • [probe] “official CLI documented at https://github.com/ramp-public/ramp-cli”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Brex✓fullprobed8/10

   Brex has an extensive documented public API surface (Accounting, Budgets, Webhooks, Team, Expenses, Payments, Transactions, Onboarding, Travel) with a quickstart guide, llms.txt discovery, Postman support, and even an MCP server for AI-native agentic access, giving strong evidence AI-native users can drive Brex programmatically. missing for 10: no live/verified OpenAPI spec (candidate URLs returned 404), and no independent third-party corroboration of API robustness beyond vendor docs.

   • [claimed-docs] “Check out our quickstart guide to get up and running making your first Brex API call in just a few minutes.”
   • [claimed-docs] “Accounting API: View and manage accounting data”
   • [claimed-docs] “Budgets API: Manage budgets and budget programs”
   • [claimed-docs] “Webhooks API: Send real-time notifications based on events”
   • [claimed-docs] “Team API: Manage users, locations, departments, and cards”
   • [claimed-docs] “Expenses API: View and manage card expenses data, receipt match and receipt uploads”
   • [claimed-docs] “Payments API: Manage vendors and send ACH, domestic wires, and checks”
   • [claimed-docs] “Transactions API: View your transactions, accounts, and statements”
   • [claimed-docs] “Onboarding API: Refer your customers and personal contacts to Brex and prefill signup information”
   • [claimed-docs] “Travel API: View trips made in Brex Travel”
   • [claimed-docs] “Brex uses webhooks to send real-time notifications when events happen in the accounts that you manage.”
   • [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] “Postman is a browser or desktop app used for API testing. It gives you a UI to easily test and play around with API calls without having to …”
   • [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] “official MCP server documented at https://developer.brex.com/docs/mcp”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.brex.com/openapi.json, https://developer.brex.com/swagger.json, https://developer.…”

   proof ↗⚑ flag

   Ramp✓fullprobed8/10

   Ramp publishes a documented public Developer API with OpenAPI spec, LLM-readable docs (/llms.txt, /llms-api.txt), and rate-limiting guides, confirmed by direct probes (200 OK) plus an official MCP server and CLI extending programmatic/AI-native access. Missing for 10: independent third-party developer reports of building against the API, and more detail on auth/scopes beyond the doc index.

   • [claimed-docs] “fetch: /llms.txt (LLM index), /llms-guides.txt (guides index), /llms-guides/<slug>.txt (specific guide), /llms-api.txt (API reference), /llm…”
   • [claimed-docs] “fetch: /llms.txt (LLM index), /llms-guides.txt (guides index), /llms-guides/<slug>.txt (specific guide), /llms-api.txt (API reference)... or…”
   • [claimed-docs] “If the URL is under /developer-api/v1/rate-limiting -> /llms-guides/rate-limiting.txt”
   • [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/ramp-mcp”
   • [probe] “official CLI documented at https://github.com/ramp-public/ramp-cli”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Brex—none0/10

   Brex documents many separate API modules (Accounting, Budgets, Team, Payments, etc.) and an MCP server for AI assistants, but there is no evidence of a mechanism to issue scoped or least-privilege API credentials/tokens specifically for an agent (e.g., OAuth scopes, granular API-key permissions, or agent-specific credential issuance).

   • [claimed-docs] “Accounting API: View and manage accounting data”
   • [claimed-docs] “Budgets API: Manage budgets and budget programs”
   • [claimed-docs] “Team API: Manage users, locations, departments, and cards”
   • [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

   Ramp—none0/10

   Ramp has a developer API, OpenAPI spec, and an official MCP server, so scoped credentialing is a fair capability to ask about for an API/agentic platform — but the evidence pack contains no mention of API keys, OAuth scopes, role-based permissions, or any mechanism to issue least-privilege credentials specifically for an AI agent.

   ⚑ flag

8. ai-native userBuild against official SDKs

   weight 2 · round to Ramp
   Brex—none0/10

   Evidence shows extensive REST API documentation (Accounting, Budgets, Team, Payments, Transactions, etc.), a quickstart guide, Postman collection, and third-party low-code integrations (Pipedream, Zapier), but no mention anywhere of official client SDKs (e.g., Python/JS/Go libraries). A probe for an OpenAPI spec that could underpin SDK generation also returned 404s across all candidate paths, suggesting no discoverable machine-readable spec for SDK tooling.

   • [claimed-docs] “Accounting API: View and manage accounting data”
   • [claimed-docs] “Check out our quickstart guide to get up and running making your first Brex API call in just a few minutes.”
   • [claimed-docs] “Postman is a browser or desktop app used for API testing. It gives you a UI to easily test and play around with API calls without having to …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.brex.com/openapi.json, https://developer.brex.com/swagger.json, https://developer.…”

   proof ↗⚑ flag

   Ramp~partialprobed7/10

   Ramp provides a public developer API with OpenAPI spec, LLM-friendly docs (llms.txt/llms-api.txt), an official CLI, and an official MCP server, all of which let AI-native developers build against Ramp programmatically. However, no evidence of dedicated language SDKs (e.g. Python/Node client libraries) is present—only raw API/OpenAPI access plus CLI/MCP tooling. Missing for 10: official first-party SDK packages in specific languages, independent developer corroboration of SDK usage.

   • [claimed-docs] “fetch: /llms.txt (LLM index), /llms-guides.txt (guides index), /llms-guides/<slug>.txt (specific guide), /llms-api.txt (API reference), /llm…”
   • [claimed-docs] “fetch: /llms.txt (LLM index), /llms-guides.txt (guides index), /llms-guides/<slug>.txt (specific guide), /llms-api.txt (API reference)... or…”
   • [claimed-docs] “If the URL is under /developer-api/v1/rate-limiting -> /llms-guides/rate-limiting.txt”
   • [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/ramp-mcp”
   • [probe] “official CLI documented at https://github.com/ramp-public/ramp-cli”

   proof ↗⚑ flag

9. ai-native userSubscribe to events via webhooks

   weight 2 · round to Brex
   Brex✓fullclaimed8/10

   Brex has a dedicated Webhooks API with first-party docs explicitly describing real-time event notifications for account activity, directly matching the story. Missing for 10: independent/hands-on developer corroboration of webhook reliability and no evidence of event-type coverage breadth or payload examples.

   • [claimed-docs] “Webhooks API: Send real-time notifications based on events”
   • [claimed-docs] “Brex uses webhooks to send real-time notifications when events happen in the accounts that you manage.”

   proof ↗⚑ flag

   Ramp—none0/10

   The evidence pack details Ramp's developer API, OpenAPI spec, MCP server, and CLI, but never mentions webhook subscriptions or event notifications anywhere. Webhooks are a plausible capability for a platform with a full developer API, so absence of evidence means this axis is unmet rather than inapplicable.

   ⚑ flag

Agentic features

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

   weight 2 · round to Ramp
   Brex!disputedcontradicted4/10

   Brex markets AI-powered features like an 'AI-powered expense assistant' and AI automation for invoices/GL coding, implying AI-generated insights from user financial data (brex-docs-7, brex-docs-16, brex-docs-9). However, hands-on community discussion of Brex's own AI chatbot demo reports concrete factual errors (bot miscounted/misdated receipts) and criticism that the underlying model is non-deterministic and unreliable for financial insight tasks, directly contradicting the polished vendor claims (brex-comm-1, brex-comm-4). Missing for 10: first-party documentation of a concrete insights/suggestions feature (e.g., dashboards with AI commentary), independent verification that current production AI features are accurate, and resolution of the hallucination concerns raised by the community.

   • [claimed-docs] “Save time with AI-powered automation of invoice entry, approval, and payments.”
   • [claimed-docs] “Make expenses a breeze for employees and managers with automated receipts, an AI-powered expense assistant, in-app travel bookings and itine…”
   • [claimed-docs] “8 reasons to switch to AI-powered financial operations”
   • [community] “This reflects astonishingly poorly on Brex. What customer wants to hear that Brex is using 'a non-deterministic model' for production use ca…”
   • [community] “Is it me or is the bot's output in the section 'Give a Bot a Fish' incorrect? It states that the most recent receipt is from Mar 5th, 2023 b…”

   proof ↗⚑ flag

   Ramp✓fullcommunity7/10

   Ramp documents multiple AI-generated insights/suggestions embedded in the product itself: auto-filled memos/categories at swipe, AI-driven invoice coding and matching, hotel rebooking suggestions, contract/screenshot parsing for intake, and dedicated AI agents for coding, fraud, approvals and payments. These are first-party claims with some corroboration via community praise of smooth automated workflows (e.g., instant card issuance and approval flows), though independent verification of the 'AI-generated insight' quality specifically is thin. Missing for 10: independent hands-on evaluation of AI insight accuracy/usefulness, and clearer distinction between rule-based automation vs. true generative insights.

   • [claimed-docs] “Auto-receipt capture at the moment of card swipe with AI-filled memos and categories”
   • [claimed-docs] “A vendor invoice is dragged into Ramp, automatically matched to its PO, coded to the right GL account, routed for approval, and paid — 7x fe…”
   • [claimed-docs] “Hotel rate monitoring with automatic rebooking when prices drop $50+”
   • [claimed-docs] “AI-powered intake parses contracts and screenshots to auto-populate request forms”
   • [claimed-docs] “Ramp automatically categorizes transactions based on transaction details, historical information, and your team's direct feedback, then sync…”
   • [claimed-docs] “Four AI agents handle auto-coding, fraud prevention, approval routing, and automatic payment”
   • [community] “It's what we use for tracking expenses and getting comped for travel, meals, software licenses etc - works great in my experience. I can cli…”

   proof ↗⚑ flag

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

   weight 2 · round to Ramp
   Brex~partialclaimed6/10

   Brex documents several automation building blocks that can run without manual triggering — auto-enforced budget controls, AI-powered invoice entry/approval/payment automation, automated GL coding/accruals, a Webhooks API for real-time event-driven triggers, and third-party workflow automation via Pipedream/Zapier (e.g., bulk card issuance, scheduled CSV exports) — which together let an AI-native user configure background automations. However, there is no first-party 'agent scheduler' or persistent autonomous-agent runtime; the MCP server (brex-docs-21) is framed as an interactive assistant interface rather than an autonomous background job runner. Missing for 10: a dedicated autonomous-agent/scheduling feature explicitly designed for unattended multi-step AI workflows, and independent confirmation that these automations run reliably without human oversight.

   • [claimed-docs] “Webhooks API: Send real-time notifications based on events”
   • [claimed-docs] “Set budgets and allocate spend limits with auto-enforced controls that empower employees to spend wisely.”
   • [claimed-docs] “Save time with AI-powered automation of invoice entry, approval, and payments.”
   • [claimed-docs] “automate GL coding by entity globally”
   • [claimed-docs] “Book accruals for incomplete expenses with one click to close the books every day and automate GL coding by entity globally.”
   • [claimed-docs] “Pipedream is a low-code integration platform that Brex integrates with to enable various use cases including bulk creating users, setting mo…”
   • [claimed-docs] “Monthly Export of Brex Card Transactions to CSV in Google Drive”
   • [claimed-docs] “you can use this integration to create virtual cards for a WFH stipend where the card limit resets every month”
   • [claimed-docs] “The Brex MCP server lets AI assistants interact directly with your Brex account: manage expenses, look up users, check cards, review banking…”

   proof ↗⚑ flag

   Ramp✓fullclaimed8/10

   Ramp's docs describe multiple autonomous background automations — auto-receipt capture, invoice matching/coding/approval/payment, hotel rate monitoring with auto-rebooking, auto top-up with balance targets, and four dedicated AI agents handling coding, fraud, approvals, and payment end-to-end without manual triggering. This directly matches the story of AI-native background automation. Missing for 10: independent/hands-on verification that these automations run fully autonomously in production (community evidence only confirms manual card/expense workflows, not the autonomous agent features).

   • [claimed-docs] “Auto-receipt capture at the moment of card swipe with AI-filled memos and categories”
   • [claimed-docs] “A vendor invoice is dragged into Ramp, automatically matched to its PO, coded to the right GL account, routed for approval, and paid — 7x fe…”
   • [claimed-docs] “Hotel rate monitoring with automatic rebooking when prices drop $50+”
   • [claimed-docs] “Auto top-up from linked checking accounts with target balance automation and low balance alerts”
   • [claimed-docs] “Four AI agents handle auto-coding, fraud prevention, approval routing, and automatic payment”

   proof ↗⚑ flag

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

   weight 3 · round to Ramp
   Brex!disputedcontradicted5/10

   Brex documents an 'AI-powered expense assistant' and AI-driven automation for invoice/GL coding (brex-docs-16, brex-docs-7, brex-docs-9), suggesting a built-in assistant users can delegate tasks to. However, hands-on community discussion of Brex's own AI demo reports factual errors in the assistant's output (misidentifying the most recent receipt date) and skepticism about using a non-deterministic model for production financial tasks (brex-comm-1, brex-comm-2, brex-comm-4), directly contradicting reliability claims. Missing for 10: independent corroboration of the assistant working correctly in production, clear scope/limits of what tasks can be delegated, and resolution of the reported output error.

   • [claimed-docs] “Make expenses a breeze for employees and managers with automated receipts, an AI-powered expense assistant, in-app travel bookings and itine…”
   • [claimed-docs] “Save time with AI-powered automation of invoice entry, approval, and payments.”
   • [claimed-docs] “8 reasons to switch to AI-powered financial operations”
   • [community] “This reflects astonishingly poorly on Brex. What customer wants to hear that Brex is using 'a non-deterministic model' for production use ca…”
   • [community] “It seems like they're using OpenAI's API... but they should be crystal clear about this. The expenses example seems like sloppy engineering—…”
   • [community] “Is it me or is the bot's output in the section 'Give a Bot a Fish' incorrect? It states that the most recent receipt is from Mar 5th, 2023 b…”

   proof ↗⚑ flag

   Ramp~partialclaimed6/10

   Ramp documents built-in AI agents that autonomously handle auto-coding, fraud prevention, approval routing, and payment, plus AI-powered intake and auto-categorization — evidence of task delegation to embedded AI. However, all evidence is vendor-sourced marketing copy with no independent/hands-on corroboration of an interactive assistant experience or how a user explicitly 'delegates' vs. the AI running fully automatically in the background. Missing for 10: independent user reports of interacting with/delegating to the assistant, detail on the assistant's conversational/task-delegation UX rather than automated background agents.

   • [claimed-docs] “Four AI agents handle auto-coding, fraud prevention, approval routing, and automatic payment”
   • [claimed-docs] “AI-powered intake parses contracts and screenshots to auto-populate request forms”
   • [claimed-docs] “Ramp automatically categorizes transactions based on transaction details, historical information, and your team's direct feedback, then sync…”
   • [claimed-docs] “A vendor invoice is dragged into Ramp, automatically matched to its PO, coded to the right GL account, routed for approval, and paid — 7x fe…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Brex✓fullprobed7/10

   Brex documents an official MCP server that lets AI assistants manage expenses, look up users, check cards, and review transactions 'through natural language,' directly enabling natural-language operation of the product (brex-docs-21, brex-probe-3). However, there's no independent hands-on validation of the MCP server's reliability, and older community commentary raises general skepticism about non-deterministic AI outputs in Brex's financial workflows (brex-comm-1–4), though this pertains to a separate legacy AI feature rather than the MCP server itself. Missing for 10: independent/hands-on corroboration of the MCP server's natural-language commands working reliably in practice, and broader documentation of natural-language support beyond the MCP feature.

   • [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”
   • [community] “This reflects astonishingly poorly on Brex. What customer wants to hear that Brex is using 'a non-deterministic model' for production use ca…”

   proof ↗⚑ flag

   Ramp✓fullprobed7/10

   Ramp publishes an official MCP server (support.ramp.com/ramp-mcp) plus llms.txt/CLI docs, which directly enables AI agents/assistants to operate Ramp via natural-language commands, and it also ships internal AI agents for coding/approval/payment automation. missing for 10: hands-on/independent evidence of a user actually issuing natural-language commands through the MCP server, and detail on what actions/scopes the MCP server exposes.

   • [probe] “official MCP server documented at https://support.ramp.com/ramp-mcp”
   • [probe] “official CLI documented at https://github.com/ramp-public/ramp-cli”
   • [claimed-docs] “Four AI agents handle auto-coding, fraud prevention, approval routing, and automatic payment”
   • [claimed-docs] “fetch: /llms.txt (LLM index), /llms-guides.txt (guides index), /llms-guides/<slug>.txt (specific guide), /llms-api.txt (API reference), /llm…”

   proof ↗⚑ flag

Api quality

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

   weight 2 · round to Brex
   Brex~partialprobed4/10

   Brex publishes extensive API reference docs (Accounting, Budgets, Team, Webhooks, etc.) and a quickstart guide, and explicitly integrates with Postman so developers can 'test and play around with API calls without having to write code' (brex-docs-22, brex-docs-5). However, a probe found no OpenAPI/Swagger spec at standard endpoints (all 404s), indicating no confirmed built-in interactive/runnable API explorer on the docs site itself—Postman is an external tool rather than embedded runnable examples. Missing for 10: a native in-browser interactive API console with runnable code samples, and independent confirmation of an OpenAPI spec powering such a reference.

   • [claimed-docs] “Check out our quickstart guide to get up and running making your first Brex API call in just a few minutes.”
   • [claimed-docs] “Postman is a browser or desktop app used for API testing. It gives you a UI to easily test and play around with API calls without having to …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.brex.com/openapi.json, https://developer.brex.com/swagger.json, https://developer.…”
   • [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

   Ramp—none0/10

   Evidence confirms Ramp has an OpenAPI spec and machine-readable llms.txt/API docs for developers, but nothing indicates an interactive reference with runnable/try-it-now examples (e.g., a Swagger/Redoc-style console). Missing for 10: any mention of an interactive API console, live request execution, or embedded runnable code samples.

   • [claimed-docs] “fetch: /llms.txt (LLM index), /llms-guides.txt (guides index), /llms-guides/<slug>.txt (specific guide), /llms-api.txt (API reference), /llm…”
   • [claimed-docs] “fetch: /llms.txt (LLM index), /llms-guides.txt (guides index), /llms-guides/<slug>.txt (specific guide), /llms-api.txt (API reference)... or…”
   • [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

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

   weight 2 · round to Ramp
   Brex!disputedcontradicted3/10

   Brex's docs reference an 'openapi' URL structure (e.g. developer.brex.com/openapi/webhooks_api.md) implying spec-based documentation, but a direct probe for standard machine-readable spec files (openapi.json, swagger.json, etc.) returned 404 on all candidate paths, meaning no downloadable OpenAPI spec is actually accessible. missing for 10: a working link to a downloadable OpenAPI/Swagger JSON or YAML file, confirmation that the 'openapi' folder pages are anything more than rendered markdown docs.

   • [claimed-docs] “Brex uses webhooks to send real-time notifications when events happen in the accounts that you manage.”
   • [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

   Ramp✓fullprobed9/10

   Ramp's developer docs explicitly expose a downloadable OpenAPI spec at /openapi/developer-api.json, confirmed by both documentation references and a live probe returning HTTP 200 at the llms.txt index that lists this spec alongside other machine-readable formats. Missing for 10: independent third-party confirmation that the OpenAPI file itself is complete/valid beyond the vendor's own docs.

   • [claimed-docs] “fetch: /llms.txt (LLM index), /llms-guides.txt (guides index), /llms-guides/<slug>.txt (specific guide), /llms-api.txt (API reference), /llm…”
   • [claimed-docs] “fetch: /llms.txt (LLM index), /llms-guides.txt (guides index), /llms-guides/<slug>.txt (specific guide), /llms-api.txt (API reference)... or…”
   • [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

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

   weight 1 · round drawn
   Brex—none0/10

   No mention of a sandbox, test environment, or non-production mode anywhere in Brex's developer docs, API listings, or MCP server description; Postman usage is for testing API calls but against real accounts, not a sandbox. Missing for 10: any documented sandbox/test environment, test API keys, or separation from production data.

   • [claimed-docs] “Postman is a browser or desktop app used for API testing. It gives you a UI to easily test and play around with API calls without having to …”
   • [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] “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

   Ramp—none0/10

   No evidence of a sandbox/test environment for developers or AI agents to safely test API/MCP calls without touching production financial data; docs only reference production API/MCP/CLI endpoints. Missing for 10: any mention of sandbox mode, test API keys, staging environment, or synthetic data support.

   ⚑ flag

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

   weight 2 · round drawn
   Brex—none0/10

   The evidence pack lists numerous Brex APIs and developer docs but nowhere mentions API versioning schemes or a documented deprecation policy; the OpenAPI spec probe even returned 404s, suggesting limited machine-readable API documentation.

   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.brex.com/openapi.json, https://developer.brex.com/swagger.json, https://developer.…”
   • [claimed-docs] “Accounting API: View and manage accounting data”
   • [claimed-docs] “Check out our quickstart guide to get up and running making your first Brex API call in just a few minutes.”

   proof ↗⚑ flag

   Ramp—none0/10

   Evidence shows Ramp has a documented Developer API (OpenAPI spec, guides, rate-limiting docs) with a 'v1' path in the URL, but nowhere is there mention of a versioning scheme or a documented deprecation/sunset policy for API versions.

   • [claimed-docs] “fetch: /llms.txt (LLM index), /llms-guides.txt (guides index), /llms-guides/<slug>.txt (specific guide), /llms-api.txt (API reference), /llm…”
   • [claimed-docs] “If the URL is under /developer-api/v1/rate-limiting -> /llms-guides/rate-limiting.txt”
   • [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

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

   weight 2 · round drawn
   Brex~partialprobed6/10

   Brex documents bulk-style automation primarily through its Pipedream integration, explicitly citing 'bulk creating users, setting monthly limits for users, issuing virtual cards, and sending vendor payments,' and its API surface (Team, Payments, Budgets, Expenses) could support scripted multi-item operations. However, this relies on a third-party low-code platform rather than native bulk endpoints in Brex's own API docs, and there's no probe evidence of a bulk API or batch endpoint in the OpenAPI spec (which 404s). Missing for 10: native/first-party bulk API endpoints, documented batch limits, and independent verification of at-scale bulk operations.

   • [claimed-docs] “Pipedream is a low-code integration platform that Brex integrates with to enable various use cases including bulk creating users, setting mo…”
   • [claimed-docs] “Team API: Manage users, locations, departments, and cards”
   • [claimed-docs] “Payments API: Manage vendors and send ACH, domestic wires, and checks”
   • [claimed-docs] “Budgets API: Manage budgets and budget programs”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.brex.com/openapi.json, https://developer.brex.com/swagger.json, https://developer.…”

   proof ↗⚑ flag

   Ramp~partialprobed6/10

   Ramp exposes a public API, official CLI, and MCP server (ramp-probe-1/2/3) plus CSV export/import (ramp-docs-12) that would let an AI-native user script bulk actions, and AI agents already auto-code/categorize transactions at scale across the platform (ramp-docs-15, ramp-docs-17). However there's no direct evidence of a dedicated bulk-edit/bulk-approve UI or documented batch endpoints for acting on many items simultaneously. Missing for 10: explicit bulk-operation API endpoints or UI (bulk approve, bulk export, batch transaction updates) and independent confirmation these programmatic paths work for large-scale bulk actions.

   • [claimed-docs] “Ramp automatically categorizes transactions based on transaction details, historical information, and your team's direct feedback, then sync…”
   • [claimed-docs] “Four AI agents handle auto-coding, fraud prevention, approval routing, and automatic payment”
   • [claimed-docs] “Ramp also supports custom CSV exports and an open API for flexible connectivity.”
   • [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/ramp-mcp”
   • [probe] “official CLI documented at https://github.com/ramp-public/ramp-cli”

   proof ↗⚑ flag

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

   weight 3 · round to Ramp
   Brex~partialclaimed5/10

   Brex has a Webhooks API for event notifications and Budgets API for auto-enforced spend controls, plus Pipedream/Zapier integrations that can chain actions on events, but these require external low-code platforms rather than a native rules engine where users directly define 'if event X then action Y' automations. missing for 10: a native rule-builder/automation engine within Brex itself, documented conditional trigger-action syntax, and independent confirmation that webhook+action chains work reliably in production.

   • [claimed-docs] “Brex uses webhooks to send real-time notifications when events happen in the accounts that you manage.”
   • [claimed-docs] “Set budgets and allocate spend limits with auto-enforced controls that empower employees to spend wisely.”
   • [claimed-docs] “Pipedream is a low-code integration platform that Brex integrates with to enable various use cases including bulk creating users, setting mo…”
   • [claimed-docs] “Monthly Export of Brex Card Transactions to CSV in Google Drive”
   • [claimed-docs] “you can use this integration to create virtual cards for a WFH stipend where the card limit resets every month”

   proof ↗⚑ flag

   Ramp~partialprobed6/10

   Ramp ships several built-in automations that fire actions on events—auto top-up triggered by low balance, hotel rate rebooking on price drops, dynamic approval routing, and AI agents auto-coding/paying invoices—showing real automation depth, and its public API/MCP/CLI let developers extend this. However these are largely preset, product-specific automations rather than a general user-defined rule engine (arbitrary trigger→condition→action authoring), and there's no evidence of a configurable rules/webhooks builder for custom event handling. Missing for 10: a documented custom rule-builder UI or webhook/event API for arbitrary automations, and independent confirmation of rule flexibility beyond the shipped presets.

   • [claimed-docs] “Hotel rate monitoring with automatic rebooking when prices drop $50+”
   • [claimed-docs] “Auto top-up from linked checking accounts with target balance automation and low balance alerts”
   • [claimed-docs] “Dynamic approval routing with parallel workflows across finance, IT, legal, and security”
   • [claimed-docs] “Four AI agents handle auto-coding, fraud prevention, approval routing, and automatic payment”
   • [probe] “official MCP server documented at https://support.ramp.com/ramp-mcp”
   • [probe] “official CLI documented at https://github.com/ramp-public/ramp-cli”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Brex~partialclaimed4/10

   Brex has no native cron/scheduling API, but its documented Zapier example ('Monthly Export of Brex Card Transactions to CSV in Google Drive') and Pipedream integration examples imply recurring automated workflows can be built via third-party low-code platforms rather than Brex itself. Missing for 10: a first-party scheduler or recurring-job API, and any evidence of AI-native (MCP/agent) triggered recurring workflows.

   • [claimed-docs] “Pipedream is a low-code integration platform that Brex integrates with to enable various use cases including bulk creating users, setting mo…”
   • [claimed-docs] “Monthly Export of Brex Card Transactions to CSV in Google Drive”
   • [claimed-docs] “you can use this integration to create virtual cards for a WFH stipend where the card limit resets every month”
   • [claimed-docs] “Simplify every task that finance touches with automatic syncing across 1,000s of native integrations.”

   proof ↗⚑ flag

   Ramp~partialprobed4/10

   Ramp ships specific built-in recurring automations (auto top-up with target-balance thresholds, hotel rate monitoring/rebooking, dynamic approval routing) that run continuously without user re-triggering, and exposes an API/MCP server/CLI that could be used to build custom scheduled jobs. However there's no evidence of a general-purpose workflow/job scheduler (e.g., cron-style triggers, custom recurring automation builder) that an AI-native user could configure via the API or MCP server themselves — the cited automations are fixed product features, not user-defined scheduled workflows. Missing for 10: documentation of a programmable scheduling/trigger API for arbitrary recurring jobs, evidence the MCP server or CLI supports defining custom recurring workflows, and independent confirmation of these automations working as advertised.

   • [claimed-docs] “Hotel rate monitoring with automatic rebooking when prices drop $50+”
   • [claimed-docs] “Auto top-up from linked checking accounts with target balance automation and low balance alerts”
   • [claimed-docs] “Dynamic approval routing with parallel workflows across finance, IT, legal, and security”
   • [claimed-docs] “Four AI agents handle auto-coding, fraud prevention, approval routing, and automatic payment”
   • [probe] “official MCP server documented at https://support.ramp.com/ramp-mcp”
   • [probe] “official CLI documented at https://github.com/ramp-public/ramp-cli”

   proof ↗⚑ flag

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

   weight 1 · round drawn
   Brex—none0/10

   No evidence of any versioning, review, or rollback mechanism for automations/workflows (e.g., budget rules, approval flows, or webhook configs) — evidence only covers APIs, integrations, and general automation features without any change-history, audit-diff, or rollback capability.

   ⚑ flag

   Ramp—none0/10

   No evidence of version history, review workflows, or rollback capability for Ramp's automations (approval rules, agent actions, categorization rules, etc.). The evidence covers what the automations do, but nothing about auditing, versioning, or reverting automation configurations/agent decisions.

   ⚑ flag

Card controls

1. finance-leadSet department or program budgets with automatically enforced spend limits

   weight 2 · round to Brex
   Brex✓fullclaimed7/10

   Brex explicitly markets budgets with auto-enforced spend limits (brex-docs-6) and offers a dedicated Budgets API for managing budgets and budget programs (brex-docs-2), plus Team API for department/user structuring (brex-docs-4). Missing for 10: independent/hands-on verification of enforcement behavior and no detailed docs excerpt showing department-level scoping specifics beyond marketing copy.

   • [claimed-docs] “Set budgets and allocate spend limits with auto-enforced controls that empower employees to spend wisely.”
   • [claimed-docs] “Budgets API: Manage budgets and budget programs”
   • [claimed-docs] “Team API: Manage users, locations, departments, and cards”

   proof ↗⚑ flag

   Ramp~partialcommunity6/10

   Ramp docs reference multi-entity support with entity-level restrictions, dynamic approval routing, and card issuance controls, implying budget/spend-limit enforcement by department, but there is no explicit first-party documentation of setting a hard department/program budget cap with automatic enforcement (e.g., blocking spend once a budget threshold is reached) nor independent confirmation of this specific behavior. missing for 10: explicit documentation of budget-setting UI/API tying spend limits to departments/programs, evidence of automatic blocking/alerts when budgets are exceeded, and independent/hands-on confirmation of enforcement in practice.

   • [claimed-docs] “Multi-entity support with entity-level restrictions and consolidated reporting”
   • [claimed-docs] “Dynamic approval routing with parallel workflows across finance, IT, legal, and security”
   • [community] “It's what we use for tracking expenses and getting comped for travel, meals, software licenses etc - works great in my experience. I can cli…”

   proof ↗⚑ flag

2. finance-leadSet per-card spend limits and granular controls for each employee

   weight 3 · round to Brex
   Brex✓fullclaimed7/10

   Brex explicitly advertises budgets and per-transaction/per-card spend limits with auto-enforced controls (brex-docs-6, brex-docs-15) and exposes a Budgets API and Team API for managing users, departments, and cards (brex-docs-2, brex-docs-4), directly matching the finance-lead's need for granular per-employee card controls. missing for 10: independent/hands-on verification of the granularity of controls in practice and no dedicated documentation excerpt detailing exact limit types (e.g., merchant category, time-based) beyond marketing copy.

   • [claimed-docs] “Set budgets and allocate spend limits with auto-enforced controls that empower employees to spend wisely.”
   • [claimed-docs] “Issue vendor-specific cards for any teams with per-transaction limits and procurement approval flows.”
   • [claimed-docs] “Budgets API: Manage budgets and budget programs”
   • [claimed-docs] “Team API: Manage users, locations, departments, and cards”

   proof ↗⚑ flag

   Ramp~partialcommunity5/10

   Evidence shows employees can quickly spin up new cards with approval workflows (ramp-comm-2) and that Ramp supports entity-level restrictions and dynamic approval routing (ramp-docs-14, ramp-docs-16), implying some granular control, but there is no explicit documentation of setting per-card numeric spend limits or category/merchant-level restrictions per employee. missing for 10: explicit docs on per-card spend limit configuration, merchant/category-level card controls, and independent verification of granularity.

   • [claimed-docs] “Multi-entity support with entity-level restrictions and consolidated reporting”
   • [claimed-docs] “Dynamic approval routing with parallel workflows across finance, IT, legal, and security”
   • [community] “It's what we use for tracking expenses and getting comped for travel, meals, software licenses etc - works great in my experience. I can cli…”

   proof ↗⚑ flag

3. finance-leadInstantly freeze a lost or stolen card and order a replacement

   weight 2 · round drawn
   Brex—none0/10

   The evidence pack mentions a Team API that can 'manage users, locations, departments, and cards' but never describes freezing a lost/stolen card or ordering a replacement. No docs, community, or probe evidence confirms this specific capability. Missing for 10: explicit documentation or UI/API evidence of card freeze and replacement ordering workflow.

   • [claimed-docs] “Team API: Manage users, locations, departments, and cards”

   proof ↗⚑ flag

   Ramp—none0/10

   Ramp is a corporate card platform where freezing/replacing lost cards is a standard, expected capability, but no evidence item describes card freezing or replacement workflows — only card issuance speed (ramp-comm-2) and unrelated features (receipts, AP automation, bill pay, ERP sync) are covered. Missing for 10: any documentation or community mention of freezing a lost/stolen card, ordering a replacement, or related self-service card controls.

   ⚑ flag

4. finance-leadRequest a transaction limit increase directly from a self-service screen

   weight 1 · round drawn
   Brex—none0/10

   Evidence shows budgets/spend-limit setting and per-transaction limits for cards (brex-docs-6, brex-docs-15) but no mention of a self-service screen for requesting a transaction limit increase or an approval workflow for such requests.

   • [claimed-docs] “Set budgets and allocate spend limits with auto-enforced controls that empower employees to spend wisely.”
   • [claimed-docs] “Issue vendor-specific cards for any teams with per-transaction limits and procurement approval flows.”
   • [claimed-docs] “Budgets API: Manage budgets and budget programs”

   proof ↗⚑ flag

   Ramp—none0/10

   The evidence pack contains no mention of a self-service screen for requesting card/transaction limit increases; only general card issuance and expense-tracking mentions appear (ramp-comm-2) but nothing about limit-increase requests.

   ⚑ flag

Card issuance

1. finance-leadInstantly create virtual cards scoped to a specific purpose like ad spend or a single vendor

   weight 3 · round to Brex
   Brex~partialclaimed7/10

   Vendor docs explicitly describe issuing vendor-specific virtual cards with per-transaction limits and procurement approval flows, plus budget-based auto-enforced spend limits and a Team API to manage cards, directly matching the story; a Pipedream example even shows programmatic virtual card creation for a recurring stipend use case. However, all evidence is vendor-authored with no independent/hands-on confirmation of speed ('instantly') or real-world reliability of the scoping controls. Missing for 10: independent or hands-on verification of instant card creation and real customer confirmation of vendor/purpose-scoped limits working as described.

   • [claimed-docs] “Issue vendor-specific cards for any teams with per-transaction limits and procurement approval flows.”
   • [claimed-docs] “Set budgets and allocate spend limits with auto-enforced controls that empower employees to spend wisely.”
   • [claimed-docs] “Team API: Manage users, locations, departments, and cards”
   • [claimed-docs] “you can use this integration to create virtual cards for a WFH stipend where the card limit resets every month”
   • [claimed-docs] “Budgets API: Manage budgets and budget programs”

   proof ↗⚑ flag

   Ramp~partialcommunity6/10

   Community evidence confirms Ramp lets users spin up a new virtual/business expense card in under a minute for a specific purchase, supporting instant, purpose-scoped card creation. However, there's no direct first-party documentation explicitly describing vendor- or category-locked virtual card controls (e.g., merchant-lock, spend-category restrictions) beyond general references to approvals and multi-entity restrictions. Missing for 10: explicit docs on merchant/category-locking rules for virtual cards, admin UI screenshots/workflow for scoping a card to a single vendor or ad-spend category, and independent verification of that specific control granularity.

   • [community] “It's what we use for tracking expenses and getting comped for travel, meals, software licenses etc - works great in my experience. I can cli…”
   • [claimed-docs] “Dynamic approval routing with parallel workflows across finance, IT, legal, and security”
   • [claimed-docs] “Multi-entity support with entity-level restrictions and consolidated reporting”

   proof ↗⚑ flag

2. finance-leadIssue physical debit or credit cards to employees with defined roles

   weight 2 · round to Brex
   Brex~partialclaimed6/10

   Brex's Team API explicitly manages users, departments, and cards, and marketing docs describe issuing vendor/team-specific cards with per-transaction limits and budget-based spend controls, supporting role-based card issuance. However, evidence never explicitly confirms physical (vs. virtual-only) card issuance or details role/permission granularity for card assignment. missing for 10: explicit mention of physical card issuance, detailed role-based permission model, independent corroboration of the physical card program.

   • [claimed-docs] “Team API: Manage users, locations, departments, and cards”
   • [claimed-docs] “Issue vendor-specific cards for any teams with per-transaction limits and procurement approval flows.”
   • [claimed-docs] “Set budgets and allocate spend limits with auto-enforced controls that empower employees to spend wisely.”
   • [claimed-docs] “Brex is the first fully unified spend platform — with global corporate cards, expense management, reimbursements, travel, and bill pay.”

   proof ↗⚑ flag

   Ramp~partialcommunity4/10

   Community evidence confirms Ramp lets a finance user quickly spin up a company card with approval and fund transfer, and docs mention entity-level restrictions and approval routing that imply role-based controls, but nothing explicitly confirms physical (vs. virtual) card issuance or granular role-based card permissions. Missing for 10: explicit mention of physical card issuance, and documentation of role-based spend controls/limits tied to employee roles.

   • [community] “It's what we use for tracking expenses and getting comped for travel, meals, software licenses etc - works great in my experience. I can cli…”
   • [claimed-docs] “Multi-entity support with entity-level restrictions and consolidated reporting”
   • [claimed-docs] “Dynamic approval routing with parallel workflows across finance, IT, legal, and security”

   proof ↗⚑ flag

Card rewards

1. founderSpend and withdraw cash abroad on a company card without hidden foreign fees

   weight 1 · round to Brex
   Brex~partialclaimed3/10

   Brex advertises global corporate cards and banking usable in 120+ countries with fast global payments, implying international spend capability, but there is no explicit claim of zero foreign transaction fees or fee-free cash withdrawals abroad. Missing for 10: explicit no-foreign-transaction-fee policy, ATM/cash withdrawal terms abroad, and independent confirmation of fee-free international spend.

   • [claimed-docs] “Modern cards, banking, expenses, accounting, and more — in 120+ countries.”
   • [claimed-docs] “Unlock up to 3.70%†, fast global payments, up to 30x higher credit limits, and cash back with a Brex business account.”
   • [claimed-docs] “Brex is the first fully unified spend platform — with global corporate cards, expense management, reimbursements, travel, and bill pay.”

   proof ↗⚑ flag

   Ramp—none0/10

   The evidence pack contains no mention of foreign transaction fees, international card usage, currency conversion, or cash withdrawal abroad — only receipt capture, AP automation, ERP sync, and integrations are covered. Axis applies to a corporate card product, but nothing in the pack supports the specific claim about fee-free international spend/withdrawal.

   ⚑ flag

2. founderEarn automatic cashback on card spend without manual redemption steps

   weight 2 · round to Brex
   Brex~partialclaimed3/10

   Brex marketing mentions cash back as a benefit of the business account, implying it accrues on spend, but there is no documentation describing the mechanism, whether it is automatic, or that no redemption step is required. missing for 10: details on automatic accrual process, redemption mechanics, any confirmation that no manual steps are needed, independent corroboration.

   • [claimed-docs] “Unlock up to 3.70%†, fast global payments, up to 30x higher credit limits, and cash back with a Brex business account.”

   proof ↗⚑ flag

   Ramp—none0/10

   The evidence pack covers expense automation, receipt capture, ERP sync, approvals, and AI agents, but contains no mention of cashback rewards or automatic cashback redemption on card spend anywhere in the docs or community evidence.

   ⚑ flag

Procurement automation

1. ai-native userHave vendor contracts parsed by AI to auto-populate procurement request forms

   weight 2 · round to Ramp
   Brex—none0/10

   No evidence of any vendor contract parsing or AI auto-population of procurement request forms; Brex's AI features cover expense assistant, invoice entry automation, and MCP-based account queries, not contract parsing for procurement. Missing for 10: any contract-ingestion/parsing feature, procurement form auto-population, or vendor document extraction capability.

   • [claimed-docs] “Save time with AI-powered automation of invoice entry, approval, and payments.”
   • [claimed-docs] “Issue vendor-specific cards for any teams with per-transaction limits and procurement approval flows.”
   • [claimed-docs] “The Brex MCP server lets AI assistants interact directly with your Brex account: manage expenses, look up users, check cards, review banking…”

   proof ↗⚑ flag

   Ramp✓fullclaimed7/10

   Ramp's docs explicitly state AI-powered intake parses contracts and screenshots to auto-populate procurement request forms, directly matching the story. Missing for 10: independent/hands-on corroboration of this specific contract-parsing feature and detail on accuracy/edge cases.

   • [claimed-docs] “AI-powered intake parses contracts and screenshots to auto-populate request forms”
   • [claimed-docs] “Dynamic approval routing with parallel workflows across finance, IT, legal, and security”

   proof ↗⚑ flag

2. ai-native userHave booked travel rates automatically monitored and rebooked when prices drop

   weight 1 · round to Ramp
   Brex—none0/10

   Brex offers a Travel API to view trips and in-app travel bookings/itinerary changes, but there is no evidence of automated rate monitoring or automatic rebooking when prices drop; missing for 10: any documentation of price-drop monitoring, automated rebooking logic, or related travel-rate alert feature.

   • [claimed-docs] “Make expenses a breeze for employees and managers with automated receipts, an AI-powered expense assistant, in-app travel bookings and itine…”
   • [claimed-docs] “Travel API: View trips made in Brex Travel”

   proof ↗⚑ flag

   Ramp✓fullclaimed7/10

   Ramp's docs explicitly claim hotel rate monitoring with automatic rebooking when prices drop $50+, directly matching the story. Missing for 10: independent/hands-on corroboration of this specific feature and details on flight/other travel rate types beyond hotels.

   • [claimed-docs] “Hotel rate monitoring with automatic rebooking when prices drop $50+”

   proof ↗⚑ flag

Receipt management

1. ai-native userHave receipts automatically captured and coded the moment a card is used, without manual entry

   weight 3 · round to Ramp
   Brex✓fullclaimed7/10

   Brex's docs describe automated receipt capture/matching (Expenses API 'receipt match and receipt uploads', 'automated receipts' in the expense assistant) and automatic GL coding by entity at close, matching the story of capture+coding without manual entry. missing for 10: independent/hands-on confirmation that receipts are captured at the exact moment of swipe with no manual step, and clearer documentation of the automation trigger mechanism.

   • [claimed-docs] “Expenses API: View and manage card expenses data, receipt match and receipt uploads”
   • [claimed-docs] “Make expenses a breeze for employees and managers with automated receipts, an AI-powered expense assistant, in-app travel bookings and itine…”
   • [claimed-docs] “automate GL coding by entity globally”
   • [claimed-docs] “Book accruals for incomplete expenses with one click to close the books every day and automate GL coding by entity globally.”

   proof ↗⚑ flag

   Ramp✓fullcommunity8/10

   Ramp's own docs claim auto-receipt capture at the moment of card swipe with AI-filled memos/categories, plus automatic categorization based on transaction details, history, and team feedback that syncs coded transactions to ERP — directly matching the story. Community evidence corroborates general ease-of-use of card issuance/expense flow, though no independent hands-on confirmation specifically of receipt auto-capture accuracy exists. Missing for 10: independent/hands-on verification of receipt-matching accuracy and edge cases (e.g., lost receipts, disputes).

   • [claimed-docs] “Auto-receipt capture at the moment of card swipe with AI-filled memos and categories”
   • [claimed-docs] “Ramp automatically categorizes transactions based on transaction details, historical information, and your team's direct feedback, then sync…”
   • [community] “It's what we use for tracking expenses and getting comped for travel, meals, software licenses etc - works great in my experience. I can cli…”

   proof ↗⚑ flag

2. finance-leadHave receipts automatically attached to the right transaction by emailing or uploading them

   weight 2 · round to Ramp
   Brex~partialclaimed6/10

   Brex's docs mention 'automated receipts' and an Expenses API with 'receipt match and receipt uploads', supporting automatic attachment of uploaded receipts to transactions, but there is no explicit mention of emailing receipts in or independent hands-on confirmation of the matching accuracy. Missing for 10: explicit email-to-receipt ingestion documentation, and independent verification that auto-matching works reliably.

   • [claimed-docs] “Expenses API: View and manage card expenses data, receipt match and receipt uploads”
   • [claimed-docs] “Make expenses a breeze for employees and managers with automated receipts, an AI-powered expense assistant, in-app travel bookings and itine…”

   proof ↗⚑ flag

   Ramp✓fullclaimed7/10

   Ramp's docs claim auto-receipt capture at swipe with AI-filled memos/categories, and automated matching/coding for vendor invoices dragged into the platform, which covers the core of automatic receipt-to-transaction matching via upload or email-based capture. Missing for 10: explicit documentation of the email-forwarding-to-transaction workflow specifically, and independent/hands-on confirmation of matching accuracy beyond vendor claims.

   • [claimed-docs] “Auto-receipt capture at the moment of card swipe with AI-filled memos and categories”
   • [claimed-docs] “A vendor invoice is dragged into Ramp, automatically matched to its PO, coded to the right GL account, routed for approval, and paid — 7x fe…”
   • [claimed-docs] “Ramp automatically categorizes transactions based on transaction details, historical information, and your team's direct feedback, then sync…”

   proof ↗⚑ flag

Signup flow

1. founderCheck my account application status while it's under review

   weight 1 · round drawn
   Brex—none0/10

   No evidence of an application-status tracking feature for founders during onboarding review; the Onboarding API only covers referral/prefill signup, and community threads discuss rejections/closures but not a status-check capability.

   ⚑ flag

   Ramp—none0/10

   No evidence in the pack describes an account application, review process, or status-tracking feature for founders during onboarding; all onboarding evidence relates to time-to-deploy after approval (e.g., ramp-docs-8), not application status tracking.

   ⚑ flag

Switching

1. founderReplace multiple point solutions for spend, bill pay, and banking with one consolidated platform

   weight 2 · round to Ramp
   Brex✓fullclaimed7/10

   Brex explicitly markets itself as a unified spend platform combining cards, banking, expense management, bill pay, accounting, and travel booking, directly matching the founder's need to consolidate point solutions (brex-docs-26, brex-docs-27, brex-docs-7, brex-docs-15, brex-docs-16). Rich API and integration documentation (Accounting, Payments, Expenses, Team, Travel APIs) supports this being a functioning single platform rather than marketing-only claims. missing for 10: independent/hands-on case studies confirming founders actually consolidated multiple tools onto Brex, and no third-party corroboration of the 'fully unified' claim beyond vendor docs.

   • [claimed-docs] “Brex is the first fully unified spend platform — with global corporate cards, expense management, reimbursements, travel, and bill pay.”
   • [claimed-docs] “Modern cards, banking, expenses, accounting, and more — in 120+ countries.”
   • [claimed-docs] “Save time with AI-powered automation of invoice entry, approval, and payments.”
   • [claimed-docs] “Issue vendor-specific cards for any teams with per-transaction limits and procurement approval flows.”
   • [claimed-docs] “Make expenses a breeze for employees and managers with automated receipts, an AI-powered expense assistant, in-app travel bookings and itine…”
   • [claimed-docs] “Accounting API: View and manage accounting data”
   • [claimed-docs] “Expenses API: View and manage card expenses data, receipt match and receipt uploads”
   • [claimed-docs] “Payments API: Manage vendors and send ACH, domestic wires, and checks”
   • [claimed-docs] “All your tools synced in one place.”

   proof ↗⚑ flag

   Ramp✓fullcommunity8/10

   Ramp's docs and case studies directly support the story: unified spend/card, bill pay/AP automation, banking/treasury (auto top-up, balances), multi-entity consolidation, and explicit customer proof of consolidating tools (Studs replacing 4 tools, AIRCO fast onboarding vs 6 months). Community evidence corroborates real-world use for expense/card issuance and approvals, reinforcing the platform's breadth beyond marketing claims. Missing for 10: independent case studies verifying bill-pay/banking consolidation claims (not just card/expense), and more third-party evidence on multi-entity/ERP sync accuracy.

   • [claimed-docs] “A vendor invoice is dragged into Ramp, automatically matched to its PO, coded to the right GL account, routed for approval, and paid — 7x fe…”
   • [claimed-docs] “Auto top-up from linked checking accounts with target balance automation and low balance alerts”
   • [claimed-docs] “Studs: Replaced 4 separate tools with Ramp's all-in-one platform”
   • [claimed-docs] “AIRCO: Full onboarding in 1 week vs. 6 months on prior platform”
   • [claimed-docs] “Multi-entity support with entity-level restrictions and consolidated reporting”
   • [community] “It's what we use for tracking expenses and getting comped for travel, meals, software licenses etc - works great in my experience. I can cli…”

   proof ↗⚑ flag

2. founderFully onboard onto a new banking platform in about a week instead of months

   weight 2 · round to Ramp
   Brex!disputedcontradicted3/10

   Brex offers an Onboarding API and quickstart docs implying fast signup (brex-docs-18, brex-docs-5), but multiple firsthand founder accounts describe painful, rejected, or abruptly terminated onboarding—requiring $1MM minimum balances for non-VC-backed startups, multi-attempt rejections, and being told to leave with 6 weeks notice—directly contradicting a quick, smooth week-long onboarding experience. missing for 10: any documented end-to-end onboarding timeline, first-party case studies showing 'week not months' onboarding, and resolution of the negative hands-on reports.

   • [claimed-docs] “Onboarding API: Refer your customers and personal contacts to Brex and prefill signup information”
   • [claimed-docs] “Check out our quickstart guide to get up and running making your first Brex API call in just a few minutes.”
   • [community] “They refused my business because I didn't have SV VC money. Chase got it instead, but they are losing it next month because of their shenani…”
   • [community] “Brex literally came to us one day in 2022 and notified us that 'We have 6 weeks to move everything off their service,' refocusing on enterpr…”
   • [community] “Brex rejected my application to open a bank account on 3 different occasions. mercury.com provided me the B2B account within the day and the…”
   • [community] “Brex founder here. We've made the difficult decision to no longer offer services to the small business market, putting the full weight of Br…”
   • [community] “This decision cannot be either changed or delayed. Your account will be closed by August 15. We've appreciated your business and wish you al…”
   • [community] “I had a terrible experience 'onboarding' with Brex last year. They approved my bootstrapped startup and sent a physical card only to rescind…”
   • [community] “(Web3 startup founder) Tried signing up for Brex and after a long and painful signup process they actually needed me to connect a different …”

   proof ↗⚑ flag

   Ramp✓fullcommunity8/10

   Ramp provides a concrete customer proof point (AIRCO: full onboarding in 1 week vs 6 months on prior platform) directly matching the story, plus general positive hands-on feedback about quick setup of cards/expenses. Missing for 10: independent third-party verification of onboarding timelines beyond vendor case studies, and detail on the actual onboarding process/steps for a new customer.

   • [claimed-docs] “AIRCO: Full onboarding in 1 week vs. 6 months on prior platform”
   • [community] “It's what we use for tracking expenses and getting comped for travel, meals, software licenses etc - works great in my experience. I can cli…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Brex~partialprobed6/10

   Brex documents a broad first-party API surface (accounting, budgets, team, expenses, payments, transactions, travel, onboarding, webhooks) covering most core UI workflows, plus an MCP server for natural-language access, suggesting strong but not confirmed full parity. There is no explicit vendor claim of 1:1 UI/API parity, no independent corroboration that every UI action is API-accessible, and a probe for a public OpenAPI spec returned 404s, limiting verifiability. Missing for 10: explicit parity statement, independent verification of completeness, discoverable OpenAPI schema.

   • [claimed-docs] “Accounting API: View and manage accounting data”
   • [claimed-docs] “Budgets API: Manage budgets and budget programs”
   • [claimed-docs] “Webhooks API: Send real-time notifications based on events”
   • [claimed-docs] “Team API: Manage users, locations, departments, and cards”
   • [claimed-docs] “Expenses API: View and manage card expenses data, receipt match and receipt uploads”
   • [claimed-docs] “Payments API: Manage vendors and send ACH, domestic wires, and checks”
   • [claimed-docs] “Transactions API: View your transactions, accounts, and statements”
   • [claimed-docs] “Onboarding API: Refer your customers and personal contacts to Brex and prefill signup information”
   • [claimed-docs] “Travel API: View trips made in Brex Travel”
   • [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] “PROBE openapi: all candidate paths 404 (https://developer.brex.com/openapi.json, https://developer.brex.com/swagger.json, https://developer.…”

   proof ↗⚑ flag

   Ramp~partialprobed6/10

   Ramp exposes a documented Developer API with OpenAPI spec, LLM-readable docs, an official MCP server, and even a public CLI, indicating broad programmatic access aligned with AI-native workflows. However, there is no explicit claim or evidence that every UI capability (e.g., hotel rebooking automation, contract intake AI, dynamic approval routing) is fully exposed via the API — only general API/ERP sync and CSV export mentions. Missing for 10: an explicit statement or independent verification of full feature parity between API and UI, and evidence covering advanced workflow features (approvals, travel, intake) being API-accessible.

   • [claimed-docs] “fetch: /llms.txt (LLM index), /llms-guides.txt (guides index), /llms-guides/<slug>.txt (specific guide), /llms-api.txt (API reference), /llm…”
   • [claimed-docs] “Ramp also supports custom CSV exports and an open API for flexible connectivity.”
   • [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/ramp-mcp”
   • [probe] “official CLI documented at https://github.com/ramp-public/ramp-cli”
   • [claimed-docs] “Ramp automatically categorizes transactions based on transaction details, historical information, and your team's direct feedback, then sync…”

   proof ↗⚑ flag

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

   weight 3 · round to Ramp
   Brex~partialcommunity4/10

   Brex exposes Transactions, Expenses, Accounting, and Team APIs that let users pull data out programmatically, and a documented Zapier example shows exporting card transactions to CSV — both are open, non-proprietary formats. However, there is no documented single 'export everything and leave' feature, no full account-data portability/archive tool, and community threads describe abrupt account closures with no mention of a clean data-export path. Missing for 10: a dedicated full-account data export/portability feature, confirmation that all data categories (not just transactions/expenses) are exportable, and independent evidence of successful full data migration on account closure.

   • [claimed-docs] “Expenses API: View and manage card expenses data, receipt match and receipt uploads”
   • [claimed-docs] “Transactions API: View your transactions, accounts, and statements”
   • [claimed-docs] “Accounting API: View and manage accounting data”
   • [claimed-docs] “Monthly Export of Brex Card Transactions to CSV in Google Drive”
   • [community] “This decision cannot be either changed or delayed. Your account will be closed by August 15. We've appreciated your business and wish you al…”

   proof ↗⚑ flag

   Ramp~partialprobed5/10

   Ramp explicitly supports custom CSV exports and an open API for connectivity, plus a documented OpenAPI spec and developer API, which gives users a path to extract their data in open formats. However, there is no evidence of a full data-portability/export-everything guarantee, no mention of standardized bulk export tooling for account closure, and no independent confirmation of completeness of exports. missing for 10: dedicated 'export all data and leave' documentation, evidence of open/standard format for full account export (not just transactions via API/CSV), independent verification of export completeness.

   • [claimed-docs] “Ramp also supports custom CSV exports and an open API for flexible connectivity.”
   • [claimed-docs] “fetch: /llms.txt (LLM index), /llms-guides.txt (guides index), /llms-guides/<slug>.txt (specific guide), /llms-api.txt (API reference), /llm…”
   • [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

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

   weight 2 · round drawn
   Brex—none0/10

   No evidence in the pack mentions data residency, regional storage options, or geographic controls for where Brex stores customer data; all docs focus on APIs, integrations, and product features. Missing for 10: any documentation of region/residency selection, data center locations, or compliance certifications tied to data storage location.

   ⚑ flag

   Ramp—none0/10

   No evidence in the pack addresses data residency, regional storage options, or compliance controls for choosing where data is stored; the evidence covers AI features, integrations, and MCP/API tooling only.

   ⚑ flag

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

   weight 3 · round drawn
   Brex—none0/10

   No evidence pack item addresses AI training data usage, opt-out controls, or data-privacy policy regarding model training; all docs cover APIs, integrations, and MCP functionality, not privacy posture toward AI training.

   ⚑ flag

   Ramp—none0/10

   No evidence pack item addresses AI-training data usage, opt-out controls, or privacy commitments regarding model training on customer data; the evidence covers product features, integrations, and MCP/CLI tooling only.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Brex—none0/10

   No evidence pack items address data retention, deletion controls, or privacy/data lifecycle policies for AI-native usage (e.g., MCP server or API data handling); the docs cover API capabilities and integrations but nothing about controlling or deleting stored data.

   ⚑ flag

   Ramp—none0/10

   Ramp's evidence pack covers expense automation, AI agents, integrations, and MCP/API access, but there is no mention of data retention policies, deletion controls, or privacy configuration relevant to AI-native users. Nothing addresses how long data/prompts are stored or how users can delete data.

   ⚑ flag

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

   weight 2 · round drawn
   Brex—none0/10

   No evidence in the pack addresses telemetry/usage-tracking opt-out settings for AI-native workflows or the MCP server; the docs cover APIs, integrations, and product features but nothing about privacy/telemetry controls.

   ⚑ flag

   Ramp—none0/10

   No evidence exists of any telemetry/usage-tracking opt-out mechanism for AI features or product analytics; Ramp is explicitly a platform that tracks employee expenses/transactions as its core service, with no mention of an opt-out control for this tracking.

   • [community] “This article's domain (Ramp) is a SaaS company that tracks employee expenses for other companies. Tracking employee credit-cards and reimbur…”

   proof ↗⚑ flag

Access control

1. finance-leadDefine granular user roles and permissions across team members, locations, and departments

   weight 3 · round drawn
   Brex~partialclaimed5/10

   Brex's Team API explicitly manages 'users, locations, departments, and cards,' suggesting structural support for organizing teams by location/department, and Budgets API allows spend controls tied to programs/teams. However, no evidence details specific role definitions (e.g., admin, bookkeeper, approver), permission granularity, or an admin console for configuring access levels. Missing for 10: explicit role/permission documentation, UI screenshots of role management, and independent confirmation of granular access control enforcement.

   • [claimed-docs] “Team API: Manage users, locations, departments, and cards”
   • [claimed-docs] “Budgets API: Manage budgets and budget programs”
   • [claimed-docs] “Issue vendor-specific cards for any teams with per-transaction limits and procurement approval flows.”

   proof ↗⚑ flag

   Ramp~partialclaimed5/10

   Ramp docs mention multi-entity support with entity-level restrictions and dynamic approval routing across finance, IT, legal, and security, which implies some role/permission granularity across entities and departments, but there is no explicit documentation of a granular role/permission system covering locations and individual team members. missing for 10: dedicated documentation of role-based access control, granular permission settings per user/location/department, and independent corroboration of these controls.

   • [claimed-docs] “Multi-entity support with entity-level restrictions and consolidated reporting”
   • [claimed-docs] “Dynamic approval routing with parallel workflows across finance, IT, legal, and security”

   proof ↗⚑ flag

Fraud detection

1. ai-native userHave AI flag anomalous or out-of-policy transactions automatically for review

   weight 2 · round to Ramp
   Brex—none0/10

   Evidence shows rule-based auto-enforced budget controls (brex-docs-6) and a general AI-powered expense assistant (brex-docs-16), but nothing describes AI automatically detecting or flagging anomalous/out-of-policy transactions for review. Community threads discuss AI reliability concerns generally but don't confirm or deny this specific capability.

   • [claimed-docs] “Set budgets and allocate spend limits with auto-enforced controls that empower employees to spend wisely.”
   • [claimed-docs] “Make expenses a breeze for employees and managers with automated receipts, an AI-powered expense assistant, in-app travel bookings and itine…”
   • [claimed-docs] “Save time with AI-powered automation of invoice entry, approval, and payments.”

   proof ↗⚑ flag

   Ramp~partialclaimed5/10

   Ramp claims a dedicated AI 'fraud prevention' agent alongside auto-coding and dynamic, multi-department approval routing, which implies automated flagging of anomalous or out-of-policy transactions for review (ramp-docs-17, ramp-docs-16). However, there is no detailed documentation of how anomaly detection thresholds work, no explicit 'flag for review' workflow description, and no independent/hands-on evidence corroborating this specific capability. Missing for 10: detailed docs on anomaly/policy-violation detection logic, explicit reviewer workflow, and independent verification of fraud-flagging accuracy.

   • [claimed-docs] “Four AI agents handle auto-coding, fraud prevention, approval routing, and automatic payment”
   • [claimed-docs] “Dynamic approval routing with parallel workflows across finance, IT, legal, and security”
   • [claimed-docs] “Ramp automatically categorizes transactions based on transaction details, historical information, and your team's direct feedback, then sync…”

   proof ↗⚑ flag

Customer support

1. founderReach live customer support at any time for urgent account issues

   weight 2 · round drawn
   Brex—none0/10

   The evidence pack contains no documentation or claims about live customer support availability, support channels, or response times for urgent account issues. Community evidence instead discusses account closures and rejections, which is unrelated to support-reliability as described in the story.

   ⚑ flag

   Ramp—none0/10

   No evidence in the pack mentions live customer support, support channels, response times, or availability guarantees; the pack only covers product features, integrations, and general community sentiment unrelated to support access.

   ⚑ flag

Deposit protection

1. finance-leadHave deposits automatically swept across partner banks to maximize FDIC insurance coverage

   weight 2 · round drawn
   Brex—none0/10

   No evidence in the pack mentions FDIC sweep networks or multi-bank deposit insurance maximization; Brex's documentation covers cards, expenses, APIs, and integrations but nothing about deposit sweep programs.

   ⚑ flag

   Ramp—none0/10

   Evidence shows only auto top-up from a linked checking account with balance targets (ramp-docs-6), not a multi-bank sweep program for maximizing FDIC coverage; no mention of partner-bank sweep networks or FDIC insurance expansion anywhere in the pack.

   • [claimed-docs] “Auto top-up from linked checking accounts with target balance automation and low balance alerts”

   proof ↗⚑ flag

Cash automation

1. finance-leadAutomate cash management with auto top-up between accounts and low-balance alerts

   weight 2 · round to Ramp
   Brex—none0/10

   The evidence pack covers Brex's cards, expenses, budgets, payments, and webhooks APIs but contains no mention of auto top-up between accounts or low-balance alert functionality, which is a fair capability to expect from a business banking/treasury platform. Missing for 10: any documentation of auto-transfer/sweep rules between accounts, low-balance threshold alerts, or treasury automation features.

   • [claimed-docs] “Unlock up to 3.70%†, fast global payments, up to 30x higher credit limits, and cash back with a Brex business account.”
   • [claimed-docs] “Transactions API: View your transactions, accounts, and statements”
   • [claimed-docs] “Brex uses webhooks to send real-time notifications when events happen in the accounts that you manage.”

   proof ↗⚑ flag

   Ramp~partialclaimed6/10

   Ramp explicitly documents auto top-up from linked checking accounts with target balance automation and low-balance alerts, directly matching the story, but this rests on a single vendor claim with no independent/hands-on corroboration and no detail on multi-account 'treasury-yield' style cash optimization or yield features. missing for 10: independent verification of auto top-up working in practice, detail on interest/yield optimization across accounts, and community evidence confirming alert reliability.

   • [claimed-docs] “Auto top-up from linked checking accounts with target balance automation and low balance alerts”

   proof ↗⚑ flag

Yield generation

1. finance-leadEarn yield on operating cash balances without moving funds to a separate institution

   weight 3 · round to Brex
   Brex~partialclaimed5/10

   Brex's marketing explicitly advertises 'up to 3.70%' yield on funds held directly in a Brex business account, indicating cash held with Brex (not moved to a separate institution) can earn yield. However, evidence is limited to a single marketing line with no detail on mechanism, eligibility, or independent verification. Missing for 10: documentation on how yield is generated (program banks/money-market sweep), terms/limits, and independent/hands-on confirmation of the yield actually being credited.

   • [claimed-docs] “Unlock up to 3.70%†, fast global payments, up to 30x higher credit limits, and cash back with a Brex business account.”

   proof ↗⚑ flag

   Ramp—none0/10

   The evidence pack mentions auto top-up from linked checking accounts and target balance automation, but there is no mention of Ramp offering interest/yield on operating cash balances held within Ramp itself, nor any treasury/yield product distinct from moving funds elsewhere.

   ⚑ flag

2. finance-leadBuild a cash cushion in a high-yield savings sub-account with automated transfer rules

   weight 2 · round to Ramp
   Brex—none0/10

   Evidence shows Brex offers a yield on cash ("Unlock up to 3.70%") but there is no mention of a distinct high-yield savings sub-account or of automated transfer rules to move cash into/out of such a sub-account.

   • [claimed-docs] “Unlock up to 3.70%†, fast global payments, up to 30x higher credit limits, and cash back with a Brex business account.”

   proof ↗⚑ flag

   Ramp~partialclaimed3/10

   Ramp documents auto top-up and target-balance automation with low-balance alerts (ramp-docs-6), which supports the 'automated transfer rules' part of the story, but no evidence explicitly confirms a high-yield savings sub-account or yield-bearing cash cushion feature. missing for 10: explicit high-yield/interest-bearing savings sub-account documentation, evidence of yield rates, and independent corroboration of treasury cash-cushion use case.

   • [claimed-docs] “Auto top-up from linked checking accounts with target balance automation and low balance alerts”

   proof ↗⚑ flag

3. founderEarn interest on balances held in multiple currencies

   weight 1 · round drawn
   Brex—none0/10

   Brex advertises up to 3.70% yield on cash balances (brex-docs-10), but there is no evidence of interest being earned specifically on balances held in multiple currencies—Brex's offering appears to be a single (USD) yield-bearing cash account with no multi-currency treasury/interest feature documented.

   • [claimed-docs] “Unlock up to 3.70%†, fast global payments, up to 30x higher credit limits, and cash back with a Brex business account.”

   proof ↗⚑ flag

   Ramp—none0/10

   No evidence in the pack mentions multi-currency accounts, FX holding, or interest/yield on non-USD balances; Ramp evidence covers cards, expense automation, integrations and AI agents but nothing about earning interest on multi-currency balances. Missing for 10: any mention of multi-currency account support, interest/yield rates, or treasury/FX yield features.

   ⚑ flag