{ "data": { "a": { "slug": "flinks", "name": "Flinks", "vendor": "Flinks Technology Inc. (National Bank of Canada)", "vendorUrl": "https://www.flinks.com", "kind": "http-api", "category": "banking-data", "summary": "Flinks is a Canadian bank-data aggregator owned by National Bank of Canada. Its REST API and Flinks Connect widget read accounts, balances, transactions and holder details from Canadian and US institutions with the holder's consent, and start Canadian bank payments.", "url": "https://www.anchorterminal.com/tools/flinks", "markdownUrl": "https://www.anchorterminal.com/tools/flinks.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/flinks.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/flinks.json", "license": "Proprietary service under Flinks' Master Terms and Conditions. No open-source SDK or repository was found", "transports": [ "http" ], "packages": [], "auth": "api-key", "authNotes": "Two static keys issued by Flinks at onboarding. The secret key goes in the `flinks-auth-key` header of `/GenerateAuthorizeToken` and returns a single-use authorise token that expires after 15 minutes. Data endpoints take the `requestId` from `/Authorize` plus an `x-api-key` header. Neither key expires, and no scopes were found. Webhooks are signed with HMAC-SHA256 in a `flinks-authenticity-key` header. Flinks Outbound, the open banking product, uses an OAuth 2.0 authorisation code flow with a `client_id` and `client_secret` and Bearer tokens. Sandbox keys for the shared Toolbox instance are published in the docs. Production keys come from a Flinks representative after a contract.", "pricing": "paid", "pricingNotes": "Plans with a monthly minimum and a one-year term (https://www.flinks.com/pricing, checked 2026-10-08). Connect is $500 a month for 200 unique connections, $1,250 for 1,100, and custom from 20,000. Enrich is $250 a month for 100 API calls and $1,100 for 1,250. Upload is $500 a month for 20 documents and $1,500 for 100. Flinks Pay is quoted by sales. The page does not state the currency or the overage rates, and says there is no pay-as-you-go plan and no self-serve trial. The Toolbox sandbox is free, with keys published in the docs and no card.", "priceSummary": "Paid", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs index, the ten OpenAPI files or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://docs.flinks.com", "llmsTxt": "https://docs.flinks.com/llms.txt", "openapi": "https://docs.flinks.com/openapi.yaml", "capabilities": [ "bank.accounts", "bank.transactions", "bank.identity", "bank.payments", "bank.consent" ], "tags": [ "hosted", "api-key", "openapi", "llms-txt", "webhooks", "sandbox", "canada", "us", "enterprise", "sales-led", "status-page", "closed-source" ], "lastRelease": "2026-09-01", "graded": true, "anchor": { "graded": true, "score": 52.7, "grade": "D", "agentReady": false, "rank": 647, "ranked": true, "rankOf": 842, "categoryRank": 7, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 54, "maintenance": 31, "payments": 25, "reliability": 53, "schema": 83, "security": 50, "transparency": 60 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "Ten public OpenAPI files, an llms.txt index with Markdown twins and published sandbox keys let an agent start without a signup. Live access needs a one-year contract from $500 a month, keys never expire, no rate-limit numbers are published, and the status page logged 77 incidents in 90 days.", "bestFor": "A lender or fintech with steady volume that needs Canadian bank data, income and lending attributes, PDF statements or Canadian bank payments.", "strengths": [ "Ten OpenAPI 3.0 files are public at docs.flinks.com, 85 operations in all, with the main Connect and Enrich file holding 34", "Shared sandbox keys for the Toolbox instance are published in the docs, so test calls need no account", "llms.txt lists 216 pages with Markdown twins, and the docs add a skill file and a read-only documentation MCP server", "Plan prices are public. Connect starts at $500 a month for 200 unique connections, with no integration or platform fee", "Each instance is hosted in the country it serves, Canada or the US, and `/DeleteCard` deletes all data held for a connection" ], "weaknesses": [ "Live access needs a contract with a monthly minimum and a one-year term. The pricing page says there is no pay-as-you-go plan or self-serve trial", "The secret key, `x-api-key` and HMAC secret do not expire, and no scopes or rotation steps were found for the Connect API", "No rate-limit numbers are published, and `TOO_MANY_REQUESTS` is documented under HTTP 401 with no Retry-After", "status.flinks.com lists 77 incidents in the 90 days to 8 October 2026, 16 of them on Flinks' own components", "`/GetAccountsDetail` returns the whole 90 or 365 days of transactions in one payload with no pagination, and no official SDK was found" ], "agentNotes": [ "Call `/GenerateAuthorizeToken` with the secret key in `flinks-auth-key`, then pass the returned token to the Connect iframe or to `/Authorize`. The token is single-use and expires after 15 minutes.", "Send the account holder through Flinks Connect in a browser. The API alone cannot complete a first bank login, and sandbox iframes need `demo=true`.", "Store the `loginId`. Call `/Authorize` with it and `MostRecentCached: true` for a new `requestId` each session, because `/GetAccountsDetail` consumes the `requestId`.", "On a 202 from `/GetAccountsDetail`, poll `/GetAccountsDetailAsync` every 10 seconds for at most 30 minutes, or ask support to enable webhooks.", "Route each end user to the instance for their country. A `loginId` from the Canadian instance is not valid on the US one." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 52.7 } ], "editorialScores": { "ergonomics": 54, "maintenance": 31, "payments": 25, "reliability": 53, "schema": 83, "security": 50, "transparency": 48 }, "provenanceScore": 71 }, "connect": { "http": "curl --request POST \\\n --url https://toolbox-api.private.fin.ag/v3/{customerId}/BankingServices/GenerateAuthorizeToken \\\n --header 'Content-Type: application/json' \\\n --header 'flinks-auth-key: YOUR_SECRET_KEY'", "claudeCode": "claude mcp add flinks --transport http https://docs.flinks.com/mcp" }, "letme": { "capability": "https://letme.dev/bank.accounts", "tool": "https://letme.dev/flinks" }, "area": "domain-data", "provenance": { "legalEntity": "Flinks Technology Inc.", "domain": "flinks.com", "domainRegistered": "1997-06-03", "endpointOnVendorDomain": false, "terms": "https://www.flinks.com/terms-and-conditions", "privacy": "https://www.flinks.com/privacy-policy", "statusPage": "https://status.flinks.com", "changelog": "https://docs.flinks.com/changelog", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The terms link is the Master Terms and Conditions, last updated 3 August 2023, which govern use of the Flinks technology under an order form and name Flinks Technology Inc. Service schedules for connectivity, enrichment and upload are separate pages on flinks.com.", "The privacy link holds the General Privacy Statement (22 September 2022) and the Services Privacy Statement (19 April 2024) on one page. The Services statement covers bank data read through the product and names National Bank of Canada as Flinks' parent company.", "API calls go to https://{instance}-api.private.fin.ag and the widget to https://{instance}-iframe.private.fin.ag. Flinks Outbound answers at ob.flinksapp.com. Neither is under flinks.com, so the endpoint is recorded as off the vendor's domain. We did not confirm the registrant of fin.ag.", "flinks.com/.well-known/security.txt, www.flinks.com/.well-known/security.txt and docs.flinks.com/.well-known/security.txt return 404. The security page gives security@flinks.com for vulnerability reports.", "status.flinks.com runs on incident.io. changelog.flinks.com redirects to docs.flinks.com/changelog.", "Verisign RDAP gives 1997-06-03 as the registration date of flinks.com and GoDaddy.com, LLC as registrar. No street address for the company was found on the pages read." ], "score": 71 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/flinks.json", "live": { "slug": "flinks", "vendorStatus": { "page": "https://status.flinks.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-09T11:39:22.196786531Z" }, "updatedAt": "2026-10-09T11:39:22.196786531Z" } }, "answer": "Flinks scores 52.7 (D) on agent readiness against Yodlee Core API's 41.9 (E), and leads in 5 of 7 scored categories.", "b": { "slug": "yodlee-financial-data", "name": "Yodlee Core API", "vendor": "Yodlee, Inc.", "vendorUrl": "https://www.yodlee.com", "kind": "http-api", "category": "banking-data", "summary": "Yodlee's Core API (v1.1) aggregates a consumer's bank, card, investment, loan and insurance accounts for balances, categorised transactions, holdings, statements and account-owner details. Consumers link accounts through the embedded FastLink 4 widget.", "url": "https://www.anchorterminal.com/tools/yodlee-financial-data", "markdownUrl": "https://www.anchorterminal.com/tools/yodlee-financial-data.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/yodlee-financial-data.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/yodlee-financial-data.json", "repo": "https://github.com/Yodlee/OpenAPI", "license": "Proprietary service. The Swagger file on GitHub is MIT", "transports": [ "http" ], "packages": [], "auth": "oauth", "authNotes": "Self-serve for the sandbox. Registering on the developer portal gives a `clientId`, a `secret` and an admin `loginName` on the API dashboard. `POST /auth/token` takes the id and secret in a form body and a `loginName` header, and returns a bearer token that lasts 30 minutes and acts for that user, or for the admin on administrative calls. Every call also sends `Api-Version: 1.1`. Each environment (sandbox, development, production) has its own credentials. How production access is granted is not stated in the public docs. Full account numbers and holder details need Yodlee Security Office approval.", "pricing": "paid", "pricingNotes": "No public price. `/pricing` returns 404 on yodlee.com and on the developer portal, and product pages ask for a demo. The sandbox is free on registration, with five preconfigured users and sample data only, so an agent's owner can test without a contract (checked 2026-10-08).", "priceSummary": "Paid", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the developer docs, the Swagger file or yodlee.com (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 17, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://developer.yodlee.com/resources/yodlee/yodlee-api-overview/docs", "openapi": "https://raw.githubusercontent.com/Yodlee/OpenAPI/main/swagger.yaml", "capabilities": [ "bank.accounts", "bank.transactions", "bank.identity", "bank.consent" ], "tags": [ "hosted", "oauth", "openapi", "sandbox", "webhooks", "sales-led", "closed-source", "enterprise", "soc2" ], "lastRelease": "2026-07-31", "graded": true, "anchor": { "graded": true, "score": 41.9, "grade": "E", "agentReady": false, "rank": 796, "ranked": true, "rankOf": 842, "categoryRank": 12, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 58, "maintenance": 33, "payments": 15, "reliability": 15, "schema": 71, "security": 49, "transparency": 53 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "A public Swagger 2.0 file covers 98 operations with per-operation error codes, and tokens last 30 minutes and are bound to one end user. No price, service terms, status page, rate limit or SLA is published, there is no official server SDK, and the sandbox is limited to five preconfigured users with sample data.", "bestFor": "A bank, wealth firm or fintech with a Yodlee contract that needs wide account coverage, including investment holdings, loans and insurance, in the US, UK, Australia and India.", "strengths": [ "Public Swagger 2.0 file on GitHub (MIT) with 98 operations, 267 definitions and `Y`-prefixed error codes listed per operation", "Access tokens expire after 30 minutes, are bound to one end user's `loginName`, and can be revoked with `DELETE /auth/token`", "Free sandbox on registration with five preconfigured test users, per the docs", "Consent endpoints list, renew and record open banking consents, and `DELETE /user/unregister` removes a user and their data", "The Security FAQ states an annual SOC 2 Type 2 assessment, PCI DSS 4.0.1 Level One certification and yearly third-party penetration tests" ], "weaknesses": [ "No public price, service agreement or developer terms. The terms address named in the Swagger file returns 404", "No status page, rate limit, 429 guidance, idempotency key or SLA was found in the pages read", "No official server SDK. Yodlee's docs tell developers to generate a client from the Swagger file", "The Swagger file was last updated on 22 April 2026 to the November 2025 release and lacks fields added in June and July 2026, such as `isCrypto`", "The sandbox cannot register new users, and full account numbers and holder details need Yodlee Security Office approval", "The privacy notice covers only Yodlee's own consumer services and websites, and no DPA or sub-processor list is public" ], "agentNotes": [ "Get a token with `POST /auth/token`, sending `Api-Version: 1.1` and the end user's `loginName` as headers and `clientId` and `secret` in a form body. Reuse it for up to 30 minutes", "Use the admin `loginName` only for administrative calls such as webhook subscriptions. A token made with a user's `loginName` reads only that user's data", "In the sandbox, pick one of the five preconfigured users. Registering new users is not supported there", "Page `GET /transactions` with `skip` and `top` (1 to 500). Without dates it returns the last 30 days, and at most two years with `fromDate` and `toDate`", "A person must link accounts in FastLink 4 first. Then read `GET /providerAccounts` for link status before `GET /accounts`", "Subscribe to `DATA_UPDATES` or `REFRESH` webhooks, or poll `GET /dataExtracts/events` in windows of at most 60 minutes, and do not poll accounts in a loop" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 41.9 } ], "editorialScores": { "ergonomics": 58, "maintenance": 33, "payments": 15, "reliability": 15, "schema": 71, "security": 49, "transparency": 32 }, "provenanceScore": 73 }, "connect": { "http": "POST /auth/token\nApi-Version: 1.1\nloginName: \u003cloginName\u003e\nContent-Type: application/x-www-form-urlencoded\n\nclientId=\u003cclientId\u003e\u0026secret=\u003csecret\u003e" }, "letme": { "capability": "https://letme.dev/bank.accounts", "tool": "https://letme.dev/yodlee-financial-data" }, "area": "domain-data", "provenance": { "legalEntity": "Yodlee, Inc.", "domain": "yodlee.com", "domainRegistered": "1999-02-09", "endpointOnVendorDomain": null, "terms": "", "privacy": "", "statusPage": "", "changelog": "https://developer.yodlee.com/resources/yodlee", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The privacy notice names Yodlee, Inc. and its subsidiaries Yodlee Credit, LLC, Yodlee Data Services, LLC and Yodlee Infotech Private Limited. The company page says Yodlee was acquired by Envestnet in 2015 and joined the STG portfolio in 2025.", "`terms` is left out. No service agreement or developer terms are published. The Swagger file gives https://developer.yodlee.com/terms/condition as its terms of service, and that address returns 404.", "`privacy` is left out. The privacy notice at https://www.yodlee.com/legal/privacy-notice says it applies to Yodlee's direct-to-consumer services and websites, and that a client's own privacy practices apply to services delivered through a Yodlee client, which is how API data is handled.", "`endpointOnVendorDomain` is null. The public docs print API paths without a host, and the host is given with the credentials on a dashboard we did not read.", "No status page is linked from yodlee.com or the developer portal, and status.yodlee.com did not answer.", "https://www.yodlee.com/.well-known/security.txt returns the home page, and the same path on developer.yodlee.com returns 404.", "Verisign's RDAP server gives a registration date of 1999-02-09 and CSC Corporate Domains, Inc. as registrar." ], "score": 73 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/yodlee-financial-data.json" }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Flinks Technology Inc. (National Bank of Canada)", "b": "Yodlee, Inc.", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "API key", "b": "OAuth", "name": "Auth" }, { "a": "Paid", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under Flinks' Master Terms and Conditions. No open-source SDK or repository was found", "b": "Proprietary service. The Swagger file on GitHub is MIT", "name": "Licence" }, { "a": "yes", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "2026-09-01", "b": "2026-07-31", "name": "Last release" }, { "a": "2023-08-03", "b": "no document linked", "name": "Terms last updated" }, { "a": "2022-09-22", "b": "no document linked", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "17 stars", "name": "Popularity" } ], "faq": [ { "answer": "Flinks scores 52.7 (D) on agent readiness against Yodlee Core API's 41.9 (E), and leads in 5 of 7 scored categories.", "question": "Which is better for AI agents, Flinks or Yodlee Core API?" }, { "answer": "Flinks needs an API key. Yodlee Core API uses an OAuth sign-in.", "question": "Do Flinks and Yodlee Core API need an API key?" }, { "answer": "No hosted endpoint is listed for Flinks. No hosted endpoint is listed for Yodlee Core API.", "question": "Can an agent call Flinks and Yodlee Core API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 53 against 15", "Schema \u0026 documentation, 83 against 71", "Payments \u0026 pricing, 25 against 15", "Transparency \u0026 trust, 60 against 53" ], "also": null, "goodFor": "A lender or fintech with steady volume that needs Canadian bank data, income and lending attributes, PDF statements or Canadian bank payments.", "slug": "flinks", "watchFor": "Live access needs a contract with a monthly minimum and a one-year term. The pricing page says there is no pay-as-you-go plan or self-serve trial" }, { "aheadOn": null, "also": null, "goodFor": "A bank, wealth firm or fintech with a Yodlee contract that needs wide account coverage, including investment holdings, loans and insurance, in the US, UK, Australia and India.", "slug": "yodlee-financial-data", "watchFor": "No public price, service agreement or developer terms. The terms address named in the Swagger file returns 404" } ], "job": { "capability": "bank.accounts", "name": "Bank accounts" }, "others": [ { "json": "https://www.anchorterminal.com/compare/akoya-vs-flinks.json", "title": "Akoya vs Flinks", "url": "https://www.anchorterminal.com/compare/akoya-vs-flinks" }, { "json": "https://www.anchorterminal.com/compare/akoya-vs-yodlee-financial-data.json", "title": "Akoya vs Yodlee Core API", "url": "https://www.anchorterminal.com/compare/akoya-vs-yodlee-financial-data" }, { "json": "https://www.anchorterminal.com/compare/belvo-vs-flinks.json", "title": "Belvo vs Flinks", "url": "https://www.anchorterminal.com/compare/belvo-vs-flinks" }, { "json": "https://www.anchorterminal.com/compare/belvo-vs-yodlee-financial-data.json", "title": "Belvo vs Yodlee Core API", "url": "https://www.anchorterminal.com/compare/belvo-vs-yodlee-financial-data" }, { "json": "https://www.anchorterminal.com/compare/enable-banking-vs-flinks.json", "title": "Enable Banking vs Flinks", "url": "https://www.anchorterminal.com/compare/enable-banking-vs-flinks" }, { "json": "https://www.anchorterminal.com/compare/enable-banking-vs-yodlee-financial-data.json", "title": "Enable Banking vs Yodlee Core API", "url": "https://www.anchorterminal.com/compare/enable-banking-vs-yodlee-financial-data" }, { "json": "https://www.anchorterminal.com/compare/flinks-vs-gocardless-bank-account-data.json", "title": "Flinks vs GoCardless Bank Account Data", "url": "https://www.anchorterminal.com/compare/flinks-vs-gocardless-bank-account-data" }, { "json": "https://www.anchorterminal.com/compare/flinks-vs-mx.json", "title": "Flinks vs MX Platform API", "url": "https://www.anchorterminal.com/compare/flinks-vs-mx" }, { "json": "https://www.anchorterminal.com/compare/flinks-vs-plaid.json", "title": "Flinks vs Plaid", "url": "https://www.anchorterminal.com/compare/flinks-vs-plaid" }, { "json": "https://www.anchorterminal.com/compare/flinks-vs-salt-edge.json", "title": "Flinks vs Salt Edge Account Information", "url": "https://www.anchorterminal.com/compare/flinks-vs-salt-edge" }, { "json": "https://www.anchorterminal.com/compare/flinks-vs-teller.json", "title": "Flinks vs Teller", "url": "https://www.anchorterminal.com/compare/flinks-vs-teller" }, { "json": "https://www.anchorterminal.com/compare/flinks-vs-tink.json", "title": "Flinks vs Tink", "url": "https://www.anchorterminal.com/compare/flinks-vs-tink" }, { "json": "https://www.anchorterminal.com/compare/flinks-vs-truelayer.json", "title": "Flinks vs TrueLayer", "url": "https://www.anchorterminal.com/compare/flinks-vs-truelayer" }, { "json": "https://www.anchorterminal.com/compare/flinks-vs-yapily.json", "title": "Flinks vs Yapily", "url": "https://www.anchorterminal.com/compare/flinks-vs-yapily" }, { "json": "https://www.anchorterminal.com/compare/gocardless-bank-account-data-vs-yodlee-financial-data.json", "title": "GoCardless Bank Account Data vs Yodlee Core API", "url": "https://www.anchorterminal.com/compare/gocardless-bank-account-data-vs-yodlee-financial-data" }, { "json": "https://www.anchorterminal.com/compare/mx-vs-yodlee-financial-data.json", "title": "MX Platform API vs Yodlee Core API", "url": "https://www.anchorterminal.com/compare/mx-vs-yodlee-financial-data" }, { "json": "https://www.anchorterminal.com/compare/plaid-vs-yodlee-financial-data.json", "title": "Plaid vs Yodlee Core API", "url": "https://www.anchorterminal.com/compare/plaid-vs-yodlee-financial-data" }, { "json": "https://www.anchorterminal.com/compare/salt-edge-vs-yodlee-financial-data.json", "title": "Salt Edge Account Information vs Yodlee Core API", "url": "https://www.anchorterminal.com/compare/salt-edge-vs-yodlee-financial-data" }, { "json": "https://www.anchorterminal.com/compare/teller-vs-yodlee-financial-data.json", "title": "Teller vs Yodlee Core API", "url": "https://www.anchorterminal.com/compare/teller-vs-yodlee-financial-data" }, { "json": "https://www.anchorterminal.com/compare/tink-vs-yodlee-financial-data.json", "title": "Tink vs Yodlee Core API", "url": "https://www.anchorterminal.com/compare/tink-vs-yodlee-financial-data" }, { "json": "https://www.anchorterminal.com/compare/truelayer-vs-yodlee-financial-data.json", "title": "TrueLayer vs Yodlee Core API", "url": "https://www.anchorterminal.com/compare/truelayer-vs-yodlee-financial-data" }, { "json": "https://www.anchorterminal.com/compare/yapily-vs-yodlee-financial-data.json", "title": "Yapily vs Yodlee Core API", "url": "https://www.anchorterminal.com/compare/yapily-vs-yodlee-financial-data" } ], "scores": [ { "by": 38, "edge": "flinks", "flinks": 53, "key": "reliability", "name": "Reliability", "weight": 16, "yodlee-financial-data": 15 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 12, "edge": "flinks", "flinks": 83, "key": "schema", "name": "Schema \u0026 documentation", "weight": 13, "yodlee-financial-data": 71 }, { "by": 4, "edge": "yodlee-financial-data", "flinks": 54, "key": "ergonomics", "name": "Agent ergonomics", "weight": 13, "yodlee-financial-data": 58 }, { "by": 1, "edge": "flinks", "flinks": 50, "key": "security", "name": "Security \u0026 auth", "weight": 14, "yodlee-financial-data": 49 }, { "by": 10, "edge": "flinks", "flinks": 25, "key": "payments", "name": "Payments \u0026 pricing", "weight": 10, "yodlee-financial-data": 15 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 2, "edge": "yodlee-financial-data", "flinks": 31, "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7, "yodlee-financial-data": 33 }, { "by": 7, "edge": "flinks", "flinks": 60, "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7, "yodlee-financial-data": 53 } ], "summary": "Flinks scores 52.7 (D) on agent readiness against Yodlee Core API's 41.9 (E), and leads in 5 of 7 scored categories. Both do bank accounts.", "verdicts": { "flinks": "Ten public OpenAPI files, an llms.txt index with Markdown twins and published sandbox keys let an agent start without a signup. Live access needs a one-year contract from $500 a month, keys never expire, no rate-limit numbers are published, and the status page logged 77 incidents in 90 days.", "yodlee-financial-data": "A public Swagger 2.0 file covers 98 operations with per-operation error codes, and tokens last 30 minutes and are bound to one end user. No price, service terms, status page, rate limit or SLA is published, there is no official server SDK, and the sandbox is limited to five preconfigured users with sample data." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/flinks-vs-yodlee-financial-data", "json": "https://www.anchorterminal.com/compare/flinks-vs-yodlee-financial-data.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/flinks-vs-yodlee-financial-data.md", "slim": "https://www.anchorterminal.com/compare/flinks-vs-yodlee-financial-data.min.md" }, "markdown": "Flinks scores 52.7 (D) on agent readiness against Yodlee Core API's 41.9 (E), and leads in 5 of 7 scored categories. Both do bank accounts.\n\n- Flinks: grade D, 52.7/100, rank #647 of 842. Markdown https://www.anchorterminal.com/tools/flinks.md · JSON https://www.anchorterminal.com/api/v1/tools/flinks.json\n- Yodlee Core API: grade E, 41.9/100, rank #796 of 842. Markdown https://www.anchorterminal.com/tools/yodlee-financial-data.md · JSON https://www.anchorterminal.com/api/v1/tools/yodlee-financial-data.json\n\n## Which one, for what\n\n### Flinks (D)\n\nGood for: A lender or fintech with steady volume that needs Canadian bank data, income and lending attributes, PDF statements or Canadian bank payments.\n\nAhead on:\n- Reliability, 53 against 15\n- Schema \u0026 documentation, 83 against 71\n- Payments \u0026 pricing, 25 against 15\n- Transparency \u0026 trust, 60 against 53\n\nWatch for: Live access needs a contract with a monthly minimum and a one-year term. The pricing page says there is no pay-as-you-go plan or self-serve trial\n\n### Yodlee Core API (E)\n\nGood for: A bank, wealth firm or fintech with a Yodlee contract that needs wide account coverage, including investment holdings, loans and insurance, in the US, UK, Australia and India.\n\nWatch for: No public price, service agreement or developer terms. The terms address named in the Swagger file returns 404\n\n\n## Score by category\n\n| Category | Weight | Flinks | Yodlee Core API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 53 | 15 | Flinks +38 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 83 | 71 | Flinks +12 |\n| Agent ergonomics | 13% (16.2 this run) | 54 | 58 | Yodlee Core API +4 |\n| Security \u0026 auth | 14% (17.5 this run) | 50 | 49 | Flinks +1 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 25 | 15 | Flinks +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 31 | 33 | Yodlee Core API +2 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 60 | 53 | Flinks +7 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **52.7 · D** | **41.9 · E** | |\n\n## Facts side by side\n\n| Fact | Flinks | Yodlee Core API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Flinks Technology Inc. (National Bank of Canada) | Yodlee, Inc. |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | HTTP | HTTP |\n| Auth | API key | OAuth |\n| Pricing | Paid | Paid |\n| x402 | no | no |\n| Licence | Proprietary service under Flinks' Master Terms and Conditions. No open-source SDK or repository was found | Proprietary service. The Swagger file on GitHub is MIT |\n| Read-only variant documented | yes | no |\n| llms.txt | yes | no |\n| Last release | 2026-09-01 | 2026-07-31 |\n| Terms last updated | 2023-08-03 | no document linked |\n| Privacy policy last updated | 2022-09-22 | no document linked |\n| Customer content may train models | not found in the text | |\n| Terms restrict automated access | not found in the text | |\n| Terms restrict benchmarking | not found in the text | |\n| Terms or service can change without notice | yes | |\n| Arbitration or class-action waiver | not found in the text | |\n| Popularity | none | 17 stars |\n\n## Verdicts\n\n**Flinks.** Ten public OpenAPI files, an llms.txt index with Markdown twins and published sandbox keys let an agent start without a signup. Live access needs a one-year contract from $500 a month, keys never expire, no rate-limit numbers are published, and the status page logged 77 incidents in 90 days.\n\n**Yodlee Core API.** A public Swagger 2.0 file covers 98 operations with per-operation error codes, and tokens last 30 minutes and are bound to one end user. No price, service terms, status page, rate limit or SLA is published, there is no official server SDK, and the sandbox is limited to five preconfigured users with sample data.\n\n## Before you call either\n\n### Flinks\n\n1. Call `/GenerateAuthorizeToken` with the secret key in `flinks-auth-key`, then pass the returned token to the Connect iframe or to `/Authorize`. The token is single-use and expires after 15 minutes.\n2. Send the account holder through Flinks Connect in a browser. The API alone cannot complete a first bank login, and sandbox iframes need `demo=true`.\n3. Store the `loginId`. Call `/Authorize` with it and `MostRecentCached: true` for a new `requestId` each session, because `/GetAccountsDetail` consumes the `requestId`.\n4. On a 202 from `/GetAccountsDetail`, poll `/GetAccountsDetailAsync` every 10 seconds for at most 30 minutes, or ask support to enable webhooks.\n5. Route each end user to the instance for their country. A `loginId` from the Canadian instance is not valid on the US one.\n\n### Yodlee Core API\n\n1. Get a token with `POST /auth/token`, sending `Api-Version: 1.1` and the end user's `loginName` as headers and `clientId` and `secret` in a form body. Reuse it for up to 30 minutes\n2. Use the admin `loginName` only for administrative calls such as webhook subscriptions. A token made with a user's `loginName` reads only that user's data\n3. In the sandbox, pick one of the five preconfigured users. Registering new users is not supported there\n4. Page `GET /transactions` with `skip` and `top` (1 to 500). Without dates it returns the last 30 days, and at most two years with `fromDate` and `toDate`\n5. A person must link accounts in FastLink 4 first. Then read `GET /providerAccounts` for link status before `GET /accounts`\n6. Subscribe to `DATA_UPDATES` or `REFRESH` webhooks, or poll `GET /dataExtracts/events` in windows of at most 60 minutes, and do not poll accounts in a loop\n\n## Questions\n\n### Which is better for AI agents, Flinks or Yodlee Core API?\n\nFlinks scores 52.7 (D) on agent readiness against Yodlee Core API's 41.9 (E), and leads in 5 of 7 scored categories.\n\n### Do Flinks and Yodlee Core API need an API key?\n\nFlinks needs an API key. Yodlee Core API uses an OAuth sign-in.\n\n### Can an agent call Flinks and Yodlee Core API without installing anything?\n\nNo hosted endpoint is listed for Flinks. No hosted endpoint is listed for Yodlee Core API.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/flinks-vs-yodlee-financial-data.json, and with the fewest tokens: https://www.anchorterminal.com/compare/flinks-vs-yodlee-financial-data.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"flinks\", \"b\": \"yodlee-financial-data\"}`. From a terminal: `anchor compare flinks yodlee-financial-data`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/flinks.json and https://www.anchorterminal.com/api/v1/tools/yodlee-financial-data.json\n\n## Other comparisons with Flinks or Yodlee Core API\n\n- [Akoya vs Flinks](https://www.anchorterminal.com/compare/akoya-vs-flinks.md)\n- [Akoya vs Yodlee Core API](https://www.anchorterminal.com/compare/akoya-vs-yodlee-financial-data.md)\n- [Belvo vs Flinks](https://www.anchorterminal.com/compare/belvo-vs-flinks.md)\n- [Belvo vs Yodlee Core API](https://www.anchorterminal.com/compare/belvo-vs-yodlee-financial-data.md)\n- [Enable Banking vs Flinks](https://www.anchorterminal.com/compare/enable-banking-vs-flinks.md)\n- [Enable Banking vs Yodlee Core API](https://www.anchorterminal.com/compare/enable-banking-vs-yodlee-financial-data.md)\n- [Flinks vs GoCardless Bank Account Data](https://www.anchorterminal.com/compare/flinks-vs-gocardless-bank-account-data.md)\n- [Flinks vs MX Platform API](https://www.anchorterminal.com/compare/flinks-vs-mx.md)\n- [Flinks vs Plaid](https://www.anchorterminal.com/compare/flinks-vs-plaid.md)\n- [Flinks vs Salt Edge Account Information](https://www.anchorterminal.com/compare/flinks-vs-salt-edge.md)\n- [Flinks vs Teller](https://www.anchorterminal.com/compare/flinks-vs-teller.md)\n- [Flinks vs Tink](https://www.anchorterminal.com/compare/flinks-vs-tink.md)\n- [Flinks vs TrueLayer](https://www.anchorterminal.com/compare/flinks-vs-truelayer.md)\n- [Flinks vs Yapily](https://www.anchorterminal.com/compare/flinks-vs-yapily.md)\n- [GoCardless Bank Account Data vs Yodlee Core API](https://www.anchorterminal.com/compare/gocardless-bank-account-data-vs-yodlee-financial-data.md)\n- [MX Platform API vs Yodlee Core API](https://www.anchorterminal.com/compare/mx-vs-yodlee-financial-data.md)\n- [Plaid vs Yodlee Core API](https://www.anchorterminal.com/compare/plaid-vs-yodlee-financial-data.md)\n- [Salt Edge Account Information vs Yodlee Core API](https://www.anchorterminal.com/compare/salt-edge-vs-yodlee-financial-data.md)\n- [Teller vs Yodlee Core API](https://www.anchorterminal.com/compare/teller-vs-yodlee-financial-data.md)\n- [Tink vs Yodlee Core API](https://www.anchorterminal.com/compare/tink-vs-yodlee-financial-data.md)\n- [TrueLayer vs Yodlee Core API](https://www.anchorterminal.com/compare/truelayer-vs-yodlee-financial-data.md)\n- [Yapily vs Yodlee Core API](https://www.anchorterminal.com/compare/yapily-vs-yodlee-financial-data.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-09", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Flinks vs Yodlee Core API", "url": "" } ], "description": "Flinks scores 52.7 (D) on agent readiness against Yodlee Core API's 41.9 (E), and leads in 5 of 7 scored categories. Both do bank accounts. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Flinks D 52.7", "Yodlee Core API E 41.9", "scores" ], "h1": "Flinks vs Yodlee Core API", "image": "https://www.anchorterminal.com/assets/og/compare-flinks-vs-yodlee-financial-data.png", "path": "/compare/flinks-vs-yodlee-financial-data", "published": "2026-10-01", "section": "tools", "title": "Flinks vs Yodlee Core API for AI agents, D 52.7 vs E 41.9", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/flinks-vs-yodlee-financial-data" }, "tokens": { "markdown": 2450, "slim": 680 }, "version": 1 }