Ramp vs Wise Business

Close automation

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

   weight 2 · round to Ramp
   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

   Wise Business—none0/10

   Evidence covers cross-border payments, multi-currency accounts, and API access for payments, but nothing about AI-driven automations, bookkeeping/close-the-books workflows, or accounting integrations that speed up month-end close.

   ⚑ flag

Developer accounting access

1. developerView and manage accounting data through a dedicated API

   weight 1 · round to Ramp
   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

   Wise Business~partialprobed3/10

   Wise exposes a documented 'Global Payments API' for sending/receiving money and business payments (wise-docs-6, wise-probe-1), which could be used to pull transaction/account data for accounting purposes, but there is no explicit documentation of endpoints for statements, balance history, or accounting-specific data management, and no OpenAPI spec is discoverable (wise-probe-2 shows 404s). Missing for 10: explicit accounting-data endpoints (statements, categorization, reconciliation), formal API reference/OpenAPI spec, and independent developer corroboration of using the API for accounting integration.

   • [claimed-docs] “How to make business payments via API from a Wise account.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.wise.com/llms.txt # Global Payments API: Send & Receive Money > Wise Platform offer domestic and c…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.wise.com/openapi.json, https://docs.wise.com/swagger.json, https://docs.wise.com/api/op…”

   proof ↗⚑ flag

Erp sync

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

   weight 3 · round to Ramp
   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

   Wise Business—none0/10

   Evidence covers payments, currency accounts, and cards, but nothing mentions accounting software sync (e.g. QuickBooks/Xero integrations) or automatic expense syncing; no such integration is documented in this evidence pack.

   ⚑ flag

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

   weight 3 · round to Ramp
   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

   Wise Business—none0/10

   Evidence shows Wise Business offers payment/API capabilities but nothing about ERP sync, journal entries, or accounting-integration connectors (e.g., QuickBooks/Xero/NetSuite bidirectional sync). No mention of any ERP integration exists in the pack.

   ⚑ flag

Account structure

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

   weight 1 · round to Wise Business
   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

   Wise Business~partialcommunity4/10

   Wise documents providing 'global account details' for receiving payments (wise-docs-9), which supports viewing account/routing numbers, but there is no evidence of a dedicated bank verification letter generation feature. Additionally, community reports show account/routing numbers can change without warning (wise-comm-2, wise-comm-3, wise-comm-5), undercutting the 'anytime' reliability implied by the story. Missing for 10: documented bank verification letter/document generation tool, and confirmation that account numbers remain stable enough to be trusted 'anytime'.

   • [claimed-docs] “Get paid easily in other currencies with global account details.”
   • [community] “I received notification that my US bank account number will stop working immediately and I should not use it anywhere and remove it from any…”
   • [community] “Due to an operational change, your USD account details for your Wise Business and Personal accounts are changing... From today, October 17, …”
   • [community] “My business works with enterprises on NET 30 to NET 90 payment terms, so having account details change without warning is a painful one to c…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   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

   Wise Business—none0/10

   The evidence pack shows Wise Business supports multi-currency accounts, global payments, and cards, but nothing about creating multiple checking sub-accounts or auto-allocating incoming deposits across them—no rules-based deposit splitting or sub-account structuring is mentioned anywhere.

   ⚑ flag

Bill pay

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

   weight 3 · round to Ramp
   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

   Wise Business—none0/10

   No evidence of bill upload, invoice capture, or approval workflow features in Wise Business; documentation covers payments, currency accounts, cards, and API for sending money, not AP bill approval routing.

   ⚑ flag

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

   weight 2 · round to Ramp
   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

   Wise Business—none0/10

   No evidence pack items mention approval workflows, permission roles, or multi-user authorization for payments in Wise Business; all evidence covers account setup, transfers, and unrelated account-detail issues.

   ⚑ flag

Invoicing

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

   weight 2 · round drawn
   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

   Wise Business—none0/10

   Evidence covers receiving/sending money, multi-currency accounts, cards, and API payments, but nothing addresses creating or sending branded invoices with payment collection features.

   ⚑ flag

