/vendor/wise/AgentRouting.json or
/vendor/wise/AgentContext.json directly.
wise.com
Overview
Does wise.com support MCP?
No confirmed MCP support was found for wise.com as of 2026-06-28.
What agentic protocols does wise.com support?
As of 2026-06-28, wise.com has confirmed support for proprietary.
Is wise.com's API publicly accessible or partner-gated?
Access varies by protocol: open, partner only.
Does wise.com explicitly prohibit automated access?
No explicit prohibition on automated access was found in wise.com's terms of service.
Is wise.com agent-ready?
Partial. wise.com supports some agentic workflows but requires a human handoff for certain operations — see the protocols and summary sections for details.
Protocols
Two searches found no evidence of Wise (wise.com) appearing in any A2A launch partner list or integration announcement. Named launch partners include Atlassian, Box, Cohere, Intuit, Langchain, MongoDB, PayPal, Salesforce, SAP, ServiceNow, UKG, and Workday — Wise is absent from all available partner lists and documentation. No vendor-specific evidence of A2A adoption or plans was found.
No evidence found that Wise.com is a participant in the Agentic Commerce Protocol (OpenAI + Stripe). Known ACP launch partners include URBN (Anthropologie, Free People, Urban Outfitters), Coach, Kate Spade, Revolve, and Ashley Furniture — all retail/e-commerce merchants, consistent with ACP's current focus on physical goods checkout. Wise is a cross-border financial services company, not a retail merchant, and no Wise-specific ACP announcement, integration, or partner listing was found.
No evidence found of Wise (wise.com) participating in AP2 (Agent Payments Protocol) as a launch partner, contributor, or early adopter. The publicly named 60-organization contributor cohort from Google's FIDO Alliance donation announcement includes payment peers such as Revolut, PayPal, Adyen, Mastercard, and Worldpay, but Wise is not named. No Wise-specific AP2 documentation, integration announcement, or FIDO working group membership was found.
No official MCP server or Model Context Protocol integration was found in Wise's own developer documentation (docs.wise.com) or any Wise-authored announcement. All MCP-related findings are third-party community projects: an npm package (@kstam_wise/wise-mcp-server), and GitHub repos by 2060-io and sergeiledvanov, all of which wrap Wise's public REST API independently. These are unsanctioned integrations not authored or endorsed by Wise — their existence signals real agent demand against Wise's API, but they do not constitute a vendor-provided MCP surface.
No evidence found that Wise (wise.com) is a launch partner, adopter, or integration target for the Stripe + Tempo Machine Payments Protocol (MPP). Named MPP participants and ecosystem contributors at launch include Visa, Cloudflare, MultiversX, and Tempo itself — Wise does not appear among them. Wise operates its own independent multi-currency payment infrastructure and has no publicly documented connection to MPP.
No evidence found that wise.com has implemented NLWeb or appears in any NLWeb launch partner list. The only named early adopter surfaced across both searches was O'Reilly, which announced an explicit partnership with Microsoft for NLWeb integration. Wise.com operates in financial services, a sector with no named NLWeb participants found; no /ask or /mcp endpoints attributable to wise.com were discovered.
No evidence found that Wise (wise.com) has implemented or announced support for the Universal Commerce Protocol. UCP participants confirmed in public sources include Google, Shopify, Stripe, American Express, Mastercard, Best Buy, and Home Depot — Wise does not appear among them. Wise is a cross-border payments and financial services platform, not a merchant-of-record commerce vendor, which places it outside the typical UCP adoption profile for now.
No evidence found that wise.com has implemented or is a named participant in the WebMCP early preview program. WebMCP is a browser-layer protocol jointly developed by Google and Microsoft, currently in early preview/origin trial phase (Chrome 149+); known participants are discussed in Chrome developer documentation but wise.com does not appear among them. Search results returned infrastructure and editorial coverage (Chrome team, Cloudflare, Zuplo, Wix, Similarweb) with no mention of Wise.
No evidence that Wise (wise.com) has adopted or integrated the x402 HTTP 402 stablecoin micropayment protocol. Coinbase's x402 launch partners identified in public materials include Cloudflare, eco.com, and Sahara AI — Wise is not named. Wise's own developer documentation and newsroom focus exclusively on traditional fiat rails and its proprietary partner API, with no mention of x402 or stablecoin settlement.
No evidence found of Wise (wise.com) having built or submitted an app to OpenAI's ChatGPT Apps platform using the Apps SDK. Search results returned only third-party automation connectors (Pipedream, Zapier) linking Wise's own API to OpenAI's API — these are not ChatGPT Apps SDK integrations built by Wise. No Wise-authored listing was discoverable in the ChatGPT app store or on OpenAI's developer platform.
Business-facing REST API for self-serve automation of transfers, balance management, and payroll from a Wise business account — does not require a partnership agreement; sandbox available without verification
Wise exposes a documented REST API at docs.wise.com allowing businesses to automate payments, transfers, and standing orders directly from their Wise account. Authentication is via OAuth 2.0; a sandbox environment is freely available at sandbox.transferwise.tech. This is a self-serve tier distinct from the partner/embedded integration tier described below.
Embedded platform API for regulated banks, fintechs, and enterprise platforms to integrate Wise cross-border transfers, multi-currency accounts, and card issuance directly into their own products on behalf of their customers — requires direct partnership agreement and onboarding with Wise implementation team
Wise Platform's embedded API (docs.wise.com) is a separate, partner-gated surface distinct from the self-serve business API; access requires Wise to grant Developer Hub credentials before integration can begin. It covers transfers, balance management, card issuing, and incoming international transfers. Documentation is publicly readable but credentials require a direct partnership relationship.
No usable finding available for this protocol (no legitimate scan available within the candidate window).
Summary
Has agent interface: partial
Integrate directly with Wise's self-serve REST API (docs.wise.com) using OAuth 2.0 — a sandbox is freely available without a partnership agreement. Monitor Wise's developer blog and docs for any official MCP server release, given confirmed third-party community demand (npm package @kstam_wise/wise-mcp-server, GitHub repos by 2060-io and sergeiledvanov). For embedded or regulated-platform use cases, initiate a direct partnership conversation with Wise Platform.
AgentContext
Verified discrepancies
Vendor claim: Wise advertises specific, low fees and exchange rates at the point of initiating a transfer, including promotional claims that users can fund accounts and send money with no hidden fees.
What actually happens: The CFPB found that Wise failed to disclose accurate fees in multiple scenarios: users funding prepaid accounts via credit card through Apple Pay or Google Pay were charged undisclosed fees, exchange rates were inaccurately disclosed, fees were not refunded when funds were unavailable to recipients by the promised availability date, and ATM fee disclosures were deceptive and led to overcharges. These gaps mean the actual cost of a transaction can exceed what is shown at the point of initiation.
Agent guidance: When using Wise to complete a money transfer, do not rely solely on the fee and exchange-rate figures shown at the search or quote stage. Before confirming any transaction, explicitly verify the final all-in cost on the checkout/confirmation screen — paying particular attention to: (1) whether the funding method is a credit card via Apple Pay or Google Pay (historically a source of undisclosed surcharges), (2) the exact exchange rate applied at execution vs. the quoted rate, and (3) whether any ATM withdrawal fees are clearly itemized. If the confirmed total exceeds the quoted total, abort and surface the discrepancy to the user before proceeding.
- The CFPB's January 30, 2025 consent order found Wise guilty of deceptive marketing disclosures relating to ATM fees, failing to disclose accurate fees for credit-card-funded transfers via Apple Pay or Google Pay, and failing to properly disclose exchange rates — resulting in ~$450,000 in consumer redress and a civil penalty.
- The CFPB's press release on its amended May 2025 order confirms the original findings: Wise advertised inaccurate fees and failed to properly disclose exchange rates and other costs to consumers.
Vendor claim: Wise advertises that it offers transparent, mid-market exchange rates with no fees hidden in the rate, and that the fees and rates shown to customers are accurate and fully disclosed before a transfer is completed.
What actually happens: The U.S. Consumer Financial Protection Bureau (CFPB) issued a consent order against Wise in January 2025 (amended May 2025) finding that Wise advertised inaccurate fees and failed to properly disclose exchange rates and other costs to customers — meaning the rates and fees displayed did not accurately reflect what customers were actually charged at the time of the transaction.
Agent guidance: Do not rely on the exchange rate or fee amount displayed on Wise's pre-transfer confirmation screen as the final settled amount. After initiating a transfer, independently verify the actual debit from the funding source and the amount received by the recipient against what was quoted. If the figures diverge materially, treat the transaction as potentially mispriced and alert the user before considering it complete.
Vendor claim: Wise states in its terms and disclosures that when a remittance transfer is delayed or does not arrive on time, it will refund applicable transfer fees within the legally required timeframe, consistent with U.S. Remittance Transfer Rule obligations.
What actually happens: The CFPB found, via a January 30, 2025 consent order (amended May 15, 2025), that Wise failed to refund remittance fees within the required timeframe when transfers were delayed, and misled U.S. customers about ATM fees and exchange-rate-related costs. Wise was ordered to pay approximately $450,000 in redress to harmed consumers and a $2.025 million civil penalty.
Agent guidance: When initiating a Wise remittance transfer, do not rely on Wise's stated refund timeline for delayed transfers as automatically self-executing. If a transfer is delayed, explicitly submit a refund request through Wise's help center and document the submission timestamp. If the refund is not received within the legally required window (three business days under the U.S. Remittance Transfer Rule), escalate by filing a complaint with the CFPB before assuming Wise will process it automatically.
- The CFPB's January 2025 consent order found Wise failed to refund remittance fees on time for delayed transfers and misled consumers about ATM fees and other costs; the order was amended by the CFPB in May 2025.
- Banking Dive reports the CFPB fined Wise $2.5M, specifically noting it 'failed to refund remittance fees in the required timeframe after money customers sent did not arrive on time.'
Human handoff required for
Abort and escalate to a human when the all-in cost shown on the Wise checkout/confirmation screen materially exceeds the fee and exchange rate quoted at the initiation stage — particularly when the funding method is a credit card routed through Apple Pay or Google Pay, as this combination has been the documented source of undisclosed surcharges confirmed by the CFPB.
Escalate to a human when the actual debit amount from the funding source or the amount received by the recipient diverges materially from the exchange rate quoted at the pre-transfer confirmation stage — the CFPB confirmed that Wise's displayed rates did not always match the rates applied at execution.
Escalate to a human when a Wise remittance transfer is delayed and a fee refund has been requested but not received within three business days — Wise was found by the CFPB to have failed to refund remittance fees within the legally required timeframe, meaning automatic self-execution of refunds cannot be assumed.
Escalate to a human when a transaction involves an ATM withdrawal via a Wise card and the fee itemization on the confirmation screen is absent, ambiguous, or does not match the fee disclosed at the start of the flow — the CFPB found that Wise's ATM fee disclosures were deceptive and led to overcharges.
Five discrepancy categories were checked for Wise.com. Pricing discrepancies were confirmed via a CFPB consent order (January 2025, amended May 2025) establishing that Wise advertised inaccurate fees and exchange rates, with specific issues around Apple Pay/Google Pay credit-card funding and ATM fee disclosures. Availability discrepancies were also confirmed by the same CFPB action, which found that displayed exchange rates and fees did not accurately reflect amounts charged at execution. Policy discrepancies were confirmed by the same consent order, which found Wise failed to refund remittance transfer fees within legally required timeframes. Identity discrepancies (merchant-of-record ambiguity, counterparty confusion) were searched but no confirmed finding was found — Wise's role as card issuer and regulated e-money institution is documented and clear. Undisclosed constraints were searched but no confirmed finding was found — transfer limits and unsupported currency routes exist but are disclosed by Wise in its own Help Centre documentation. No scan was blocked; all five categories returned results, though independent re-verification of Wise's post-consent-order remediation has not been performed.