Plaid vs Mastercard Open Finance (Finicity)
Plaid wins · 17–10 (21 drawn)
Account linking — stories about account linking in this arenaAccount linking
Stories about account linking in this arena
Hosted flows
developerLet a user connect their bank with a drop-in hosted flow — create a session server-side, open the widget, and get back a token for the connected account — without building institution UI myself
weight 3 · round to PlaidPlaid Link is explicitly documented as the client-side hosted widget that lets users connect their bank without the developer building institution UI, paired with server-side session/token creation (public_token/access_token flow) shown in SDKs and Sandbox docs. missing for 10: no independent/hands-on developer report confirming the end-to-end token exchange experience, and no explicit token-exchange code snippet in this pack (only Sandbox/public_token creation and general Link description).
- [claimed-docs] “Plaid Link is the client-side component that your users will interact with in order to link their accounts to Plaid and allow you to access …”
- [claimed-docs] “You can customize parts of Link's flow straight from the Dashboard. You can preview your changes in real time and then publish them instantl…”
- [claimed-docs] “you can also create Items in Sandbox via the API, using a special Sandbox-only endpoint, /sandbox/public_token/create. This endpoint allows …”
- [claimed-docs] “The Plaid Sandbox is a free and fully-featured environment for application development and testing. All Plaid functionality of both the Plai…”
- [claimed-docs] “Let's test out running Plaid locally by cloning the Quickstart app. You'll need API keys, which you can receive by signing up in the Dashboa…”
- [github] “try { await plaidClient.transactionsSync(request); } catch (error) { const err = error.response.data; }”
The evidence only briefly references a 'Connect' mechanism for linking accounts ('link them to at least one account via Connect') but provides no detail on a hosted, drop-in widget, server-side session creation, or token retrieval flow that a developer would use to avoid building institution UI. Missing for 10: documentation of Connect widget UI, session token generation API, and end-to-end token exchange after linking.
- [claimed-docs] “link them to at least one account via Connect”
Oauth
developerConnections to major institutions use bank-hosted OAuth rather than screen-scraped credentials — the platform documents its OAuth coverage and how legacy credential flows are being retired
weight 2 · round drawnPlaidnone0/10The evidence pack contains no Plaid documentation describing OAuth coverage for institutions or a plan to retire legacy credential/screen-scraping flows; docs only describe Auth/Balance/Identity/Transactions products generically. Community evidence in fact describes Plaid using screen-scraped credentials and even mimicking bank login pages, reinforcing the absence of documented OAuth-first coverage.
- [community] “Plaid is terrible! Both Wells Fargo and Bank of America support API integration, but Plaid chooses to screen-scrape and does not work if you…”
- [community] “Slightly off topic... Privacy virtual card use Plaid... The integration was extremely questionable. They were faking the bank's login page. …”
- [community] “Teller does not use screen scraping. They reverse engineer each bank's mobile APIs — contrasted favorably against Plaid's approach in discus…”
- [claimed-docs] “Plaid Link is the client-side component that your users will interact with in order to link their accounts to Plaid and allow you to access …”
Mastercard Open Finance (Finicity)none0/10The evidence pack covers Connect/account-linking, webhooks, and API products but never mentions OAuth-based bank authentication coverage, connectivity method mix, or a documented plan/status for retiring screen-scraped credential flows. Without explicit documentation of OAuth coverage vs. legacy scraping, this specific developer-facing transparency claim is unevidenced.
- [claimed-docs] “link them to at least one account via Connect”
- [claimed-docs] “Webhooks allow you to receive real-time notifications when specific events occur, eliminating the need for constant polling.”
Repair
ops leadBroken connections are repairable — expired or revoked links surface as documented statuses, and users can re-authenticate in an update flow without starting over
weight 2 · round to PlaidPlaid's webhook docs mention that webhooks inform developers about 'changes to Plaid Items or the status of asynchronous processes' (plaid-docs-8), which touches on connection status changes, and Link (plaid-docs-5, plaid-docs-11) is the client-side re-linking component. However, the evidence pack never explicitly documents the specific re-authentication 'update mode' flow, named error statuses like ITEM_LOGIN_REQUIRED, or confirmation that re-auth avoids re-onboarding from scratch. Missing for 10: explicit documentation of update-mode Link flow, named broken-connection status codes/webhooks, and confirmation users don't restart the full linking process.
- [claimed-docs] “Plaid sends webhooks to programmatically inform you about changes to Plaid Items or the status of asynchronous processes.”
- [claimed-docs] “Plaid Link is the client-side component that your users will interact with in order to link their accounts to Plaid and allow you to access …”
- [claimed-docs] “You can customize parts of Link's flow straight from the Dashboard. You can preview your changes in real time and then publish them instantl…”
Mastercard Open Finance (Finicity)none0/10The evidence pack covers account data products, webhooks, onboarding, and testing personas, but nothing documents connection health statuses (expired/revoked), a re-authentication or 'update mode' flow, or any repair-without-restart mechanism for broken links. Missing for 10: documented connection status states (e.g., expired/revoked/error), an update/re-auth flow API or UI, and any evidence of preserving existing account links during re-auth.
- [claimed-docs] “Webhooks allow you to receive real-time notifications when specific events occur, eliminating the need for constant polling.”
- [claimed-docs] “link them to at least one account via Connect”
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
Agent access
ai-native userPoint an agent at llms.txt or agent-oriented docs
weight 2 · round to Mastercard Open Finance (Finicity)Plaid has a live llms.txt at plaid.com/llms.txt (HTTP 200) confirming basic agent-oriented discovery, but the content is minimal (a short description, not a full doc index), the /docs/.md and openapi.json probes 404 rather than exposing machine-readable docs, and there's no independent corroboration of agents actually consuming these successfully. missing for 10: richer llms.txt content indexing full doc set, working markdown/OpenAPI endpoints, independent/hands-on evidence of an agent successfully using these to navigate docs.
- [probe] “PROBE llms.txt: HTTP 200 at https://plaid.com/llms.txt # Plaid > Plaid helps all companies build fintech solutions by making it easy, safe …”
- [probe] “PROBE docs-md: HTTP 404 at https://plaid.com/docs/.md”
- [probe] “PROBE openapi: all candidate paths 404 (https://plaid.com/openapi.json, https://plaid.com/swagger.json, https://plaid.com/api/openapi.json, …”
A probe confirms llms.txt is live at developer.mastercard.com/llms.txt (HTTP 200), and Mastercard also documents an agent-oriented MCP toolkit with dynamic code generation for agents. Missing for 10: no independent third-party confirmation that agents actually consume this llms.txt effectively, and no explicit doc listing Open Finance-specific sections within it.
- [probe] “PROBE llms.txt: HTTP 200 at https://developer.mastercard.com/llms.txt # Mastercard Developers Mastercard Developers is a comprehensive API p…”
- [probe] “official MCP server documented at https://developer.mastercard.com/platform/documentation/agent-toolkit/mcp-overview/”
- [claimed-docs] “Dynamic Code Generation: Generate accurate, working code examples based on current API specifications”
- [claimed-docs] “I need to integrate Open Finance to verify account ownership and check balances for my fintech app”
ai-native userRun the product headlessly / in CI for automation
weight 2 · round drawnPlaid's Sandbox exposes a special API endpoint (/sandbox/public_token/create) that lets developers generate test Items and public tokens purely via API calls, without any UI, which supports scripted/headless testing suitable for CI (plaid-docs-14, plaid-docs-13). The Node SDK further demonstrates programmatic, promise-based server-side calls (plaid-gh-1, plaid-gh-2) that can run in automated pipelines. However, real (non-sandbox) account linking still requires the client-side Plaid Link UI component, so full production automation isn't headless, and no explicit CI/automation documentation or examples are provided. missing for 10: explicit CI/headless automation guide, confirmation that production flows can bypass Link UI, independent evidence of running Plaid in automated pipelines.
- [claimed-docs] “you can also create Items in Sandbox via the API, using a special Sandbox-only endpoint, /sandbox/public_token/create. This endpoint allows …”
- [claimed-docs] “The Plaid Sandbox is a free and fully-featured environment for application development and testing. All Plaid functionality of both the Plai…”
- [github] “try { await plaidClient.transactionsSync(request); } catch (error) { const err = error.response.data; }”
- [github] “All errors can now be caught using try/catch with async/await or through promise chaining.”
- [claimed-docs] “Let's test out running Plaid locally by cloning the Quickstart app. You'll need API keys, which you can receive by signing up in the Dashboa…”
As a pure REST API platform, Open Finance is inherently headless — it uses PartnerID/secret token auth (docs-10, docs-23), an OpenAPI spec with generated client libraries (mastercard-open-finance-gh-1), and a non-billable 'Test Drive' sandbox with scripted test personas (docs-24, docs-25) suitable for automated/CI testing. Missing for 10: no explicit CI/CD pipeline examples, no documented headless SDK/CLI runner, and no first-party guidance on automating the flow end-to-end in a build pipeline.
- [claimed-docs] “To create a token, you are required to provide the PartnerID along with the corresponding secret and appKey.”
- [claimed-docs] “Use your Partner ID and Secret with the following endpoint whenever you need to generate a new access token”
- [claimed-docs] “Test Drive is a non-billable, unlimited plan that provides access to all Open Finance API endpoints.”
- [claimed-docs] “we provide you with a set of testing personas. Each persona represents an example of a user who might use your app.”
- [github] “The test project generates an API client library from the API specification like you would do in a real application”
ai-native userConnect an agent via an official MCP server
weight 3 · round to Mastercard Open Finance (Finicity)Plaid documents an official 'Dashboard MCP server' hosted by Plaid providing Production diagnostics and analytics tools (debugging Items, Link conversion data, usage metrics), confirmed by both docs and a probe hit. However, this MCP server is scoped only to dashboard/analytics functions rather than full API/product access (Auth, Transactions, Identity, etc.), so an agent cannot use it to perform general Plaid operations via MCP. Missing for 10: MCP coverage of core Plaid API functionality (Auth, Transactions, Payments) and independent/community corroboration of real-world MCP usage.
- [claimed-docs] “The Dashboard MCP server is a remote MCP server hosted by Plaid. It provides Production diagnostics and analytics tools, including tools for…”
- [probe] “official MCP server documented at https://plaid.com/docs/resources/mcp/”
Mastercard documents an official Agent Toolkit MCP server (mcp-overview) that includes dynamic code generation and an example use case directly referencing Open Finance verification and balance checks, confirming AI agents can connect via this official MCP server to access Open Finance APIs. Missing for 10: independent/hands-on corroboration of the MCP server working with Open Finance endpoints, and detailed API-to-tool mapping documentation.
- [claimed-docs] “Dynamic Code Generation: Generate accurate, working code examples based on current API specifications”
- [claimed-docs] “I need to integrate Open Finance to verify account ownership and check balances for my fintech app”
- [probe] “official MCP server documented at https://developer.mastercard.com/platform/documentation/agent-toolkit/mcp-overview/”
ai-native userUse an official CLI
weight 2 · round drawnPlaidnone0/10Evidence shows Plaid SDKs (e.g., plaid-node), Quickstart apps, and a hosted MCP server, but no mention anywhere of an official CLI tool for interacting with Plaid's API or dashboard.
Mastercard Open Finance (Finicity)none0/10No evidence of an official CLI tool; evidence covers APIs, webhooks, MCP server, and SDK/test client generation but nothing describing a command-line interface for AI-native workflows. Missing for 10: any mention of an official CLI, its installation, or its use in agentic/AI workflows.
ai-native userDrive the product through a documented public API
weight 3 · round to Mastercard Open Finance (Finicity)Plaid provides extensive public API documentation (Auth, Balance, Identity, Transactions, Payment Initiation), SDKs (plaid-node), webhooks, and a Sandbox for programmatic testing, all of which let a developer (including an AI agent) drive the product via documented endpoints. However, there's no discoverable OpenAPI/Swagger spec (404s on all candidate paths) and no llms.txt-style machine-readable API map beyond a generic landing page, which limits pure agentic/machine-driven discovery. missing for 10: publicly discoverable OpenAPI/machine-readable spec, evidence of AI-agent-specific API tooling beyond the separate Dashboard MCP server.
- [claimed-docs] “Auth allows you to request a user's checking, savings, or cash management account and routing number, making it easy for you to initiate cre…”
- [claimed-docs] “Balance is Plaid's product for receiving real-time balance information. This data is commonly used to tell if an account has sufficient fund…”
- [claimed-docs] “Plaid's Identity product helps you verify users' identities by accessing information on file with their financial institution.”
- [claimed-docs] “Retrieve up to 24 months of transaction data and stay up-to-date with webhooks”
- [claimed-docs] “The Plaid Sandbox is a free and fully-featured environment for application development and testing... you can create an unlimited number of …”
- [claimed-docs] “Plaid sends webhooks to programmatically inform you about changes to Plaid Items or the status of asynchronous processes.”
- [claimed-docs] “you can also create Items in Sandbox via the API, using a special Sandbox-only endpoint, /sandbox/public_token/create. This endpoint allows …”
- [github] “try { await plaidClient.transactionsSync(request); } catch (error) { const err = error.response.data; }”
- [github] “All errors can now be caught using try/catch with async/await or through promise chaining.”
- [probe] “PROBE docs-md: HTTP 404 at https://plaid.com/docs/.md”
- [probe] “PROBE openapi: all candidate paths 404 (https://plaid.com/openapi.json, https://plaid.com/swagger.json, https://plaid.com/api/openapi.json, …”
Mastercard Open Finance exposes a well-documented public REST API (accounts, balances, transactions, ownership verification, webhooks) with OpenAPI spec, token-based auth, sandbox/test-drive access, and even an llms.txt plus official MCP toolkit for agent-driven access. missing for 10: independent third-party developer confirmation of API usability/reliability beyond vendor docs.
- [claimed-docs] “To create a token, you are required to provide the PartnerID along with the corresponding secret and appKey.”
- [claimed-docs] “Use your Partner ID and Secret with the following endpoint whenever you need to generate a new access token”
- [claimed-docs] “Test Drive is a non-billable, unlimited plan that provides access to all Open Finance API endpoints.”
- [github] “The test project generates an API client library from the API specification like you would do in a real application”
- [probe] “PROBE llms.txt: HTTP 200 at https://developer.mastercard.com/llms.txt # Mastercard Developers Mastercard Developers is a comprehensive API p…”
- [probe] “official MCP server documented at https://developer.mastercard.com/platform/documentation/agent-toolkit/mcp-overview/”
- [claimed-docs] “Dynamic Code Generation: Generate accurate, working code examples based on current API specifications”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · round drawnPlaidnone0/10Plaid's evidence covers products (Auth, Balance, Identity, Transactions), Sandbox testing, Link, and a read-only diagnostics MCP server, but nothing describes issuing scoped or least-privilege API credentials/tokens specifically for an agent or any granular permissioning model for AI-native use. Missing for 10: any documentation of scoped API keys, credential minimization, or agent-specific access tokens.
- [claimed-docs] “The Dashboard MCP server is a remote MCP server hosted by Plaid. It provides Production diagnostics and analytics tools, including tools for…”
- [claimed-docs] “Let's test out running Plaid locally by cloning the Quickstart app. You'll need API keys, which you can receive by signing up in the Dashboa…”
- [claimed-docs] “The Plaid Sandbox is a free and fully-featured environment for application development and testing... you can create an unlimited number of …”
Mastercard Open Finance (Finicity)none0/10Evidence shows PartnerID/secret/appKey token generation for API access (docs-10, docs-23) but no mention of scoped, least-privilege, or per-agent credential issuance — auth appears to be a single partner-level secret rather than granular scoped tokens for agents. Missing for 10: any documentation of scoped/limited-permission API keys, per-agent credential issuance, or role-based access control for agent use.
- [claimed-docs] “To create a token, you are required to provide the PartnerID along with the corresponding secret and appKey.”
- [claimed-docs] “Use your Partner ID and Secret with the following endpoint whenever you need to generate a new access token”
ai-native userBuild against official SDKs
weight 2 · round to PlaidPlaid ships an official Node.js SDK (plaid-node) with documented async/await error-handling patterns and a quickstart guide showing API-key based setup, which supports building integrations programmatically. However, the evidence pack only shows one language SDK, no explicit mention of other official SDKs (Python, Java, Go, etc.) or SDK features tailored to AI-native/agentic workflows, and no independent corroboration of SDK quality. missing for 10: evidence of multi-language official SDKs, AI-specific SDK tooling or agent integration guides, independent developer corroboration of SDK usability.
- [github] “try { await plaidClient.transactionsSync(request); } catch (error) { const err = error.response.data; }”
- [github] “All errors can now be caught using try/catch with async/await or through promise chaining.”
- [claimed-docs] “Let's test out running Plaid locally by cloning the Quickstart app. You'll need API keys, which you can receive by signing up in the Dashboa…”
The only relevant evidence is a GitHub repo showing an OpenAPI-generated client library used for testing, not a fully documented, officially published SDK across languages. Missing for 10: dedicated official SDK repositories/packages (e.g., npm, PyPI, Maven), SDK version support docs, and independent developer confirmation of SDK usability.
- [github] “The test project generates an API client library from the API specification like you would do in a real application”
ai-native userSubscribe to events via webhooks
weight 2 · round drawnPlaid documents a first-class webhooks system that notifies subscribers of Item/product state changes (e.g., new transactions), which any AI-native integration could consume just like a human-built app. Missing for 10: independent/hands-on corroboration of webhook reliability and any agent-specific guidance for consuming webhooks programmatically.
- [claimed-docs] “Plaid sends webhooks to programmatically inform you about changes to Plaid Items or the status of asynchronous processes.”
- [claimed-docs] “Retrieve up to 24 months of transaction data and stay up-to-date with webhooks”
Docs explicitly describe webhook support for real-time event notifications (avoiding polling) and a subscription-based OBWMS API letting developers subscribe to specific events. Missing for 10: concrete webhook payload/setup examples, independent/hands-on confirmation, and detail on programmatic subscription management via API/SDK.
- [claimed-docs] “Webhooks allow you to receive real-time notifications when specific events occur, eliminating the need for constant polling.”
- [claimed-docs] “OBWMS will provide a comprehensive API for managing real-time event notifications, enabling you to subscribe to specific events, ensuring yo…”
Agentic features
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · round drawnPlaidnone0/10No evidence that Plaid generates AI-driven insights or suggestions from a user's financial data; the closest item (Dashboard MCP server) only exposes diagnostics/analytics tools for developers, not AI-generated insights delivered to end users. Missing for 10: any AI/ML insight-generation feature, natural-language summarization of transactions/balances, or user-facing recommendation engine.
- [claimed-docs] “The Dashboard MCP server is a remote MCP server hosted by Plaid. It provides Production diagnostics and analytics tools, including tools for…”
Mastercard Open Finance (Finicity)none0/10The evidence shows Mastercard Open Finance exposes categorized financial data (transaction types, recurring transactions, spending, loan payments) via APIs, and a separate MCP agent toolkit for developers to generate code, but there is no evidence of AI-generated insights or suggestions surfaced to an end-user inside the product itself.
- [claimed-docs] “Insights into: * [Transaction types] * [Recurring transactions] * [Consumer spending] * [Loan payments]”
- [claimed-docs] “Dynamic Code Generation: Generate accurate, working code examples based on current API specifications”
- [claimed-docs] “I need to integrate Open Finance to verify account ownership and check balances for my fintech app”
ai-native userSet up automations that run autonomously in the background
weight 2 · round to PlaidPlaid provides webhooks and transactionsSync for asynchronous, background processing of financial data changes (docs-8, gh-1), which could underpin automations, but there is no evidence of any AI-native automation/agent orchestration capability, scheduling, or autonomous workflow builder — the Dashboard MCP server is limited to diagnostics/analytics, not automation setup. Missing for 10: explicit automation/agent framework, scheduling or trigger-action tooling, and any AI-native framing of background autonomy beyond generic webhooks.
- [claimed-docs] “Plaid sends webhooks to programmatically inform you about changes to Plaid Items or the status of asynchronous processes.”
- [github] “try { await plaidClient.transactionsSync(request); } catch (error) { const err = error.response.data; }”
- [claimed-docs] “The Dashboard MCP server is a remote MCP server hosted by Plaid. It provides Production diagnostics and analytics tools, including tools for…”
Mastercard Open Finance (Finicity)none0/10Evidence shows webhooks for event notifications and an MCP toolkit for code generation, but nothing about scheduling or configuring autonomous background automations/workflows that run without user intervention. Missing for 10: any documentation of scheduled/triggered automation setup, autonomous workflow orchestration, or agentic task execution running independently in the background.
- [claimed-docs] “Webhooks allow you to receive real-time notifications when specific events occur, eliminating the need for constant polling.”
- [claimed-docs] “OBWMS will provide a comprehensive API for managing real-time event notifications, enabling you to subscribe to specific events, ensuring yo…”
- [claimed-docs] “Dynamic Code Generation: Generate accurate, working code examples based on current API specifications”
ai-native userOperate the product with natural-language commands
weight 2 · round to Mastercard Open Finance (Finicity)Plaid documents an official 'Dashboard MCP server' that exposes diagnostics/analytics tools (debugging Items, Link conversion data, usage metrics) which an AI agent could invoke via natural language, but this only covers dashboard operations, not the core product functionality (Auth, Transactions, Identity, Payments) — there is no broader natural-language interface for operating Plaid's main capabilities. Missing for 10: NL control over core Plaid products (linking, transactions, payments), independent/hands-on confirmation of MCP usability, and any conversational agent interface beyond dashboard diagnostics.
- [claimed-docs] “The Dashboard MCP server is a remote MCP server hosted by Plaid. It provides Production diagnostics and analytics tools, including tools for…”
- [probe] “official MCP server documented at https://plaid.com/docs/resources/mcp/”
Mastercard offers an official Agent Toolkit/MCP server with dynamic code generation and natural-language-friendly API access (e.g., 'I need to integrate Open Finance to verify account ownership and check balances'), which supports operating the platform via AI-native/natural-language workflows. However, this is a developer-integration tool rather than end-user natural-language command execution over the product's core financial functions. missing for 10: evidence of an end-user-facing natural-language interface, broader coverage of MCP tool capabilities beyond code generation, and independent/hands-on validation of the MCP server's reliability.
- [claimed-docs] “Dynamic Code Generation: Generate accurate, working code examples based on current API specifications”
- [claimed-docs] “I need to integrate Open Finance to verify account ownership and check balances for my fintech app”
- [probe] “official MCP server documented at https://developer.mastercard.com/platform/documentation/agent-toolkit/mcp-overview/”
Api quality
ai-native userExplore an interactive API reference with runnable examples
weight 2 · round drawnPlaidnone0/10Evidence shows only static docs pages, a Quickstart sample app to clone locally, and a Sandbox test environment, but no interactive API reference (e.g., try-it console, embedded runnable code snippets) — probes for an OpenAPI spec and docs-as-markdown interactive surface both returned 404s, suggesting no such interactive reference exists.
- [claimed-docs] “Let's test out running Plaid locally by cloning the Quickstart app. You'll need API keys, which you can receive by signing up in the Dashboa…”
- [probe] “PROBE docs-md: HTTP 404 at https://plaid.com/docs/.md”
- [probe] “PROBE openapi: all candidate paths 404 (https://plaid.com/openapi.json, https://plaid.com/swagger.json, https://plaid.com/api/openapi.json, …”
Mastercard Open Finance (Finicity)none0/10The evidence shows extensive product/API documentation, an OpenAPI spec-driven test client, and a 'Test Drive' sandbox plan, but nothing describes an interactive API reference (e.g., Swagger/Postman-style try-it console) with runnable code examples in the docs portal itself.
- [claimed-docs] “Test Drive is a non-billable, unlimited plan that provides access to all Open Finance API endpoints.”
- [github] “The test project generates an API client library from the API specification like you would do in a real application”
- [claimed-docs] “we provide you with a set of testing personas”
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round to Mastercard Open Finance (Finicity)Plaidnone0/10Direct probes for OpenAPI/swagger spec files at standard paths all returned 404, and no documentation references a downloadable machine-readable API spec; only an llms.txt marketing page was found, not an OpenAPI/equivalent spec.
- [probe] “PROBE openapi: all candidate paths 404 (https://plaid.com/openapi.json, https://plaid.com/swagger.json, https://plaid.com/api/openapi.json, …”
- [probe] “PROBE docs-md: HTTP 404 at https://plaid.com/docs/.md”
- [probe] “PROBE llms.txt: HTTP 200 at https://plaid.com/llms.txt # Plaid > Plaid helps all companies build fintech solutions by making it easy, safe …”
A GitHub repo (open-banking-us-openapi) explicitly generates an API client library from a published OpenAPI specification, confirming a machine-readable spec is downloadable/usable, and Mastercard also exposes an llms.txt and MCP toolkit for machine-consumable API access. Missing for 10: no direct link/documentation showing a single canonical spec file download page or version history, and no independent third-party confirmation of spec completeness.
- [github] “The test project generates an API client library from the API specification like you would do in a real application”
- [probe] “PROBE llms.txt: HTTP 200 at https://developer.mastercard.com/llms.txt # Mastercard Developers Mastercard Developers is a comprehensive API p…”
- [probe] “official MCP server documented at https://developer.mastercard.com/platform/documentation/agent-toolkit/mcp-overview/”
- [claimed-docs] “Dynamic Code Generation: Generate accurate, working code examples based on current API specifications”
ai-native userTest against a sandbox environment without touching production data
weight 1 · round drawnPlaid provides a dedicated, fully-featured Sandbox environment supporting all API/Link functionality with unlimited test Items and test credentials, plus a special sandbox-only endpoint for programmatic Item creation, clearly separating test from production data. missing for 10: no independent/hands-on developer corroboration of sandbox fidelity, and no explicit mention of AI-agent-specific sandbox testing workflows.
- [claimed-docs] “The Plaid Sandbox is a free and fully-featured environment for application development and testing... you can create an unlimited number of …”
- [claimed-docs] “The Plaid Sandbox is a free and fully-featured environment for application development and testing. All Plaid functionality of both the Plai…”
- [claimed-docs] “you can also create Items in Sandbox via the API, using a special Sandbox-only endpoint, /sandbox/public_token/create. This endpoint allows …”
- [claimed-docs] “Let's test out running Plaid locally by cloning the Quickstart app. You'll need API keys, which you can receive by signing up in the Dashboa…”
Mastercard provides a dedicated non-billable 'Test Drive' plan with unlimited access to all Open Finance API endpoints plus documented testing personas representing example users, explicitly for sandbox-style integration testing without production data, and a GitHub sample project generating a client from the API spec for testing. missing for 10: independent/hands-on confirmation of full production-data isolation and details on sandbox data realism or limitations.
- [claimed-docs] “Test Drive is a non-billable, unlimited plan that provides access to all Open Finance API endpoints.”
- [claimed-docs] “we provide you with a set of testing personas”
- [claimed-docs] “we provide you with a set of testing personas. Each persona represents an example of a user who might use your app.”
- [github] “The test project generates an API client library from the API specification like you would do in a real application”
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round drawnPlaidnone0/10The evidence pack contains no documentation of API versioning scheme or a deprecation policy — no changelog, version headers, or sunset timeline are mentioned anywhere, only product feature docs (Auth, Balance, Identity, Transactions) and SDK error-handling snippets.
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
ai-native userPerform bulk operations across many items at once
weight 2 · round drawnPlaidnone0/10Plaid's docs describe per-Item operations (Auth, Balance, Identity, Transactions, sandbox item creation) and webhooks, but no evidence shows a bulk/batch API for operating across many Items simultaneously (e.g., no bulk sync, bulk webhook re-fire, or multi-item query endpoint documented).
Mastercard Open Finance (Finicity)none0/10No evidence describes batch/bulk endpoints or multi-item operations (e.g., submitting many account IDs or requests in a single call); documented APIs appear per-account/per-transaction oriented, and webhooks only address real-time single-event notifications, not bulk processing.
ai-native userDefine rules that trigger actions automatically on events
weight 3 · round to PlaidPlaid provides webhooks that notify developers of events (item changes, transaction updates, async completions), which can be used to build automated reactions, but there is no evidence of a declarative rules engine where an AI-native user defines 'if event X then action Y' logic directly within Plaid—developers must write their own handling code. Missing for 10: a native rule/condition-action builder, AI-triggered automation config, or no-code trigger definitions beyond raw webhook payloads.
- [claimed-docs] “Plaid sends webhooks to programmatically inform you about changes to Plaid Items or the status of asynchronous processes.”
- [claimed-docs] “Retrieve up to 24 months of transaction data and stay up-to-date with webhooks”
- [github] “try { await plaidClient.transactionsSync(request); } catch (error) { const err = error.response.data; }”
Mastercard Open Finance (Finicity)none0/10Webhooks provide event notifications but there is no evidence of user-definable rules or automated triggered actions based on those events; missing for 10: rule-definition engine, conditional logic, automated action execution tied to events.
- [claimed-docs] “Webhooks allow you to receive real-time notifications when specific events occur, eliminating the need for constant polling.”
- [claimed-docs] “OBWMS will provide a comprehensive API for managing real-time event notifications, enabling you to subscribe to specific events, ensuring yo…”
ai-native userSchedule recurring jobs or workflows
weight 2 · round drawnPlaidnone0/10The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)
Balance ownership — stories about balance ownership in this arenaBalance ownership
Stories about balance ownership in this arena
Ach details
developerObtain verified account and routing numbers (or tokenized equivalents) from a linked account to fund ACH or bank-debit payments without micro-deposits
weight 3 · round to PlaidPlaid Auth explicitly provides checking/savings/cash management account and routing numbers to initiate ACH/wire debits/credits without micro-deposits, and is paired with Balance and Identity for verification, with Sandbox/Link supporting full dev testing. missing for 10: no independent/hands-on corroboration of micro-deposit-free instant verification success rate, and no explicit mention of tokenized-equivalent output formats.
- [claimed-docs] “Auth allows you to request a user's checking, savings, or cash management account and routing number, making it easy for you to initiate cre…”
- [claimed-docs] “Balance is Plaid's product for receiving real-time balance information. This data is commonly used to tell if an account has sufficient fund…”
- [claimed-docs] “Plaid's Identity product helps you verify users' identities by accessing information on file with their financial institution.”
- [claimed-docs] “Plaid Link is the client-side component that your users will interact with in order to link their accounts to Plaid and allow you to access …”
- [claimed-docs] “The Plaid Sandbox is a free and fully-featured environment for application development and testing. All Plaid functionality of both the Plai…”
Mastercard's docs list dedicated 'Get ACH details' and 'Validate account details' products alongside account-ownership verification and balance checks, which together match the story of retrieving account/routing data and validating funding source without micro-deposits. However, the evidence pack only shows product titles/index links rather than detailed descriptions of the actual data returned (e.g., explicit account/routing number fields, tokenization format, or confirmation that validation replaces micro-deposits). Missing for 10: detailed API schema/response showing routing+account numbers or tokens, explicit statement that validation eliminates micro-deposit verification, and independent developer confirmation of real-world usage.
- [claimed-docs] “Get ACH details”
- [claimed-docs] “Get [ACH details]”
- [claimed-docs] “Validate account details”
- [claimed-docs] “Validate [account details]”
- [claimed-docs] “Retrieves account ownership details (name, address, email and phone - where available) from a connected account at a financial institution.”
- [claimed-docs] “you can send customer data to our match account ownership details endpoint to receive confidence scores comparing the provided data and the …”
Balances
developerFetch a real-time balance for a connected account before initiating a payment — a documented balance endpoint intended for NSF and risk checks
weight 3 · round to PlaidPlaid's Balance product is explicitly documented as a real-time balance endpoint used to check sufficient funds before using an account as a payment funding source, directly matching the NSF/risk-check use case. missing for 10: independent hands-on developer confirmation of the /accounts/balance/get endpoint behavior and no explicit mention of latency/SLA guarantees for pre-payment checks.
- [claimed-docs] “Balance is Plaid's product for receiving real-time balance information. This data is commonly used to tell if an account has sufficient fund…”
Docs explicitly describe an Account Balance service returning real-time or cached balance data from the connected FI, matching the NSF/risk-check use case, and MCP overview references verifying ownership and checking balances as a supported integration flow. Missing for 10: explicit request/response schema examples, independent/hands-on confirmation of real-time latency, and no direct mention of pre-payment NSF workflow tying balance check to payment initiation.
- [claimed-docs] “The Account Balance service provides real-time or cached bank account balance information from your customer's Financial Institution (FI).”
- [claimed-docs] “I need to integrate Open Finance to verify account ownership and check balances for my fintech app”
Ownership
ops leadRetrieve account-holder details — names, addresses, contact data on file at the bank — to match the account owner against my customer
weight 2 · round drawnPlaid's Identity product is explicitly documented to return name, phone, email, and mailing address on file with the account holder's financial institution, directly matching the ops-lead need to verify account-owner identity against a customer record. Missing for 10: no independent/hands-on corroboration of match-accuracy or match-rate quality, and no explicit description of a 'match' scoring feature (e.g., identity match API) beyond raw data retrieval.
- [claimed-docs] “Plaid's Identity product helps you verify users' identities by accessing information on file with their financial institution.”
- [claimed-docs] “Plaid's Identity product helps you verify users' identities by accessing information on file with their financial institution. Using Identit…”
Docs explicitly describe an Account Owner Verification service retrieving name, address, email and phone from the connected FI account, and a match-account-ownership endpoint that compares provided customer data against the bank's on-file details with confidence scores — directly matching the ops matching workflow. Missing for 10: independent/hands-on corroboration beyond vendor docs and more detail on data completeness/edge cases across FIs.
- [claimed-docs] “Retrieves account ownership details (name, address, email and phone - where available) from a connected account at a financial institution.”
- [claimed-docs] “you can send customer data to our match account ownership details endpoint to receive confidence scores comparing the provided data and the …”
- [claimed-docs] “I need to integrate Open Finance to verify account ownership and check balances for my fintech app”
Processor tokens
developerLinked accounts plug into my payment processor — documented integrations or token exchange that hand verified account credentials to third-party processors and platforms
weight 2 · round to PlaidPlaid's Auth product explicitly hands over verified account and routing numbers to enable third-party ACH/wire debits/credits, and Payment Initiation extends this to real-time European bank transfers without manual entry, with Balance/Identity supplementing verification data used by payment processors. This is documented as a core first-party capability (token exchange via Link → API access to account credentials for downstream money movement). missing for 10: named case studies/integrations with specific processors (e.g., Stripe), independent technical corroboration of the token-exchange flow beyond docs.
- [claimed-docs] “Auth allows you to request a user's checking, savings, or cash management account and routing number, making it easy for you to initiate cre…”
- [claimed-docs] “Balance is Plaid's product for receiving real-time balance information. This data is commonly used to tell if an account has sufficient fund…”
- [claimed-docs] “Plaid's European Payments suite enables your users to make real-time payments without manually entering their account details or leaving you…”
- [claimed-docs] “Plaid's European Payments suite enables your users to make real-time payments without manually entering their account details or leaving you…”
- [claimed-docs] “Plaid Link is the client-side component that your users will interact with in order to link their accounts to Plaid and allow you to access …”
Mastercard Open Finance provides account ownership verification, balance, ACH details, and account aggregation APIs accessible via token-based auth (PartnerID/secret) that developers can integrate into payment processing flows, and it supports Connect for account linking. However, the evidence does not document specific third-party payment processor/platform integration partnerships or an explicit token-exchange handoff mechanism to hand verified credentials to external processors — the story implies pre-built plug-and-play integrations rather than raw APIs a developer must wire up themselves. missing for 10: named third-party processor/platform integration partners, explicit token-exchange-to-processor handoff documentation, independent confirmation of such integrations working in production.
- [claimed-docs] “Retrieves account ownership details (name, address, email and phone - where available) from a connected account at a financial institution.”
- [claimed-docs] “The Account Balance service provides real-time or cached bank account balance information from your customer's Financial Institution (FI).”
- [claimed-docs] “Get ACH details”
- [claimed-docs] “To create a token, you are required to provide the PartnerID along with the corresponding secret and appKey.”
- [claimed-docs] “Use your Partner ID and Secret with the following endpoint whenever you need to generate a new access token”
- [claimed-docs] “link them to at least one account via Connect”
Banking agent access — stories about banking agent access in this arenaBanking agent access
Stories about banking agent access in this arena
Agent data
ai-native userThe data comes back agent-consumable — clean structured JSON, documented schemas, and enrichment an automated financial workflow can reason over without heuristic parsing
weight 2 · round to Mastercard Open Finance (Finicity)Plaid's docs describe structured JSON products (Auth, Balance, Identity, Transactions) with clear semantics and webhooks for async updates, and SDKs show typed request/response handling with try/catch error parsing, suggesting machine-consumable output. However, there's no evidence of a public OpenAPI/JSON-schema spec (probe explicitly found 404s for openapi.json/swagger.json), and no documentation of transaction enrichment/categorization features an agent could reason over without extra parsing logic. Missing for 10: published OpenAPI or JSON schema definitions, explicit enrichment/categorization documentation, and independent confirmation that outputs require no heuristic post-processing.
- [claimed-docs] “Auth allows you to request a user's checking, savings, or cash management account and routing number, making it easy for you to initiate cre…”
- [claimed-docs] “Balance is Plaid's product for receiving real-time balance information. This data is commonly used to tell if an account has sufficient fund…”
- [claimed-docs] “Retrieve up to 24 months of transaction data and stay up-to-date with webhooks”
- [claimed-docs] “Plaid sends webhooks to programmatically inform you about changes to Plaid Items or the status of asynchronous processes.”
- [github] “try { await plaidClient.transactionsSync(request); } catch (error) { const err = error.response.data; }”
- [github] “All errors can now be caught using try/catch with async/await or through promise chaining.”
- [probe] “PROBE openapi: all candidate paths 404 (https://plaid.com/openapi.json, https://plaid.com/swagger.json, https://plaid.com/api/openapi.json, …”
Mastercard Open Finance provides structured JSON APIs with documented schemas for account, transaction, balance, and enrichment data (transaction categorization, recurring transactions, spending insights), an OpenAPI spec with generated client libraries, and even an official MCP/agent-toolkit for AI consumption. However, evidence doesn't show explicit example JSON payloads or schema definitions in the pack, nor confirmation that enrichment fields are agent-optimized (e.g., no heuristic parsing needed) versus requiring developer interpretation. missing for 10: concrete JSON schema examples/response samples, explicit confirmation that enrichment output avoids downstream heuristic parsing, independent developer corroboration of agent-readiness.
- [claimed-docs] “The Transaction Data Services provide account transaction data.”
- [claimed-docs] “The account and transaction data elements returned from Account Aggregation and Transaction Data vary depending on the account type.”
- [claimed-docs] “Insights into: * [Transaction types] * [Recurring transactions] * [Consumer spending] * [Loan payments]”
- [github] “The test project generates an API client library from the API specification like you would do in a real application”
- [probe] “official MCP server documented at https://developer.mastercard.com/platform/documentation/agent-toolkit/mcp-overview/”
- [claimed-docs] “Dynamic Code Generation: Generate accurate, working code examples based on current API specifications”
Agent operations
ai-native userAn agent can operate the platform — create link sessions, retrieve balances and transactions, and manage connections through the API or an MCP surface with scoped credentials
weight 3 · round drawnPlaid's REST API comprehensively covers the core story — creating Link sessions (plaid-docs-5), retrieving balances (plaid-docs-2), pulling transactions (plaid-docs-4, plaid-gh-1), and managing connections/Items via webhooks (plaid-docs-8) — and SDKs like plaid-node make this scriptable by an agent. However, the only documented MCP surface is the Dashboard MCP server, which is scoped to Production diagnostics/analytics (debugging Items, Link conversion, usage metrics) rather than operational banking actions like initiating Link or pulling balances/transactions (plaid-docs-9, plaid-probe-4). Missing for 10: an MCP surface (or equivalent agent-native interface) that actually performs Link session creation/balance/transaction retrieval, and explicit documentation of scoped/limited credentials designed for autonomous agent use rather than server-side API keys.
- [claimed-docs] “Plaid Link is the client-side component that your users will interact with in order to link their accounts to Plaid and allow you to access …”
- [claimed-docs] “Balance is Plaid's product for receiving real-time balance information. This data is commonly used to tell if an account has sufficient fund…”
- [claimed-docs] “Retrieve up to 24 months of transaction data and stay up-to-date with webhooks”
- [claimed-docs] “Plaid sends webhooks to programmatically inform you about changes to Plaid Items or the status of asynchronous processes.”
- [github] “try { await plaidClient.transactionsSync(request); } catch (error) { const err = error.response.data; }”
- [claimed-docs] “The Dashboard MCP server is a remote MCP server hosted by Plaid. It provides Production diagnostics and analytics tools, including tools for…”
- [probe] “official MCP server documented at https://plaid.com/docs/resources/mcp/”
Mastercard's Open Finance APIs clearly support the core actions an agent would need — creating link sessions via Connect, retrieving balances (Account Balance service), pulling transactions (Transaction Data), and managing connections/webhooks — all gated by PartnerID/secret/appKey OAuth tokens that function as scoped credentials. There is also a documented official MCP surface (agent-toolkit/mcp-overview) explicitly referencing Open Finance use cases like verifying ownership and checking balances, but its documented function is 'dynamic code generation' for developers rather than confirmed direct agentic execution of live account operations. missing for 10: evidence the MCP server itself executes link-session/balance/transaction calls (vs. just generating code samples), and independent/hands-on confirmation of an agent operating end-to-end with scoped MCP credentials.
- [claimed-docs] “The Account Balance service provides real-time or cached bank account balance information from your customer's Financial Institution (FI).”
- [claimed-docs] “The Transaction Data Services provide account transaction data.”
- [claimed-docs] “Webhooks allow you to receive real-time notifications when specific events occur, eliminating the need for constant polling.”
- [claimed-docs] “To create a token, you are required to provide the PartnerID along with the corresponding secret and appKey.”
- [claimed-docs] “Use your Partner ID and Secret with the following endpoint whenever you need to generate a new access token”
- [claimed-docs] “link them to at least one account via Connect”
- [claimed-docs] “Dynamic Code Generation: Generate accurate, working code examples based on current API specifications”
- [claimed-docs] “I need to integrate Open Finance to verify account ownership and check balances for my fintech app”
- [probe] “official MCP server documented at https://developer.mastercard.com/platform/documentation/agent-toolkit/mcp-overview/”
Consent security — stories about consent security in this arenaConsent security
Stories about consent security in this arena
Consent
ops leadEnd users can see and revoke what they've shared — a documented consent surface or portal where a user manages which apps hold access to their bank data
weight 2 · round drawnPlaidnone0/10The evidence pack contains no documentation of a Plaid-hosted consent management portal or dashboard where end users can view or revoke connected apps' access to their bank data; Plaid Link (docs-5) only covers the initial linking/consent flow, not ongoing management or revocation. Community comments even show a user explicitly asking how to revoke Plaid's access with no clear answer, reinforcing the absence of a documented self-service revocation surface.
- [claimed-docs] “Plaid Link is the client-side component that your users will interact with in order to link their accounts to Plaid and allow you to access …”
- [community] “I gave them access to my bank via coinbase. If I change my bank password would they lose access to my account? If not, what do I need to do …”
Mastercard Open Finance (Finicity)none0/10Evidence pack covers data retrieval, verification, transaction data, webhooks, onboarding tokens, and testing personas, but nowhere documents an end-user-facing consent management portal, dashboard, or revocation mechanism for shared bank-data access. No mention of a consent surface for users to view or revoke connected apps' access.
Deletion
ops leadSever and clean up — a documented way to delete a connection or user and have the platform stop collecting and purge held data
weight 2 · round drawnPlaidnone0/10The evidence pack contains no documentation of an item/access-token deletion endpoint, account disconnection flow, or data purge/retention policy — only product feature docs (Auth, Balance, Identity, Transactions) and Sandbox/dashboard mentions. A community comment even shows a user asking how to revoke Plaid's bank access with no clear answer surfaced, reinforcing the absence of a documented sever-and-purge mechanism in the pack.
- [community] “I gave them access to my bank via coinbase. If I change my bank password would they lose access to my account? If not, what do I need to do …”
- [claimed-docs] “Retrieve up to 24 months of transaction data and stay up-to-date with webhooks”
- [claimed-docs] “Plaid sends webhooks to programmatically inform you about changes to Plaid Items or the status of asynchronous processes.”
Scopes
developerI request only the data scopes I need — product-scoped consents and documented data-minimization controls, not an all-or-nothing grant
weight 2 · round to Mastercard Open Finance (Finicity)Plaiddisputedcontradicted4/10Plaid's docs show genuinely separate, scopeable products (Auth, Balance, Identity, Transactions, Payment Initiation) that a developer can choose to request individually rather than one monolithic grant, which supports a product-scoped consent model. However, independent/community reports concretely contradict the 'data-minimization by design' claim: users report Plaid flows give 'no indication... you're likely giving away much more than just the bare minimum' and that dark patterns lead to over-broad grants (transaction, identity, balance data) beyond what the integrating app needs. Missing for 10: first-party documentation of a scoped-consent UI/permission screen, independent audit confirming least-privilege enforcement, and no rebuttal to the dark-pattern complaints.
- [claimed-docs] “Auth allows you to request a user's checking, savings, or cash management account and routing number, making it easy for you to initiate cre…”
- [claimed-docs] “Balance is Plaid's product for receiving real-time balance information. This data is commonly used to tell if an account has sufficient fund…”
- [claimed-docs] “Plaid's Identity product helps you verify users' identities by accessing information on file with their financial institution.”
- [claimed-docs] “Retrieve up to 24 months of transaction data and stay up-to-date with webhooks”
- [claimed-docs] “Plaid's European Payments suite enables your users to make real-time payments without manually entering their account details or leaving you…”
- [community] “Have to say I'm not a fan of Plaid at all. Dark patterns galore. Absolutely no indication when you go through a Plaid flow that you're likel…”
- [community] “Plaid is a terrible company. Their main product scrapes financial data from unsuspecting users that simply think they're making a bank trans…”
The docs show a product-based API structure (separate endpoints for account ownership, balance, transactions, ACH, etc.), which implicitly allows requesting only specific data products rather than a single blob, but there is no explicit documentation of scoped consent tokens, granular permission grants, or data-minimization controls presented to developers. missing for 10: explicit consent-scoping API/parameters, documentation of minimal-data-grant mechanisms, evidence of per-scope authorization tokens, and any independent confirmation of data-minimization enforcement.
- [claimed-docs] “Retrieves account ownership details (name, address, email and phone - where available) from a connected account at a financial institution.”
- [claimed-docs] “The Account Balance service provides real-time or cached bank account balance information from your customer's Financial Institution (FI).”
- [claimed-docs] “The Transaction Data Services provide account transaction data.”
- [claimed-docs] “The account and transaction data elements returned from Account Aggregation and Transaction Data vary depending on the account type.”
- [claimed-docs] “[Account] and [transaction] details”
Data freshness — stories about data freshness in this arenaData freshness
Stories about data freshness in this arena
Refresh
developerTrigger an on-demand refresh of a connected account's data through the API when my use case needs now-fresh data, with the refresh semantics documented
weight 2 · round to PlaidThe evidence shows Plaid supports webhook-based updates (plaid-docs-8, plaid-docs-4) and an API-driven `transactionsSync` call (plaid-gh-1, plaid-gh-2) that developers can invoke to pull current data, which is adjacent to an on-demand refresh trigger, but the pack never cites Plaid's dedicated refresh endpoint (e.g. /transactions/refresh) or documents its specific semantics (timing, cost, which products support it). Missing for 10: explicit documentation of a refresh-on-demand endpoint and its semantics, confirmation of which products it applies to, and any independent/hands-on confirmation of its behavior.
- [claimed-docs] “Plaid sends webhooks to programmatically inform you about changes to Plaid Items or the status of asynchronous processes.”
- [claimed-docs] “Retrieve up to 24 months of transaction data and stay up-to-date with webhooks”
- [github] “try { await plaidClient.transactionsSync(request); } catch (error) { const err = error.response.data; }”
- [github] “All errors can now be caught using try/catch with async/await or through promise chaining.”
Mastercard Open Finance (Finicity)none0/10Evidence shows account balance can be 'real-time or cached' and webhooks provide event notifications, but there is no documented API endpoint or explicit refresh semantics (e.g., a force-refresh trigger, freshness guarantees, or polling-for-refresh-status flow) for triggering an on-demand data refresh. Missing for 10: an explicit refresh/force-update endpoint, documented refresh semantics (sync vs async, staleness thresholds), and any independent confirmation of on-demand refresh behavior.
- [claimed-docs] “The Account Balance service provides real-time or cached bank account balance information from your customer's Financial Institution (FI).”
- [claimed-docs] “Webhooks allow you to receive real-time notifications when specific events occur, eliminating the need for constant polling.”
- [claimed-docs] “The Transaction Data Services provide account transaction data.”
Webhooks
developerData changes arrive as signed webhooks — new transactions, balance updates, connection state changes — so my system stays current without polling
weight 2 · round to PlaidPlaid's docs explicitly describe webhooks for transactions, balance, and Item/connection state changes to keep systems updated without polling, and this is a well-documented core mechanism (plaid-docs-4, plaid-docs-8) reinforced by SDK error-handling examples showing transactionsSync usage in conjunction with webhooks (plaid-gh-1). No evidence indicates webhook signing/verification is missing or broken. Missing for 10: explicit mention of webhook signature verification mechanics and independent third-party confirmation of webhook reliability in production.
- [claimed-docs] “Retrieve up to 24 months of transaction data and stay up-to-date with webhooks”
- [claimed-docs] “Plaid sends webhooks to programmatically inform you about changes to Plaid Items or the status of asynchronous processes.”
- [github] “try { await plaidClient.transactionsSync(request); } catch (error) { const err = error.response.data; }”
Docs confirm webhooks exist for real-time event notifications instead of polling, and OBWMS lets you subscribe to specific events; transaction/notification-type docs exist too. However, there's no evidence of webhook payload signing/verification, and no explicit documentation enumerating events like balance updates or connection-state changes with delivery guarantees. Missing for 10: signature verification mechanism, explicit event-type catalog (transactions/balances/connection state), delivery retry/reliability details.
- [claimed-docs] “Webhooks allow you to receive real-time notifications when specific events occur, eliminating the need for constant polling.”
- [claimed-docs] “OBWMS will provide a comprehensive API for managing real-time event notifications, enabling you to subscribe to specific events, ensuring yo…”
- [claimed-docs] “[Transaction notifications]”
Institution coverage — stories about institution coverage in this arenaInstitution coverage
Stories about institution coverage in this arena
Coverage
founderThe platform documents how many institutions it reaches and where — published coverage numbers and geographies I can check against where my users actually bank
weight 3 · round to PlaidThe pack shows only a narrow geography claim (payment-initiation supports '18 European markets') but no overall institution count or country-by-country coverage list that a founder could check against user banks. missing for 10: published total institution count, per-country/region coverage breakdown, and any independent verification of coverage claims.
- [claimed-docs] “Plaid's European Payments suite enables your users to make real-time payments without manually entering their account details or leaving you…”
Mastercard Open Finance (Finicity)none0/10The evidence pack covers API capabilities (verification, balances, transaction data, webhooks, onboarding) but contains no published institution-coverage numbers, geographic breakdowns, or bank-reach statistics that a founder could check against their users' banks.
Status
ops leadPer-institution health is visible — documented institution statuses, outage or degradation signals, and error codes that distinguish a bank problem from my problem
weight 2 · round to PlaidPlaid documents webhooks for Item status changes and SDK-level error handling, and offers a Dashboard MCP server with 'diagnostics tools' for debugging Items, which supports some institution-health visibility. However, there is no evidence of a documented institution-status/error-code taxonomy (e.g., distinguishing bank outages from integration errors) or a public status page for individual institutions. Missing for 10: documented per-institution error code list distinguishing bank vs. client errors, an institution status/outage dashboard or feed, and independent confirmation these diagnostics reliably surface bank-side outages.
- [claimed-docs] “Plaid sends webhooks to programmatically inform you about changes to Plaid Items or the status of asynchronous processes.”
- [github] “try { await plaidClient.transactionsSync(request); } catch (error) { const err = error.response.data; }”
- [github] “All errors can now be caught using try/catch with async/await or through promise chaining.”
- [claimed-docs] “The Dashboard MCP server is a remote MCP server hosted by Plaid. It provides Production diagnostics and analytics tools, including tools for…”
- [probe] “official MCP server documented at https://plaid.com/docs/resources/mcp/”
Mastercard Open Finance (Finicity)none0/10The evidence pack covers API products (balance, ownership, transaction data, webhooks, onboarding) but contains no mention of institution status dashboards, outage/degradation signals, or error codes distinguishing bank-side vs integration-side issues.
Integration dx — sandboxes, test modes, webhooks, and how fast a developer gets to a working integrationIntegration dx
Sandboxes, test modes, webhooks, and how fast a developer gets to a working integration
Multi product
developerOne link session can power multiple data products — auth, balances, transactions, identity — without forcing the user through separate connection flows per product
weight 2 · round to PlaidPlaid's sandbox docs explicitly mention creating an Item with 'initial products' (plural) via a single public_token, implying one Link-created Item can be enabled for multiple products (auth, balance, identity, transactions) at once rather than separate connections. However, the evidence pack never explicitly confirms a single Link session UX flow surfacing multiple products to the end user in one consent step. Missing for 10: an explicit doc/example showing a single Link token configured with products=['auth','balances','transactions','identity'] and the resulting single end-user consent flow, plus independent/hands-on confirmation.
- [claimed-docs] “you can also create Items in Sandbox via the API, using a special Sandbox-only endpoint, /sandbox/public_token/create. This endpoint allows …”
- [claimed-docs] “Plaid Link is the client-side component that your users will interact with in order to link their accounts to Plaid and allow you to access …”
- [claimed-docs] “Auth allows you to request a user's checking, savings, or cash management account and routing number, making it easy for you to initiate cre…”
- [claimed-docs] “Balance is Plaid's product for receiving real-time balance information. This data is commonly used to tell if an account has sufficient fund…”
- [claimed-docs] “Plaid's Identity product helps you verify users' identities by accessing information on file with their financial institution.”
- [claimed-docs] “Retrieve up to 24 months of transaction data and stay up-to-date with webhooks”
Mastercard Open Finance (Finicity)none0/10The evidence lists multiple separate data products (account ownership, balances, transactions) and mentions a generic 'Connect' linking step, but nothing describes a single link/Connect session simultaneously provisioning auth, balances, transactions, and identity without repeated connection flows per product.
Quickstart
developerGo from signup to my first linked sandbox account fast — self-serve API keys, a runnable quickstart, and client libraries in my language
weight 2 · round to PlaidDocs show self-serve signup via Dashboard for API keys, a runnable Quickstart app, a fully-featured free Sandbox environment supporting all products, and a Node client library with async/await error handling. However, there's no explicit evidence of the breadth of client libraries across multiple languages, no independent hands-on confirmation of quickstart speed/ease, and no OpenAPI spec discoverable via probes. missing for 10: multi-language client library coverage evidence, independent/hands-on time-to-first-linked-account confirmation, public OpenAPI/API reference spec.
- [claimed-docs] “The Plaid Sandbox is a free and fully-featured environment for application development and testing... you can create an unlimited number of …”
- [claimed-docs] “Let's test out running Plaid locally by cloning the Quickstart app. You'll need API keys, which you can receive by signing up in the Dashboa…”
- [claimed-docs] “The Plaid Sandbox is a free and fully-featured environment for application development and testing. All Plaid functionality of both the Plai…”
- [claimed-docs] “you can also create Items in Sandbox via the API, using a special Sandbox-only endpoint, /sandbox/public_token/create. This endpoint allows …”
- [github] “try { await plaidClient.transactionsSync(request); } catch (error) { const err = error.response.data; }”
- [github] “All errors can now be caught using try/catch with async/await or through promise chaining.”
- [probe] “PROBE openapi: all candidate paths 404 (https://plaid.com/openapi.json, https://plaid.com/swagger.json, https://plaid.com/api/openapi.json, …”
Docs show a self-serve-ish onboarding path (PartnerID/secret/appKey token generation, a non-billable unlimited 'Test Drive' plan, and test personas for sandbox account linking) and a GitHub OpenAPI spec that can generate a client library, but there's no explicit runnable quickstart tutorial or multi-language official client libraries beyond the one generated test project. Missing for 10: an explicit step-by-step quickstart guide, published official SDKs in multiple languages, and clear evidence of instant self-serve API key issuance without a sales/partner approval step.
- [claimed-docs] “To create a token, you are required to provide the PartnerID along with the corresponding secret and appKey.”
- [claimed-docs] “Use your Partner ID and Secret with the following endpoint whenever you need to generate a new access token”
- [claimed-docs] “Test Drive is a non-billable, unlimited plan that provides access to all Open Finance API endpoints.”
- [claimed-docs] “we provide you with a set of testing personas. Each persona represents an example of a user who might use your app.”
- [github] “The test project generates an API client library from the API specification like you would do in a real application”
Sandbox
developerA sandbox with test institutions and documented test credentials lets me exercise linking, data retrieval, and error states end-to-end before touching a real bank account
weight 3 · round to PlaidPlaid's Sandbox docs describe a free, fully-featured test environment supporting all API and Link functionality, unlimited test Items, a special sandbox-only endpoint to create Items with arbitrary institution IDs and test credentials, and SDK error-handling examples for exercising error states end-to-end. This directly matches the story's need to test linking, data retrieval, and error flows before touching real accounts. Missing for 10: independent/hands-on developer corroboration of the sandbox experience beyond first-party docs.
- [claimed-docs] “The Plaid Sandbox is a free and fully-featured environment for application development and testing... you can create an unlimited number of …”
- [claimed-docs] “The Plaid Sandbox is a free and fully-featured environment for application development and testing. All Plaid functionality of both the Plai…”
- [claimed-docs] “you can also create Items in Sandbox via the API, using a special Sandbox-only endpoint, /sandbox/public_token/create. This endpoint allows …”
- [github] “try { await plaidClient.transactionsSync(request); } catch (error) { const err = error.response.data; }”
- [github] “All errors can now be caught using try/catch with async/await or through promise chaining.”
- [claimed-docs] “Plaid Link is the client-side component that your users will interact with in order to link their accounts to Plaid and allow you to access …”
Docs confirm a dedicated Test Drive sandbox with unlimited access to all endpoints, testing personas representing different user scenarios, and a GitHub sample project generating a real API client for end-to-end testing — covering linking, data retrieval, and onboarding tokens. However, there is no explicit documentation of error-state simulation or a catalog of documented test credentials/institutions with specific failure scenarios. Missing for 10: explicit documented test credentials list, coverage of error/failure state simulation, and independent/hands-on confirmation of the sandbox experience.
- [claimed-docs] “we provide you with a set of testing personas”
- [claimed-docs] “Test Drive is a non-billable, unlimited plan that provides access to all Open Finance API endpoints.”
- [claimed-docs] “we provide you with a set of testing personas. Each persona represents an example of a user who might use your app.”
- [github] “The test project generates an API client library from the API specification like you would do in a real application”
- [claimed-docs] “link them to at least one account via Connect”
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
ai-native userDo everything through the API that I can do in the UI
weight 2 · round to Mastercard Open Finance (Finicity)Plaid is API-first for core financial data products, and Sandbox Items can be created via API instead of the Dashboard UI (plaid-docs-14), suggesting some UI/API parity. However, the docs explicitly describe Dashboard-only actions like customizing and publishing Link's flow (plaid-docs-11) and signing up for API keys (plaid-docs-10) with no corresponding API endpoint shown, and there's no OpenAPI spec or full endpoint catalog to confirm total parity (plaid-probe-3). Missing for 10: evidence that Dashboard-only settings (Link customization, key management, analytics) have API equivalents, and independent confirmation of full UI/API feature parity.
- [claimed-docs] “You can customize parts of Link's flow straight from the Dashboard. You can preview your changes in real time and then publish them instantl…”
- [claimed-docs] “you can also create Items in Sandbox via the API, using a special Sandbox-only endpoint, /sandbox/public_token/create. This endpoint allows …”
- [claimed-docs] “Let's test out running Plaid locally by cloning the Quickstart app. You'll need API keys, which you can receive by signing up in the Dashboa…”
- [probe] “PROBE openapi: all candidate paths 404 (https://plaid.com/openapi.json, https://plaid.com/swagger.json, https://plaid.com/api/openapi.json, …”
As an API-first data platform, virtually all core functions (account verification, balances, transactions, ACH details, webhooks/event management, token generation) are exposed directly via documented REST APIs rather than gated behind a UI, and even administrative functions like webhook subscriptions and token creation are API-driven (docs-9, docs-23, docs-26). However, the 'Connect' account-linking flow is a hosted widget/UI experience (docs-27) whose full API-equivalence isn't evidenced, and there's no explicit confirmation that all developer-portal/dashboard actions (billing, partner management) have API parity. Missing for 10: explicit API equivalents for the Connect linking UI, and confirmation that portal/dashboard admin tasks are fully scriptable.
- [claimed-docs] “Webhooks allow you to receive real-time notifications when specific events occur, eliminating the need for constant polling.”
- [claimed-docs] “Use your Partner ID and Secret with the following endpoint whenever you need to generate a new access token”
- [claimed-docs] “OBWMS will provide a comprehensive API for managing real-time event notifications, enabling you to subscribe to specific events, ensuring yo…”
- [claimed-docs] “link them to at least one account via Connect”
- [claimed-docs] “The Transaction Data Services provide account transaction data.”
- [claimed-docs] “Retrieves account ownership details (name, address, email and phone - where available) from a connected account at a financial institution.”
ai-native userExport all of my data in open formats and leave
weight 3 · round drawnPlaidnone0/10The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)
Mastercard Open Finance (Finicity)none0/10This is a B2B financial data API platform, not a consumer product with user-owned data to export; the evidence shows no data export/portability feature for end users to take their data out in open formats and leave. No mention of any account/data export or account deletion/portability capability anywhere in the docs.
ai-native userRead the product's source under an open license
weight 2 · round drawnPlaidnone0/10Plaid is a closed-source commercial API/SaaS product; its client SDKs (e.g., plaid-node) are open-source wrappers but the core Plaid service/source is not published under an open license, and no evidence shows the product's actual source available for inspection.
Payment initiation — stories about payment initiation in this arenaPayment initiation
Stories about payment initiation in this arena
Pay by bank
developerInitiate a bank payment from a connected account — a documented pay-by-bank or payment-initiation product with its live geographies stated honestly
weight 2 · round to PlaidPlaid documents a real Payment Initiation product enabling real-time bank payments across 18 named European markets, which is a fairly honest geography disclosure, but Plaid explicitly does not offer this product in the US (US flows rely on Auth+ACH via third-party rails, not Plaid-initiated payment). missing for 10: explicit US/global payment-initiation coverage or a clear statement of unsupported geographies beyond Europe, independent/hands-on confirmation of the payment-initiation flow working as documented, and clarity on settlement/liability model for developers.
- [claimed-docs] “Plaid's European Payments suite enables your users to make real-time payments without manually entering their account details or leaving you…”
- [claimed-docs] “Plaid's European Payments suite enables your users to make real-time payments without manually entering their account details or leaving you…”
- [claimed-docs] “Auth allows you to request a user's checking, savings, or cash management account and routing number, making it easy for you to initiate cre…”
Mastercard Open Finance (Finicity)none0/10The evidence pack describes the 'Pay' product family only as verification (account ownership, balance, ACH details, match), fraud/success prediction, and switching services — none of the docs describe an actual payment-initiation endpoint that moves funds from a connected account, nor any stated live geographies for such a capability. Without a documented API to actually initiate a bank payment, this axis is unmet.
- [claimed-docs] “Retrieves account ownership details (name, address, email and phone - where available) from a connected account at a financial institution.”
- [claimed-docs] “The Account Balance service provides real-time or cached bank account balance information from your customer's Financial Institution (FI).”
- [claimed-docs] “you can send customer data to our match account ownership details endpoint to receive confidence scores comparing the provided data and the …”
- [claimed-docs] “Predict [payment success]”
- [claimed-docs] “Switch [deposits and bill payments]”
- [claimed-docs] “Get ACH details”
Recurring
developerRecurring bank payments are supported — variable recurring payments, standing consents, or documented recurring debit flows built on the connection
weight 2 · round drawnPlaidnone0/10Plaid's Payment Initiation docs describe single real-time payments across European markets, with no mention of variable recurring payments, standing orders, or documented recurring debit/consent flows; Auth/ACH docs also only describe initiating one-off credits/debits, not recurring mandates.
- [claimed-docs] “Plaid's European Payments suite enables your users to make real-time payments without manually entering their account details or leaving you…”
- [claimed-docs] “Plaid's European Payments suite enables your users to make real-time payments without manually entering their account details or leaving you…”
- [claimed-docs] “Auth allows you to request a user's checking, savings, or cash management account and routing number, making it easy for you to initiate cre…”
Mastercard Open Finance (Finicity)none0/10Evidence covers account data (balances, ownership, transactions), ACH details, and 'switch deposits and bill payments' but nothing documents variable recurring payments, standing consents, or a recurring debit/payment-initiation flow — this product's Pay APIs appear focused on verification (account owner, balance, ACH details) rather than initiating recurring debits.
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
ai-native userChoose where my data is stored (region/residency)
weight 2 · round drawnPlaidnone0/10No evidence of any data residency/region selection controls in Plaid's documentation; the evidence pack covers products, sandbox, MCP server, and payment features but never mentions data storage location choice or regional hosting options.
Mastercard Open Finance (Finicity)none0/10No evidence anywhere in the pack discusses data residency, regional storage options, or geographic controls for where customer data is stored/processed. This is an applicable axis for a financial data platform handling sensitive PII, but nothing addresses it.
ai-native userControl data retention and deletion
weight 2 · round drawnPlaidnone0/10No evidence pack item documents any user- or developer-facing mechanism for controlling data retention periods or deleting stored financial data in Plaid; docs cover data collection (Auth, Identity, Transactions, Balance) but not retention/deletion controls. Community commentary even shows a user unsure how to revoke Plaid's access, underscoring the absence of a clear deletion/retention feature.
- [claimed-docs] “Retrieve up to 24 months of transaction data and stay up-to-date with webhooks”
- [community] “I gave them access to my bank via coinbase. If I change my bank password would they lose access to my account? If not, what do I need to do …”
Mastercard Open Finance (Finicity)none0/10The evidence pack covers API products (account data, verification, transactions, webhooks, onboarding) but contains no mention of data retention policies, deletion controls, or user-facing privacy/data-lifecycle management tools. Missing for 10: any documentation of data retention periods, deletion/erasure APIs, or consumer-facing controls over stored financial data.
ai-native userOpt out of telemetry and usage tracking
weight 2 · round drawnPlaidnone0/10No evidence in the pack addresses telemetry or usage-tracking opt-out for Plaid's SDKs, Link, or APIs; the docs and community items focus on financial data access and privacy concerns about data collection scope, not an opt-out mechanism for usage analytics.
Transactions enrichment — stories about transactions enrichment in this arenaTransactions enrichment
Stories about transactions enrichment in this arena
Cashflow
finance leadThe platform derives income and cash-flow signals from connected accounts — recurring streams, payroll detection, or documented income verification products built on the same data
weight 2 · round to Mastercard Open Finance (Finicity)Plaidnone0/10The evidence pack covers Auth, Balance, Identity, Transactions, Payment Initiation and Link, but contains no mention of an Income product, payroll detection, or recurring-stream/cash-flow analytics built on transaction data — the specific capability the story asks about is absent from the pack.
Docs confirm transaction data services with insights into recurring transactions, transaction types, consumer spending, and loan payments, plus credit-decisioning report APIs — directly supporting cash-flow/recurring-stream signals. However, there's no explicit mention of payroll detection or a dedicated income-verification product built on this data. missing for 10: explicit payroll/income detection feature, named income-verification product, independent validation of accuracy.
- [claimed-docs] “The Transaction Data Services provide account transaction data.”
- [claimed-docs] “Insights into: * [Transaction types] * [Recurring transactions] * [Consumer spending] * [Loan payments]”
- [claimed-docs] “APIs for credit decisioning [reports]”
- [claimed-docs] “The account and transaction data elements returned from Account Aggregation and Transaction Data vary depending on the account type.”
Enrichment
developerRaw bank transactions come back enriched — cleaned merchant names, categories, and logos — documented as a capability of the platform, not left as an exercise for me
weight 2 · round to Mastercard Open Finance (Finicity)Plaidnone0/10While Plaid's Transactions product is documented as returning transaction data, none of the evidence describes enrichment specifics like cleaned merchant names, categories, or logos being a documented feature — only raw transaction retrieval and webhooks are mentioned (plaid-docs-4, plaid-gh-1). Missing for 10: explicit documentation of merchant name cleaning, category taxonomy, and logo/icon fields as part of the Transactions response.
- [claimed-docs] “Retrieve up to 24 months of transaction data and stay up-to-date with webhooks”
- [github] “try { await plaidClient.transactionsSync(request); } catch (error) { const err = error.response.data; }”
Docs confirm Transaction Data Services return categorized insights (transaction types, recurring transactions, consumer spending, loan payments), which implies some enrichment/categorization layer, but nothing explicitly documents merchant-name cleansing or logo attachment as a first-class capability. Missing for 10: explicit documentation of merchant name normalization/cleanup and logo enrichment fields in the transaction schema.
- [claimed-docs] “The Transaction Data Services provide account transaction data.”
- [claimed-docs] “The account and transaction data elements returned from Account Aggregation and Transaction Data vary depending on the account type.”
- [claimed-docs] “Insights into: * [Transaction types] * [Recurring transactions] * [Consumer spending] * [Loan payments]”
Transactions
developerPull transaction history for a connected account through the API — paginated, with documented history depth and a sync pattern for fetching only what changed
weight 3 · round to PlaidPlaid's Transactions docs confirm up to 24 months of history and webhook-based updates, and the plaid-node SDK demonstrates the transactionsSync pattern for fetching only changed data, matching the story's pagination/sync/history-depth requirements. missing for 10: no explicit mention of pagination cursor mechanics or rate limits, and no independent/hands-on corroboration of sync behavior beyond the SDK snippet.
- [claimed-docs] “Retrieve up to 24 months of transaction data and stay up-to-date with webhooks”
- [github] “try { await plaidClient.transactionsSync(request); } catch (error) { const err = error.response.data; }”
- [github] “All errors can now be caught using try/catch with async/await or through promise chaining.”
Evidence confirms a dedicated Transaction Data Services API that returns account/transaction details and varies by account type, plus a webhook/notification system explicitly framed as eliminating constant polling, which implies a change-based sync pattern. However, no evidence documents pagination mechanics or a specific stated history depth (e.g., days/months of transactions) for the transaction endpoint. missing for 10: explicit pagination documentation, stated transaction history depth/lookback window, explicit delta/cursor sync pattern for transactions specifically (webhooks reference is generic, not transaction-specific).
- [claimed-docs] “The Transaction Data Services provide account transaction data.”
- [claimed-docs] “The account and transaction data elements returned from Account Aggregation and Transaction Data vary depending on the account type.”
- [claimed-docs] “Webhooks allow you to receive real-time notifications when specific events occur, eliminating the need for constant polling.”
- [claimed-docs] “[Account] and [transaction] details”
- [claimed-docs] “Insights into: * [Transaction types] * [Recurring transactions] * [Consumer spending] * [Loan payments]”
- [claimed-docs] “OBWMS will provide a comprehensive API for managing real-time event notifications, enabling you to subscribe to specific events, ensuring yo…”
Not comparable on these axes
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · not comparablePlaidn/aPlaid is a fintech data/API platform, not an agentic host or assistant interface where a user would plug in MCP servers for it to consume tools; the only MCP-related evidence shows Plaid exposing its own Dashboard as an MCP server (a different, server-provider axis), not Plaid acting as an MCP client consuming external tools.
- [claimed-docs] “The Dashboard MCP server is a remote MCP server hosted by Plaid. It provides Production diagnostics and analytics tools, including tools for…”
- [probe] “official MCP server documented at https://plaid.com/docs/resources/mcp/”
Mastercard Open Finance (Finicity)n/aMastercard Open Finance is a financial data/API platform, not an agent or assistant host that could itself consume external MCP servers as tools; the evidence only shows Mastercard publishing its own MCP server (agent-toolkit) for others to call into Open Finance APIs, which is the opposite role from 'plugging MCP servers into this product'.
- [probe] “official MCP server documented at https://developer.mastercard.com/platform/documentation/agent-toolkit/mcp-overview/”
- [claimed-docs] “Dynamic Code Generation: Generate accurate, working code examples based on current API specifications”
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · not comparablePlaidn/aPlaid is a financial data/payments API infrastructure product, not a user-facing product with a built-in AI assistant persona; this axis is a category error for this kind of B2B fintech API platform. No evidence describes a built-in AI assistant for delegating tasks (the MCP server is for dashboard diagnostics, not an in-product assistant).
Mastercard Open Finance (Finicity)n/aMastercard Open Finance is a developer API platform for financial data/verification, not a consumer or workflow product with a built-in AI assistant persona to delegate tasks to; the MCP toolkit evidence is about exposing APIs to external agents/tools, not a native in-product assistant.
ai-native userVersion, review, and roll back my automations
weight 1 · not comparablePlaidn/aPlaid is a financial data/payments API platform, not an automation-building tool with workflows to version, review, or roll back; this axis doesn't apply to its product category.
ai-native userSelf-host the core product
weight 3 · not comparablePlaidn/aPlaid is a hosted financial-data/API SaaS product built on proprietary bank connections and infrastructure; self-hosting the core service is not a plausible axis for this category (only a local quickstart demo app is offered, not the core Plaid backend).
ai-native userPrevent my data from being used to train AI models
weight 3 · not comparablePlaidn/aPlaid is a financial data connectivity API, not an AI model or AI product feature; the evidence pack contains no mention of AI model training or opt-out controls for such training. This axis is a category error for this type of product.