Money movement

1. founderSend money abroad that arrives in under a minute

   weight 2 · round to Wise Business
   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

   Wise Business~partialcommunity6/10

   Vendor docs explicitly claim most payments arrive in under 20 seconds and cover 40+ currencies/160+ countries, directly supporting the story. However, community evidence shows operational disruptions (account detail changes, account blocks) that undermine reliability of the payment experience, and there's no independent corroboration of actual speed claims. Missing for 10: independent/hands-on verification of the under-a-minute speed claim, and resolution of community reliability concerns.

   • [claimed-docs] “Send payments globally, in under 20 seconds”
   • [claimed-docs] “Most arrive in under 20 seconds.”
   • [claimed-docs] “Make payments and get paid in 40+ currencies.”
   • [community] “Due to an operational change, your USD account details for your Wise Business and Personal accounts are changing... From today, October 17, …”
   • [community] “Indie developer levelsio's Wise Business account—including incoming and outgoing transfers, cards, etc.—was completely blocked because his W…”

   proof ↗⚑ flag

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

   weight 1 · round to Wise Business
   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

   Wise Business~partialclaimed6/10

   Wise explicitly offers a rate lock ('Lock in exactly what your recipient will get for up to 24 hours') via wise-docs-8, directly matching the story, but this is a fixed 24-hour window rather than a flexible/finance-lead-configurable window, and there's no independent corroboration or API-level documentation of this feature for Business specifically. missing for 10: evidence of business-specific (vs. consumer) rate-lock terms, longer/configurable lock windows, and independent confirmation of reliability.

   • [claimed-docs] “Lock in exactly what your recipient will get for up to 24 hours. If the rate drops, you won’t lose out.”

   proof ↗⚑ flag

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

   weight 3 · round to Wise Business
   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

   Wise Business~partialcommunity5/10

   Wise Business docs confirm global/business payments via API and US bank account details (implying domestic transfers), but no explicit mention of ACH or wire transfer mechanics, batch vendor payments, or approval workflows for finance teams. Community reports also show real friction — sudden change of US account/routing details with no notice (wise-comm-3) and a business account being fully blocked over a category mismatch (wise-comm-6) — which undercuts reliability for ongoing vendor payments. missing for 10: explicit ACH/wire terminology, vendor batch-payment/approval workflow evidence, and confirmation that account-detail volatility doesn't disrupt recurring vendor payments.

   • [claimed-docs] “Send payments globally, in under 20 seconds”
   • [claimed-docs] “How to make business payments via API from a Wise account.”
   • [claimed-docs] “Make payments and get paid in 40+ currencies.”
   • [community] “Due to an operational change, your USD account details for your Wise Business and Personal accounts are changing... From today, October 17, …”
   • [community] “Indie developer levelsio's Wise Business account—including incoming and outgoing transfers, cards, etc.—was completely blocked because his W…”

   proof ↗⚑ flag

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

   weight 3 · round to Wise Business
   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

   Wise Business✓fullcommunity8/10

   Docs show international payments in 40+ currencies with rate lock guarantees and no hidden fees/markups, directly matching the finance-lead's need for transparent-fee international payments; community evidence corroborates it's used for real business payments (NET 30-90 terms) and is seen as reliable vs alternatives. Missing for 10: independent fee-transparency audits and more detail on actual fee schedules beyond marketing claims, plus account-detail-change incidents that add operational friction risk not solely about fee transparency.

   • [claimed-docs] “Send payments globally, in under 20 seconds”
   • [claimed-docs] “Most arrive in under 20 seconds.”
   • [claimed-docs] “Lock in exactly what your recipient will get for up to 24 hours. If the rate drops, you won’t lose out.”
   • [claimed-docs] “Pay and withdraw cash worldwide without any hidden fees or markups.”
   • [claimed-docs] “Make payments and get paid in 40+ currencies.”
   • [community] “I feel they are more reliable than PayPal.”
   • [community] “My business works with enterprises on NET 30 to NET 90 payment terms, so having account details change without warning is a painful one to c…”

   proof ↗⚑ flag

