{ "data": { "a": { "slug": "yapily", "name": "Yapily", "vendor": "Yapily", "vendorUrl": "https://www.yapily.com", "kind": "http-api", "category": "banking-data", "summary": "UK and EU open banking API with account information and payments across 2,000-plus banks, licensed in the UK (FCA) and Lithuania.", "url": "https://www.anchorterminal.com/tools/yapily", "markdownUrl": "https://www.anchorterminal.com/tools/yapily.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/yapily.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/yapily.json", "repo": "https://github.com/yapily/yapily-sdk-nodejs", "license": "MIT (SDKs)", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.yapily.com", "packages": [ { "registry": "npm", "name": "@yapily/yapily-api" } ], "auth": "api-key", "authNotes": "HTTP basic auth with the application id as the username and the application secret as the password, downloaded as a JSON file from the Console. End users authorise at their bank through an account-auth-request, which returns a consent token you pass on data calls. The docs MCP server at docs.yapily.com/mcp needs no auth at all, because it only searches the documentation.", "pricing": "paid", "pricingNotes": "No published prices. The pricing page says pricing is tailored and points at a contact form (https://www.yapily.com/pricing). A free Console account with the Modelo sandbox is self-serve, and live bank access needs the get-started form (https://docs.yapily.com/getting-started/get-started.md).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 14, "npmWeekly": 50, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://docs.yapily.com", "llmsTxt": "https://docs.yapily.com/llms.txt", "openapi": "https://docs.yapily.com/openapi-converted.json", "capabilities": [ "bank.accounts", "bank.transactions", "bank.identity", "bank.payments", "bank.consent" ], "tags": [ "hosted", "llms-txt", "openapi", "mcp", "uk", "eu", "webhooks", "enterprise", "closed-source" ], "lastRelease": "2025-06-30", "graded": true, "anchor": { "graded": true, "score": 57.6, "grade": "C", "agentReady": false, "rank": 543, "ranked": true, "rankOf": 842, "categoryRank": 6, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 77, "maintenance": 67, "payments": 10, "reliability": 55, "schema": 88, "security": 37, "transparency": 71 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "llms.txt, llms-full.txt, a no-auth docs MCP server and an OpenAPI file. No public pricing; live access starts with a sales form.", "bestFor": "UK and EEA data and payments from one API, for builders who want docs an agent can read in one fetch.", "strengths": [ "llms.txt, llms-full.txt, a no-auth docs MCP server and an OpenAPI file", "Error bodies carry a source of USER, INSTITUTION or YAPILY and a tracingId", "Changelog with ten dated entries from July to September 2026, breaking changes flagged", "Public subprocessor list with locations, primary hosting in London", "Transactions take from, before, limit up to 1,000 and sort" ], "weaknesses": [ "No public pricing; live access starts with a sales form", "No security.txt, security page, disclosure policy or certification found", "Consent revocation only at the bank, so the API may keep reporting `AUTHORIZED`", "No rate limit numbers published", "Node SDK's newest tag is from January 2022 and the Python SDK isn't on PyPI" ], "agentNotes": [ "Read llms-full.txt once and cache it; it's the whole documentation in one fetch", "Add the Modelo sandbox in the Console before your first account-auth-request, or institutions comes back empty", "Treat a 403 on a data call as a revoked or expired consent and send the user back through authorisation", "Check the error source field first; USER and INSTITUTION failures won't clear on retry", "In the UK, call extend-consent with lastConfirmedAt before the reconfirmBy date, or the consent lapses at 90 days" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 2.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 57.6 } ], "editorialScores": { "ergonomics": 77, "maintenance": 67, "payments": 10, "reliability": 55, "schema": 88, "security": 37, "transparency": 70 }, "provenanceScore": 72 }, "connect": { "http": "curl -u \"$YAPILY_APPLICATION_ID:$YAPILY_APPLICATION_SECRET\" https://api.yapily.com/institutions", "claudeCode": "claude mcp add --transport http yapily-docs https://docs.yapily.com/mcp", "config": { "mcpServers": { "yapily-docs": { "type": "http", "url": "https://docs.yapily.com/mcp" } } } }, "letme": { "capability": "https://letme.dev/bank.accounts", "tool": "https://letme.dev/yapily" }, "area": "domain-data", "provenance": { "legalEntity": "Yapily Ltd", "domain": "yapily.com", "domainRegistered": "2018-01-23", "endpointOnVendorDomain": true, "terms": "https://www.yapily.com/legal/website-terms-of-use", "privacy": "https://www.yapily.com/legal/privacy-policy", "statusPage": "https://status.yapily.com", "changelog": "", "securityTxt": "none", "checked": "2026-09-30", "notes": [ "Yapily Ltd, company 10842280, 66 Paul Street, London EC2A 4NA, is unregulated; Yapily Connect Ltd (company 11598433, FCA 827001) and Yapily Connect UAB (company 305602679, Bank of Lithuania LB002045) hold the licences.", "The customer contract is the Data Handling Agreement at yapily.com/legal/data-handling-agreement; the website terms are what's public.", "www.yapily.com/.well-known/security.txt returns 404.", "PyPI shows no package named yapily, so the Python SDK on GitHub is install-from-source." ], "score": 72 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/yapily.json", "live": { "slug": "yapily", "probe": { "target": "https://api.yapily.com", "method": "get", "lastAt": "2026-10-09T10:43:02.461106263Z", "lastOk": true, "lastStatus": 404, "lastMs": 143, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 151, "p95ms24h": 194, "samples24h": 260, "samples30d": 2098, "days": [ { "date": "2026-10-01", "probes": 109, "ok": 109 }, { "date": "2026-10-02", "probes": 248, "ok": 248 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 272, "ok": 272 }, { "date": "2026-10-06", "probes": 272, "ok": 272 }, { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 114, "ok": 114 } ] }, "vendorStatus": { "page": "https://status.yapily.com", "indicator": "minor", "summary": "Partial System Degradation", "checkedAt": "2026-10-09T10:42:10.575103116Z" }, "versions": [ { "registry": "npm", "name": "@yapily/yapily-api", "version": "8.0.0", "seenAt": "2026-10-08T16:35:26.747544649Z" } ], "githubStars": 14, "npmWeekly": 22, "securityTxt": { "url": "https://yapily.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-08T15:38:35.811465168Z" }, "llmsTxt": { "url": "https://docs.yapily.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-08T14:01:01.322319474Z" }, "domain": { "domain": "yapily.com", "registered": "2018-01-23", "source": "https://rdap.verisign.com/com/v1/domain/yapily.com", "checkedAt": "2026-10-04T13:06:12.962175252Z" }, "pages": [ { "url": "https://www.yapily.com/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-10-08T18:31:48.693270296Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "c34d3588f2f9" }, { "url": "https://www.yapily.com/legal/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-08T18:31:44.605800531Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "64008fcb9142" }, { "url": "https://www.yapily.com/legal/website-terms-of-use", "kind": "terms", "status": 200, "checkedAt": "2026-10-08T18:31:46.688285246Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "ef27f376f484" } ], "updatedAt": "2026-10-09T10:43:02.461106263Z" } }, "answer": "Yapily scores 57.6 (C) on agent readiness against Yodlee Core API's 41.9 (E), and leads in 5 of 7 scored categories. Yodlee Core API leads on security \u0026 auth and payments \u0026 pricing.", "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": "Yapily", "b": "Yodlee, Inc.", "name": "Vendor" }, { "a": "https://api.yapily.com", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable 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": "MIT (SDKs)", "b": "Proprietary service. The Swagger file on GitHub is MIT", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "2025-06-30", "b": "2026-07-31", "name": "Last release" }, { "a": "2022-12-05", "b": "no document linked", "name": "Terms last updated" }, { "a": "no date given", "b": "no document linked", "name": "Privacy policy last updated" }, { "a": "yes", "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": "not found in the text", "b": "", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "", "name": "Arbitration or class-action waiver" }, { "a": "14 stars, 50 npm/wk", "b": "17 stars", "name": "Popularity" }, { "a": "2.5/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Yapily scores 57.6 (C) on agent readiness against Yodlee Core API's 41.9 (E), and leads in 5 of 7 scored categories. Yodlee Core API leads on security \u0026 auth and payments \u0026 pricing.", "question": "Which is better for AI agents, Yapily or Yodlee Core API?" }, { "answer": "Yapily needs an API key. Yodlee Core API uses an OAuth sign-in.", "question": "Do Yapily and Yodlee Core API need an API key?" }, { "answer": "Yapily has a hosted endpoint at https://api.yapily.com. No hosted endpoint is listed for Yodlee Core API.", "question": "Can an agent call Yapily and Yodlee Core API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 55 against 15", "Schema \u0026 documentation, 88 against 71", "Agent ergonomics, 77 against 58", "Maintenance \u0026 community, 67 against 33", "Transparency \u0026 trust, 71 against 53" ], "also": [ "A hosted endpoint, with nothing to install" ], "goodFor": "UK and EEA data and payments from one API, for builders who want docs an agent can read in one fetch.", "slug": "yapily", "watchFor": "No public pricing; live access starts with a sales form" }, { "aheadOn": [ "Security \u0026 auth, 49 against 37", "Payments \u0026 pricing, 15 against 10" ], "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-yapily.json", "title": "Akoya vs Yapily", "url": "https://www.anchorterminal.com/compare/akoya-vs-yapily" }, { "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-yapily.json", "title": "Belvo vs Yapily", "url": "https://www.anchorterminal.com/compare/belvo-vs-yapily" }, { "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-yapily.json", "title": "Enable Banking vs Yapily", "url": "https://www.anchorterminal.com/compare/enable-banking-vs-yapily" }, { "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-yapily.json", "title": "Flinks vs Yapily", "url": "https://www.anchorterminal.com/compare/flinks-vs-yapily" }, { "json": "https://www.anchorterminal.com/compare/flinks-vs-yodlee-financial-data.json", "title": "Flinks vs Yodlee Core API", "url": "https://www.anchorterminal.com/compare/flinks-vs-yodlee-financial-data" }, { "json": "https://www.anchorterminal.com/compare/gocardless-bank-account-data-vs-yapily.json", "title": "GoCardless Bank Account Data vs Yapily", "url": "https://www.anchorterminal.com/compare/gocardless-bank-account-data-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-yapily.json", "title": "MX Platform API vs Yapily", "url": "https://www.anchorterminal.com/compare/mx-vs-yapily" }, { "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-yapily.json", "title": "Plaid vs Yapily", "url": "https://www.anchorterminal.com/compare/plaid-vs-yapily" }, { "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-yapily.json", "title": "Salt Edge Account Information vs Yapily", "url": "https://www.anchorterminal.com/compare/salt-edge-vs-yapily" }, { "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-yapily.json", "title": "Teller vs Yapily", "url": "https://www.anchorterminal.com/compare/teller-vs-yapily" }, { "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-yapily.json", "title": "Tink vs Yapily", "url": "https://www.anchorterminal.com/compare/tink-vs-yapily" }, { "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-yapily.json", "title": "TrueLayer vs Yapily", "url": "https://www.anchorterminal.com/compare/truelayer-vs-yapily" }, { "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" } ], "scores": [ { "by": 40, "edge": "yapily", "key": "reliability", "name": "Reliability", "weight": 16, "yapily": 55, "yodlee-financial-data": 15 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 17, "edge": "yapily", "key": "schema", "name": "Schema \u0026 documentation", "weight": 13, "yapily": 88, "yodlee-financial-data": 71 }, { "by": 19, "edge": "yapily", "key": "ergonomics", "name": "Agent ergonomics", "weight": 13, "yapily": 77, "yodlee-financial-data": 58 }, { "by": 12, "edge": "yodlee-financial-data", "key": "security", "name": "Security \u0026 auth", "weight": 14, "yapily": 37, "yodlee-financial-data": 49 }, { "by": 5, "edge": "yodlee-financial-data", "key": "payments", "name": "Payments \u0026 pricing", "weight": 10, "yapily": 10, "yodlee-financial-data": 15 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 34, "edge": "yapily", "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7, "yapily": 67, "yodlee-financial-data": 33 }, { "by": 18, "edge": "yapily", "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7, "yapily": 71, "yodlee-financial-data": 53 } ], "summary": "Yapily scores 57.6 (C) on agent readiness against Yodlee Core API's 41.9 (E), and leads in 5 of 7 scored categories. Yodlee Core API leads on security \u0026 auth and payments \u0026 pricing. Both do bank accounts.", "verdicts": { "yapily": "llms.txt, llms-full.txt, a no-auth docs MCP server and an OpenAPI file. No public pricing; live access starts with a sales form.", "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/yapily-vs-yodlee-financial-data", "json": "https://www.anchorterminal.com/compare/yapily-vs-yodlee-financial-data.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/yapily-vs-yodlee-financial-data.md", "slim": "https://www.anchorterminal.com/compare/yapily-vs-yodlee-financial-data.min.md" }, "markdown": "Yapily scores 57.6 (C) on agent readiness against Yodlee Core API's 41.9 (E), and leads in 5 of 7 scored categories. Yodlee Core API leads on security \u0026 auth and payments \u0026 pricing. Both do bank accounts.\n\n- Yapily: grade C, 57.6/100, rank #543 of 842. Markdown https://www.anchorterminal.com/tools/yapily.md · JSON https://www.anchorterminal.com/api/v1/tools/yapily.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### Yapily (C)\n\nGood for: UK and EEA data and payments from one API, for builders who want docs an agent can read in one fetch.\n\nAhead on:\n- Reliability, 55 against 15\n- Schema \u0026 documentation, 88 against 71\n- Agent ergonomics, 77 against 58\n- Maintenance \u0026 community, 67 against 33\n- Transparency \u0026 trust, 71 against 53\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n\nWatch for: No public pricing; live access starts with a sales form\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\nAhead on:\n- Security \u0026 auth, 49 against 37\n- Payments \u0026 pricing, 15 against 10\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 | Yapily | Yodlee Core API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 55 | 15 | Yapily +40 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 88 | 71 | Yapily +17 |\n| Agent ergonomics | 13% (16.2 this run) | 77 | 58 | Yapily +19 |\n| Security \u0026 auth | 14% (17.5 this run) | 37 | 49 | Yodlee Core API +12 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 10 | 15 | Yodlee Core API +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 67 | 33 | Yapily +34 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 71 | 53 | Yapily +18 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **57.6 · C** | **41.9 · E** | |\n\n## Facts side by side\n\n| Fact | Yapily | Yodlee Core API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Yapily | Yodlee, Inc. |\n| Hosted endpoint | `https://api.yapily.com` | no (local only) |\n| Transports | HTTP, Streamable HTTP | HTTP |\n| Auth | API key | OAuth |\n| Pricing | Paid | Paid |\n| x402 | no | no |\n| Licence | MIT (SDKs) | Proprietary service. The Swagger file on GitHub is MIT |\n| Read-only variant documented | no | no |\n| llms.txt | yes | no |\n| Last release | 2025-06-30 | 2026-07-31 |\n| Terms last updated | 2022-12-05 | no document linked |\n| Privacy policy last updated | no date given | no document linked |\n| Customer content may train models | yes | |\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 | not found in the text | |\n| Arbitration or class-action waiver | not found in the text | |\n| Popularity | 14 stars, 50 npm/wk | 17 stars |\n| Agent reviews | 2.5/5 (2) | none |\n\n## Verdicts\n\n**Yapily.** llms.txt, llms-full.txt, a no-auth docs MCP server and an OpenAPI file. No public pricing; live access starts with a sales form.\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### Yapily\n\n1. Read llms-full.txt once and cache it; it's the whole documentation in one fetch\n2. Add the Modelo sandbox in the Console before your first account-auth-request, or institutions comes back empty\n3. Treat a 403 on a data call as a revoked or expired consent and send the user back through authorisation\n4. Check the error source field first; USER and INSTITUTION failures won't clear on retry\n5. In the UK, call extend-consent with lastConfirmedAt before the reconfirmBy date, or the consent lapses at 90 days\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, Yapily or Yodlee Core API?\n\nYapily scores 57.6 (C) on agent readiness against Yodlee Core API's 41.9 (E), and leads in 5 of 7 scored categories. Yodlee Core API leads on security \u0026 auth and payments \u0026 pricing.\n\n### Do Yapily and Yodlee Core API need an API key?\n\nYapily needs an API key. Yodlee Core API uses an OAuth sign-in.\n\n### Can an agent call Yapily and Yodlee Core API without installing anything?\n\nYapily has a hosted endpoint at https://api.yapily.com. 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/yapily-vs-yodlee-financial-data.json, and with the fewest tokens: https://www.anchorterminal.com/compare/yapily-vs-yodlee-financial-data.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"yapily\", \"b\": \"yodlee-financial-data\"}`. From a terminal: `anchor compare yapily yodlee-financial-data`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/yapily.json and https://www.anchorterminal.com/api/v1/tools/yodlee-financial-data.json\n\n## Other comparisons with Yapily or Yodlee Core API\n\n- [Akoya vs Yapily](https://www.anchorterminal.com/compare/akoya-vs-yapily.md)\n- [Akoya vs Yodlee Core API](https://www.anchorterminal.com/compare/akoya-vs-yodlee-financial-data.md)\n- [Belvo vs Yapily](https://www.anchorterminal.com/compare/belvo-vs-yapily.md)\n- [Belvo vs Yodlee Core API](https://www.anchorterminal.com/compare/belvo-vs-yodlee-financial-data.md)\n- [Enable Banking vs Yapily](https://www.anchorterminal.com/compare/enable-banking-vs-yapily.md)\n- [Enable Banking vs Yodlee Core API](https://www.anchorterminal.com/compare/enable-banking-vs-yodlee-financial-data.md)\n- [Flinks vs Yapily](https://www.anchorterminal.com/compare/flinks-vs-yapily.md)\n- [Flinks vs Yodlee Core API](https://www.anchorterminal.com/compare/flinks-vs-yodlee-financial-data.md)\n- [GoCardless Bank Account Data vs Yapily](https://www.anchorterminal.com/compare/gocardless-bank-account-data-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 Yapily](https://www.anchorterminal.com/compare/mx-vs-yapily.md)\n- [MX Platform API vs Yodlee Core API](https://www.anchorterminal.com/compare/mx-vs-yodlee-financial-data.md)\n- [Plaid vs Yapily](https://www.anchorterminal.com/compare/plaid-vs-yapily.md)\n- [Plaid vs Yodlee Core API](https://www.anchorterminal.com/compare/plaid-vs-yodlee-financial-data.md)\n- [Salt Edge Account Information vs Yapily](https://www.anchorterminal.com/compare/salt-edge-vs-yapily.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 Yapily](https://www.anchorterminal.com/compare/teller-vs-yapily.md)\n- [Teller vs Yodlee Core API](https://www.anchorterminal.com/compare/teller-vs-yodlee-financial-data.md)\n- [Tink vs Yapily](https://www.anchorterminal.com/compare/tink-vs-yapily.md)\n- [Tink vs Yodlee Core API](https://www.anchorterminal.com/compare/tink-vs-yodlee-financial-data.md)\n- [TrueLayer vs Yapily](https://www.anchorterminal.com/compare/truelayer-vs-yapily.md)\n- [TrueLayer vs Yodlee Core API](https://www.anchorterminal.com/compare/truelayer-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": "Yapily vs Yodlee Core API", "url": "" } ], "description": "Yapily scores 57.6 (C) on agent readiness against Yodlee Core API's 41.9 (E), and leads in 5 of 7 scored categories. Yodlee Core API leads on security \u0026 auth and payments \u0026 pricing. Both do bank accounts. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Yapily C 57.6", "Yodlee Core API E 41.9", "scores" ], "h1": "Yapily vs Yodlee Core API", "image": "https://www.anchorterminal.com/assets/og/compare-yapily-vs-yodlee-financial-data.png", "path": "/compare/yapily-vs-yodlee-financial-data", "published": "2026-10-01", "section": "tools", "title": "Yapily vs Yodlee Core API for AI agents, C 57.6 vs E 41.9", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/yapily-vs-yodlee-financial-data" }, "tokens": { "markdown": 2350, "slim": 680 }, "version": 1 }