Multi currency

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

   weight 2 · round to Wise Business
   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

   Wise Business✓fullclaimed8/10

   Wise Business documentation clearly supports holding and receiving in 40+ currencies with global account details from one account, matching the founder story directly. Missing for 10: independent hands-on review of the multi-currency dashboard/balance management UI itself (community evidence cited relates to account-detail change notices, not to the core multi-currency holding capability).

   • [claimed-docs] “Receive payment in 40+ currencies”
   • [claimed-docs] “Get paid easily in other currencies with global account details.”
   • [claimed-docs] “Make payments and get paid in 40+ currencies.”
   • [claimed-docs] “Create accounts for 160+ countries”

   proof ↗⚑ flag

2. founderReceive payments using local account details in multiple currencies

   weight 2 · round to Wise Business
   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

   Wise Business!disputedcontradicted5/10

   Wise Business documents receiving payments via local account details in 40+ currencies/160+ countries (wise-docs-1,3,9,12), but concrete hands-on reports show these account details can change with zero notice, breaking real business payment flows with enterprise clients on NET30/90 terms (wise-comm-3, wise-comm-5), and one founder's entire business account was blocked due to a category mismatch (wise-comm-6). Missing for 10: independent verification of stability of account details over time, and resolution/track record after the reported incidents.

   • [claimed-docs] “Create accounts for 160+ countries”
   • [claimed-docs] “Receive payment in 40+ currencies”
   • [claimed-docs] “Get paid easily in other currencies with global account details.”
   • [claimed-docs] “Make payments and get paid in 40+ currencies.”
   • [community] “Due to an operational change, your USD account details for your Wise Business and Personal accounts are changing... From today, October 17, …”
   • [community] “My business works with enterprises on NET 30 to NET 90 payment terms, so having account details change without warning is a painful one to c…”
   • [community] “Indie developer levelsio's Wise Business account—including incoming and outgoing transfers, cards, etc.—was completely blocked because his W…”

   proof ↗⚑ 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
   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

   Wise Business—none0/10

   No evidence of a universal search bar across transactions, vendors, and cards, nor any UI navigation feature that lets a finance-lead jump from search results into initiating a payment. Evidence pack only covers payment sending, currency accounts, cards issuance, and unrelated account-closure complaints.

   ⚑ flag

Payment transparency

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

   weight 2 · round to Wise Business
   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

   Wise Business~partialclaimed3/10

   Wise advertises general speed ('most arrive in under 20 seconds') and a rate-lock guarantee, but there is no evidence of a specific, itemized delivery-time estimate shown per ACH/wire transfer before confirmation. missing for 10: concrete UI/API evidence of a per-transaction delivery estimate for ACH/wire, confirmation-screen screenshots or docs showing exact ETA, independent corroboration of estimate accuracy.

   • [claimed-docs] “Most arrive in under 20 seconds.”
   • [claimed-docs] “Lock in exactly what your recipient will get for up to 24 hours. If the rate drops, you won’t lose out.”

   proof ↗⚑ flag

Agent access

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

   weight 2 · round to Ramp
   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

   Wise Business✓fullprobed8/10

   A direct probe confirms llms.txt is live at docs.wise.com/llms.txt returning HTTP 200 with structured agent-oriented content describing the Global Payments API, showing an AI agent can be pointed at this file successfully. Missing for 10: independent/community confirmation of agents actually consuming it, and a discoverable OpenAPI spec (all candidate paths 404) to complement the llms.txt for deeper agentic use.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.wise.com/llms.txt # Global Payments API: Send & Receive Money > Wise Platform offer domestic and c…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.wise.com/openapi.json, https://docs.wise.com/swagger.json, https://docs.wise.com/api/op…”

   proof ↗⚑ flag

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

   weight 2 · round to Ramp
   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

   Wise Business~partialprobed4/10

   Wise documents an API for making business payments programmatically (wise-docs-6) and an llms.txt referencing a 'Global Payments API' (wise-probe-1), suggesting some headless/automation capability exists. However, no OpenAPI/swagger spec is discoverable at standard locations (wise-probe-2 shows 404s), and there is no explicit mention of CI integration, SDKs, webhooks, or automation-friendly tooling. Missing for 10: discoverable API spec, CI/CD examples, SDK/CLI tooling, and any explicit automation-focused documentation.

   • [claimed-docs] “How to make business payments via API from a Wise account.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.wise.com/llms.txt # Global Payments API: Send & Receive Money > Wise Platform offer domestic and c…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.wise.com/openapi.json, https://docs.wise.com/swagger.json, https://docs.wise.com/api/op…”

   proof ↗⚑ flag

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

   weight 3 · round to Ramp
   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

   Wise Business✓fullprobed7/10

   Wise publishes public API docs (docs.wise.com) explicitly covering account creation, global payments, and business payments via API, and the llms.txt probe confirms a 'Global Payments API' surface. Missing for 10: a discoverable OpenAPI/swagger spec (all probed endpoints 404'd) and independent developer corroboration of API usage/reliability.

   • [claimed-docs] “How to make business payments via API from a Wise account.”
   • [claimed-docs] “Create accounts for 160+ countries”
   • [claimed-docs] “Send payments globally, in under 20 seconds”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.wise.com/llms.txt # Global Payments API: Send & Receive Money > Wise Platform offer domestic and c…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.wise.com/openapi.json, https://docs.wise.com/swagger.json, https://docs.wise.com/api/op…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   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

   Wise Business—none0/10

   No evidence of scoped or least-privilege API credential issuance (e.g., token scoping, permission granularity, or per-agent API keys); docs mention API payments but nothing about credential scoping mechanisms, and OpenAPI/spec probes 404.

   • [claimed-docs] “How to make business payments via API from a Wise account.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.wise.com/openapi.json, https://docs.wise.com/swagger.json, https://docs.wise.com/api/op…”

   proof ↗⚑ flag

5. ai-native userBuild against official SDKs

   weight 2 · round to Ramp
   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

   Wise Business—none0/10

   Evidence shows Wise has business payment APIs and docs (wise-docs-6, wise-probe-1) but nothing about official SDKs/client libraries for developers; the OpenAPI spec itself 404s across all standard paths (wise-probe-2), suggesting even machine-readable API definitions aren't published, let alone language SDKs.

   • [claimed-docs] “How to make business payments via API from a Wise account.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.wise.com/llms.txt # Global Payments API: Send & Receive Money > Wise Platform offer domestic and c…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.wise.com/openapi.json, https://docs.wise.com/swagger.json, https://docs.wise.com/api/op…”

   proof ↗⚑ flag

6. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   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

   Wise Business—none0/10

   No evidence in the pack mentions webhooks or event subscription capabilities for Wise Business; the docs cover payments, accounts, and cards but nothing about webhook subscriptions or event-driven notifications.

   ⚑ flag

Api quality

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

   weight 2 · round drawn
   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

   Wise Business—none0/10

   No evidence of an interactive API reference with runnable examples; probes for OpenAPI/swagger specs all returned 404, and docs pack only lists feature descriptions, not interactive tooling.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.wise.com/openapi.json, https://docs.wise.com/swagger.json, https://docs.wise.com/api/op…”

   proof ↗⚑ flag

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

   weight 2 · round to Ramp
   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

   Wise Business—none0/10

   Wise Business exposes a documented API (payments, accounts, cards) so an OpenAPI-style machine-readable spec is a fair expectation, but direct probes for openapi.json/swagger.json and related paths all returned 404, and no evidence shows a downloadable spec elsewhere.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.wise.com/openapi.json, https://docs.wise.com/swagger.json, https://docs.wise.com/api/op…”
   • [claimed-docs] “How to make business payments via API from a Wise account.”

   proof ↗⚑ flag

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

   weight 1 · round drawn
   Ramp—none0/10

   No evidence of a sandbox/test environment for 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

   Wise Business—none0/10

   No evidence in the pack mentions a sandbox or test environment for Wise Business API testing; documentation focuses on live payment features, account creation, and API usage without any sandbox/test-mode reference. missing for 10: mention of sandbox environment, test API keys, or non-production testing mode.

   ⚑ flag

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

   weight 2 · round drawn
   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

   Wise Business—none0/10

   No evidence of API versioning scheme or a documented deprecation policy; OpenAPI spec probes all returned 404, and community evidence actually shows abrupt, undocumented breaking changes (bank account details changing with zero notice) rather than a managed deprecation process.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.wise.com/openapi.json, https://docs.wise.com/swagger.json, https://docs.wise.com/api/op…”
   • [community] “I received notification that my US bank account number will stop working immediately and I should not use it anywhere and remove it from any…”
   • [community] “Due to an operational change, your USD account details for your Wise Business and Personal accounts are changing... From today, October 17, …”
   • [community] “My business works with enterprises on NET 30 to NET 90 payment terms, so having account details change without warning is a painful one to c…”

   proof ↗⚑ flag

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

   weight 2 · round to Ramp
   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

   Wise Business—none0/10

   Evidence covers single-payment API and account features but nothing about batch/bulk payment operations, CSV uploads, or multi-item transaction processing that would support AI-native bulk automation.

   ⚑ flag

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

   weight 3 · round to Ramp
   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

   Wise Business—none0/10

   No evidence of any rules engine, event-trigger system, or automation/workflow configuration in Wise Business docs; evidence only covers payments, accounts, cards, and API basics, not event-driven automation.

   ⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Ramp
   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

   Wise Business—none0/10

   No evidence of scheduling recurring jobs/workflows or automation orchestration capability; the API docs only cover one-off payments, account creation, and currency exchange, with no mention of recurring/scheduled transfers or workflow automation.

   ⚑ flag

Card controls

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

   weight 2 · round to Ramp
   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

   Wise Business—none0/10

   No evidence of department/program budgeting or automated spend-limit enforcement in Wise Business docs; evidence covers payments, currency accounts, and card issuance only, with community reports focused on account-number changes and account blocks, not budget controls.

   ⚑ flag

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

   weight 3 · round to Ramp
   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

   Wise Business—none0/10

   Evidence pack only mentions issuing debit cards worldwide (wise-docs-4) but contains no documentation of per-card spend limits, granular employee-level controls, or admin card management features. No evidence supports this specific capability.

   ⚑ flag

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

   weight 2 · round drawn
   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

   Wise Business—none0/10

   Evidence shows Wise issues debit cards worldwide, but there is no mention of card freezing/locking or replacement-ordering functionality anywhere in the pack.

   • [claimed-docs] “Issue debit cards worldwide”

   proof ↗⚑ flag

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

   weight 1 · round drawn
   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

   Wise Business—none0/10

   No evidence of a self-service screen or workflow for requesting transaction limit increases; evidence covers account creation, payments, cards issuance, and unrelated community complaints about account detail changes and profile mismatches.

   ⚑ 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 Ramp
   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

   Wise Business—none0/10

   Evidence only mentions issuing debit cards worldwide (wise-docs-4) with no mention of virtual cards, spend controls, or scoping cards to a vendor/purpose — the specific capability finance leads need for scoped spend controls is absent.

   • [claimed-docs] “Issue debit cards worldwide”

   proof ↗⚑ flag

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

   weight 2 · round to Ramp
   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

   Wise Business~partialclaimed3/10

   Evidence only shows a thin claim that Wise lets businesses 'issue debit cards worldwide' with no detail on assigning employee roles, spending controls, or credit card issuance. missing for 10: evidence of credit card issuance, role-based permissions/spend controls per employee, and any independent corroboration of card issuance workflow.

   • [claimed-docs] “Issue debit cards worldwide”

   proof ↗⚑ flag

Card rewards

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

   weight 1 · round to Wise Business
   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

   Wise Business✓fullcommunity7/10

   Wise docs explicitly state cards can be issued worldwide and used to 'pay and withdraw cash worldwide without any hidden fees or markups,' directly matching the founder's story. Community evidence corroborates general reliability but doesn't specifically address card fee transparency, and there's no independent hands-on verification of the no-hidden-fee claim for card withdrawals abroad. Missing for 10: independent/hands-on confirmation of actual ATM withdrawal fees and card FX markup transparency in practice.

   • [claimed-docs] “Issue debit cards worldwide”
   • [claimed-docs] “Pay and withdraw cash worldwide without any hidden fees or markups.”
   • [community] “I feel they are more reliable than PayPal.”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   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

   Wise Business—none0/10

   No evidence anywhere in the pack of a cashback or rewards program for card spend; the evidence covers currency accounts, payments, and card issuance only.

   ⚑ 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
   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

   Wise Business—none0/10

   No evidence Wise offers receipt capture, OCR, or expense coding features tied to card transactions; documentation only covers accounts, payments, and card issuance, not receipt automation.

   • [claimed-docs] “Issue debit cards worldwide”
   • [claimed-docs] “How to make business payments via API from a Wise account.”

   proof ↗⚑ flag

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

   weight 2 · round to Ramp
   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

   Wise Business—none0/10

   No evidence pack items mention receipt capture, receipt attachment, email-in receipts, or expense/spend management matching features for Wise Business; evidence covers payments, accounts, cards issuance, and unrelated community complaints about account detail changes.

   ⚑ flag

Signup flow

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

   weight 1 · round drawn
   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

   Wise Business—none0/10

   No evidence in the pack describes an application status tracker or onboarding review dashboard for founders; evidence covers payments, currencies, cards, and unrelated account-closure/support issues.

   ⚑ flag

Switching

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

   weight 2 · round to Ramp
   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

   Wise Business~partialcommunity5/10

   Wise Business clearly consolidates banking (multi-currency accounts, global payment details), cards, and payment sending/API into one platform, which covers 'banking' and part of 'spend'. However, there is no evidence of dedicated bill-pay/AP automation or spend-management features (approvals, budgets, expense categorization) that founders would need to fully replace those point solutions, and community reports show operational friction (account detail changes, account blocks) that undercut a seamless 'one platform' story. Missing for 10: dedicated bill pay/invoicing workflow, spend management/approval controls, and independent evidence of reliability at scale.

   • [claimed-docs] “Create accounts for 160+ countries”
   • [claimed-docs] “Receive payment in 40+ currencies”
   • [claimed-docs] “Issue debit cards worldwide”
   • [claimed-docs] “How to make business payments via API from a Wise account.”
   • [claimed-docs] “Get paid easily in other currencies with global account details.”
   • [community] “Due to an operational change, your USD account details for your Wise Business and Personal accounts are changing... From today, October 17, …”
   • [community] “Indie developer levelsio's Wise Business account—including incoming and outgoing transfers, cards, etc.—was completely blocked because his W…”

   proof ↗⚑ flag

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

   weight 2 · round to Ramp
   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

   Wise Business—none0/10

   The evidence pack contains no claims or documentation about how long it takes a founder to open and fully activate a Wise Business account — no onboarding timeline, sign-up flow speed, or verification turnaround is mentioned. The only tangential items describe account creation breadth (160+ countries) and API payment docs, not onboarding speed, and community evidence instead highlights account blocks/changes (wise-comm-6, wise-comm-3) rather than fast onboarding.

   ⚑ flag

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

   weight 2 · round to Ramp
   Ramp~partialprobed6/10

   Ramp exposes a 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

   Wise Business~partialprobed5/10

   Docs show the API can create accounts, send/receive payments, and issue cards, mirroring several core UI capabilities (wise-docs-1..6), but there's no evidence of full parity — no OpenAPI/spec found (wise-probe-2 all 404), and UI-only features like rate locks, FDIC opt-in, or dispute/support workflows aren't shown as API-accessible. missing for 10: a published complete API reference/OpenAPI spec, explicit parity statement, coverage of rate-lock/insurance/account-management UI features via API, and independent confirmation of full functional overlap.

   • [claimed-docs] “Create accounts for 160+ countries”
   • [claimed-docs] “Send payments globally, in under 20 seconds”
   • [claimed-docs] “Receive payment in 40+ currencies”
   • [claimed-docs] “Issue debit cards worldwide”
   • [claimed-docs] “How to make business payments via API from a Wise account.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.wise.com/openapi.json, https://docs.wise.com/swagger.json, https://docs.wise.com/api/op…”

   proof ↗⚑ flag

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

   weight 3 · round to Ramp
   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

   Wise Business—none0/10

   No evidence of any data export/portability feature (transaction history, statements in open formats like CSV/JSON) or account-closure data-export process; evidence pack only covers payment features and API docs, with no mention of exporting or leaving with your data.

   ⚑ flag

1. ai-native userControl data retention and deletion

   weight 2 · round drawn
   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

   Wise Business—none0/10

   No evidence in the pack addresses data retention policies, deletion controls, or privacy/data-lifecycle management for Wise Business; all evidence covers payments, account features, and unrelated account-closure incidents.

   ⚑ flag

Access control

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

   weight 3 · round to Ramp
   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

   Wise Business—none0/10

   No evidence in the pack addresses role-based access control, permissions granularity, or team/location/department-level management; all evidence covers payments, currency accounts, and unrelated account-closure incidents.

   ⚑ flag

Fraud detection

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

   weight 2 · round to Ramp
   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

   Wise Business—none0/10

   No evidence of AI-driven anomaly detection or policy-based transaction flagging in Wise Business docs or community reports; evidence covers payments, cards, and account changes only. missing for 10: any AI/ML anomaly detection feature, policy rule engine, automated flagging or review workflow.

   ⚑ flag

Customer support

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

   weight 2 · round drawn
   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

   Wise Business—none0/10

   No evidence of live/24-7 customer support access; instead community reports describe support taking 30 days to respond to urgent account issues and accounts being blocked without quick resolution, suggesting no reliable live urgent support channel.

   • [community] “My business works with enterprises on NET 30 to NET 90 payment terms, so having account details change without warning is a painful one to c…”
   • [community] “Indie developer levelsio's Wise Business account—including incoming and outgoing transfers, cards, etc.—was completely blocked because his W…”

   proof ↗⚑ flag

Deposit protection

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

   weight 2 · round drawn
   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

   Wise Business—none0/10

   Wise only documents passthrough FDIC insurance up to $250,000 through a single named Program Bank, not an automated multi-bank sweep network that would extend coverage beyond that cap; no evidence of sweeping deposits across multiple partner banks.

   • [claimed-docs] “Opt in and get passthrough FDIC insurance up to $250,000 through our Program Bank.”

   proof ↗⚑ flag

Cash automation

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

   weight 2 · round to Ramp
   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

   Wise Business—none0/10

   No evidence of auto top-up between accounts or low-balance alert features; evidence covers multi-currency accounts, payments, cards, and rate locking but nothing about automated cash management/treasury alerting.

   ⚑ flag

Yield generation

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

   weight 3 · round drawn
   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

   Wise Business—none0/10

   No evidence in the pack mentions interest, yield, or return on operating cash balances held in Wise Business accounts; only FDIC pass-through insurance and payments/currency features are documented.

   • [claimed-docs] “Opt in and get passthrough FDIC insurance up to $250,000 through our Program Bank.”
   • [claimed-docs] “Create accounts for 160+ countries”
   • [claimed-docs] “Get paid easily in other currencies with global account details.”

   proof ↗⚑ flag

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

   weight 2 · round to Ramp
   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

   Wise Business—none0/10

   No evidence of a high-yield savings sub-account or automated transfer/sweep rules in Wise Business; evidence covers multi-currency accounts, payments, cards, and FDIC pass-through insurance only, not yield-generating savings or automation rules.

   ⚑ flag

3. founderEarn interest on balances held in multiple currencies

   weight 1 · round drawn
   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

   Wise Business—none0/10

   No evidence in the pack mentions interest-earning on multi-currency balances; only FDIC insurance passthrough and payment/transfer features are documented.

   ⚑ flag