{ "data": { "a": { "slug": "enable-banking", "name": "Enable Banking", "vendor": "Enable Banking", "vendorUrl": "https://enablebanking.com", "kind": "http-api", "category": "banking-data", "summary": "Finnish open banking API (FIN-FSA registered AISP) covering 2,700-plus banks in about 30 European countries, with account information and payment initiation under Enable Banking's licence or your own eIDAS certificates.", "url": "https://www.anchorterminal.com/tools/enable-banking", "markdownUrl": "https://www.anchorterminal.com/tools/enable-banking.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/enable-banking.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/enable-banking.json", "repo": "https://github.com/enablebanking/enablebanking-api-samples", "license": "Apache-2.0 (code samples)", "transports": [ "http" ], "remoteUrl": "https://api.enablebanking.com", "packages": [], "auth": "mixed", "authNotes": "Mint an RS256 JWT with the application's private key (kid is the application id, iss enablebanking.com, aud api.enablebanking.com, at most 24 hours) and send it as a Bearer token. The end user authorises at the bank through POST /auth, and the returned code becomes a session with POST /sessions. No client secret: the private key is the credential, so keep it in a secret store.", "pricing": "paid", "pricingNotes": "Volume-based on the number of accounts accessed and payments made a month, with a minimum monthly invoice that includes a quota of accounts and payments; figures on request from info@enablebanking.com (https://enablebanking.com/docs/faq/). You can create an account and use both the sandbox and production before signing a contract; a production application stays pending until the contract is done or you whitelist your own accounts, which activates it in restricted mode for those accounts only (https://enablebanking.com/docs/api/). Payment initiation in production is only switched on for companies holding a PISP licence.", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://enablebanking.com/docs/api/reference/", "capabilities": [ "bank.accounts", "bank.transactions", "bank.payments", "bank.consent" ], "tags": [ "hosted", "eu", "closed-source", "enterprise" ], "lastRelease": "2026-09-09", "graded": true, "anchor": { "graded": true, "score": 47.3, "grade": "D", "agentReady": false, "rank": 384, "ranked": true, "rankOf": 452, "categoryRank": 4, "methodology": "0.3", "run": "2026-10-01", "scores": { "ergonomics": 67, "maintenance": 67, "payments": 20, "reliability": 33, "schema": 54, "security": 47, "transparency": 51 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "Restricted mode gives live data for your own whitelisted accounts before any contract. No public prices and a minimum monthly invoice.", "strengths": [ "Restricted mode gives live data for your own whitelisted accounts before any contract", "Private-key JWT auth, at most 24 hours, with no shared secret on the wire", "continuation_key pagination with date and status filters on transactions", "DELETE /sessions closes the bank consent where the bank allows", "Monthly changelog posts, the newest on 9 September 2026" ], "weaknesses": [ "No public prices and a minimum monthly invoice", "No public status page; bank disruptions sit behind the Control Panel login", "No OpenAPI file, llms.txt or official SDK, only samples", "No public terms, security.txt, disclosure policy or certification found", "No idempotency guidance for payments" ], "agentNotes": [ "Mint one JWT per run with exp under 24 hours; don't reuse a long-lived token across sessions", "Test against the Mock ASPSP first; bank sandboxes fail for reasons that aren't yours", "Pass the bank's maximum_consent_validity as valid_until, usually 180 days, or you'll be back at the bank sooner", "On 429 ASPSP_RATE_LIMIT_EXCEEDED stop until tomorrow; it's the bank's 4-a-day cap", "Follow continuation_key until it's absent to get every transaction" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.3", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 47.3 } ], "editorialScores": { "ergonomics": 67, "maintenance": 67, "payments": 20, "reliability": 33, "schema": 54, "security": 47, "transparency": 35 }, "provenanceScore": 66 }, "connect": { "http": "curl \"https://api.enablebanking.com/aspsps?country=FI\" -H \"Authorization: Bearer $ENABLE_BANKING_JWT\"" }, "letme": { "capability": "https://letme.dev/bank.accounts", "tool": "https://letme.dev/enable-banking" }, "area": "domain-data", "provenance": { "legalEntity": "Enable Banking", "domain": "enablebanking.com", "domainRegistered": "2018-04-23", "endpointOnVendorDomain": true, "terms": "", "privacy": "https://enablebanking.com/privacy-policy", "statusPage": "", "changelog": "https://enablebanking.com/blog", "securityTxt": "none", "checked": "2026-09-30", "notes": [ "The home page describes the company as a registered Account Information Service Provider regulated by the Finnish Financial Supervisory Authority (FIN-FSA). The privacy policy page renders only with JavaScript, so we couldn't read the registered company name or business ID from it.", "No terms of service page was found; the FAQ refers to a contract agreed by email.", "The blog carries monthly changelog posts; there's no status page we could find.", "rdap.org returned 403; the registration date is from Verisign's RDAP server." ], "score": 66 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/enable-banking.json", "live": { "slug": "enable-banking", "probe": { "target": "https://api.enablebanking.com", "method": "get", "lastAt": "2026-10-04T23:32:46.924906174Z", "lastOk": true, "lastStatus": 200, "lastMs": 372, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 389, "p95ms24h": 754, "samples24h": 272, "samples30d": 895, "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": 267, "ok": 267 } ] }, "githubStars": 68, "securityTxt": { "url": "https://enablebanking.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-04T15:15:55.325774876Z" }, "domain": { "domain": "enablebanking.com", "registered": "2018-04-23", "source": "https://rdap.verisign.com/com/v1/domain/enablebanking.com", "checkedAt": "2026-10-04T13:08:31.314512732Z" }, "pages": [ { "url": "https://enablebanking.com/blog", "kind": "changelog", "status": 200, "checkedAt": "2026-10-04T15:44:28.095932355Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "04abb839753e" }, { "url": "https://enablebanking.com/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-04T15:44:30.341971538Z", "changedAt": "2026-10-04T15:44:30.341971538Z", "fingerprint": "b89c0791c950" } ], "updatedAt": "2026-10-04T23:32:46.924906174Z" } }, "b": { "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.8, "grade": "C", "agentReady": false, "rank": 289, "ranked": true, "rankOf": 452, "categoryRank": 3, "methodology": "0.3", "run": "2026-10-01", "scores": { "ergonomics": 77, "maintenance": 67, "payments": 10, "reliability": 55, "schema": 88, "security": 37, "transparency": 73 }, "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.", "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.3", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 57.8 } ], "editorialScores": { "ergonomics": 77, "maintenance": 67, "payments": 10, "reliability": 55, "schema": 88, "security": 37, "transparency": 70 }, "provenanceScore": 76 }, "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": 76 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/yapily.json", "live": { "slug": "yapily", "probe": { "target": "https://api.yapily.com", "method": "get", "lastAt": "2026-10-04T23:32:56.940054241Z", "lastOk": true, "lastStatus": 404, "lastMs": 134, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 146, "p95ms24h": 209, "samples24h": 272, "samples30d": 895, "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": 267, "ok": 267 } ] }, "vendorStatus": { "page": "https://status.yapily.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-04T23:28:05.959939127Z" }, "versions": [ { "registry": "npm", "name": "@yapily/yapily-api", "version": "8.0.0", "seenAt": "2026-10-04T16:44:27.614147653Z" } ], "githubStars": 14, "npmWeekly": 19, "securityTxt": { "url": "https://yapily.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-04T15:15:37.454228203Z" }, "llmsTxt": { "url": "https://docs.yapily.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-04T15:18:22.576942898Z" }, "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-04T15:53:02.956957213Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "c34d3588f2f9" }, { "url": "https://www.yapily.com/legal/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-04T15:52:58.881384464Z", "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-04T15:53:00.962218068Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "ef27f376f484" } ], "updatedAt": "2026-10-04T23:32:56.940054241Z" } }, "summary": "Yapily has a score of 57.8 (C) against Enable Banking's 47.3 (D). Both do bank accounts. The largest gap is schema \u0026 documentation, 34 points." }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/enable-banking-vs-yapily", "json": "https://www.anchorterminal.com/compare/enable-banking-vs-yapily.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/enable-banking-vs-yapily.md", "slim": "https://www.anchorterminal.com/compare/enable-banking-vs-yapily.min.md" }, "markdown": "Yapily has a score of 57.8 (C) against Enable Banking's 47.3 (D). Both do bank accounts. The largest gap is schema \u0026 documentation, 34 points.\n\n- Enable Banking: grade D, 47.3/100, rank #384 of 452. Markdown https://www.anchorterminal.com/tools/enable-banking.md · JSON https://www.anchorterminal.com/api/v1/tools/enable-banking.json\n- Yapily: grade C, 57.8/100, rank #289 of 452. Markdown https://www.anchorterminal.com/tools/yapily.md · JSON https://www.anchorterminal.com/api/v1/tools/yapily.json\n\n## Which one, for what\n\nPick Enable Banking for security \u0026 auth (+10), payments \u0026 pricing (+10).\n\nPick Yapily for reliability (+22), schema \u0026 documentation (+34), agent ergonomics (+10), transparency \u0026 trust (+22).\n\n## Score by category\n\n| Category | Weight | Enable Banking | Yapily | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 33 | 55 | Yapily +22 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 54 | 88 | Yapily +34 |\n| Agent ergonomics | 13% (16.2 this run) | 67 | 77 | Yapily +10 |\n| Security \u0026 auth | 14% (17.5 this run) | 47 | 37 | Enable Banking +10 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 10 | Enable Banking +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 67 | 67 | even |\n| Transparency \u0026 trust | 7% (8.8 this run) | 51 | 73 | Yapily +22 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **47.3 · D** | **57.8 · C** | |\n\n## Facts side by side\n\n| Fact | Enable Banking | Yapily |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Enable Banking | Yapily |\n| Hosted endpoint | `https://api.enablebanking.com` | `https://api.yapily.com` |\n| Transports | HTTP | HTTP, Streamable HTTP |\n| Auth | OAuth or key | API key |\n| Pricing | Paid | Paid |\n| x402 | no | no |\n| Licence | Apache-2.0 (code samples) | MIT (SDKs) |\n| Tools exposed | none | none |\n| Context cost (tools/list) | n/a | n/a |\n| p95 latency | not measured yet | not measured yet |\n| Availability (30d) | not measured yet | not measured yet |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| MCP registry | not listed | not listed |\n| Last release | 2026-09-09 | 2025-06-30 |\n| Popularity | none | 14 stars, 50 npm/wk |\n| Agent reviews | 3/5 (2) | 2.5/5 (2) |\n\n## Verdicts\n\n**Enable Banking.** Restricted mode gives live data for your own whitelisted accounts before any contract. No public prices and a minimum monthly invoice.\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## Before you call either\n\n### Enable Banking\n\n1. Mint one JWT per run with exp under 24 hours; don't reuse a long-lived token across sessions\n2. Test against the Mock ASPSP first; bank sandboxes fail for reasons that aren't yours\n3. Pass the bank's maximum_consent_validity as valid_until, usually 180 days, or you'll be back at the bank sooner\n4. On 429 ASPSP_RATE_LIMIT_EXCEEDED stop until tomorrow; it's the bank's 4-a-day cap\n5. Follow continuation_key until it's absent to get every transaction\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## Other comparisons with Enable Banking or Yapily\n\n- [Enable Banking vs GoCardless Bank Account Data](https://www.anchorterminal.com/compare/enable-banking-vs-gocardless-bank-account-data.md)\n- [Enable Banking vs Plaid](https://www.anchorterminal.com/compare/enable-banking-vs-plaid.md)\n- [Enable Banking vs Salt Edge Account Information](https://www.anchorterminal.com/compare/enable-banking-vs-salt-edge.md)\n- [Enable Banking vs Teller](https://www.anchorterminal.com/compare/enable-banking-vs-teller.md)\n- [Enable Banking vs TrueLayer](https://www.anchorterminal.com/compare/enable-banking-vs-truelayer.md)\n- [GoCardless Bank Account Data vs Yapily](https://www.anchorterminal.com/compare/gocardless-bank-account-data-vs-yapily.md)\n- [Plaid vs Yapily](https://www.anchorterminal.com/compare/plaid-vs-yapily.md)\n- [Salt Edge Account Information vs Yapily](https://www.anchorterminal.com/compare/salt-edge-vs-yapily.md)\n- [Teller vs Yapily](https://www.anchorterminal.com/compare/teller-vs-yapily.md)\n- [TrueLayer vs Yapily](https://www.anchorterminal.com/compare/truelayer-vs-yapily.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-04", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.3", "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": "Enable Banking vs Yapily", "url": "" } ], "description": "Yapily has a score of 57.8 (C) against Enable Banking's 47.3 (D). Both do bank accounts. The largest gap is schema \u0026 documentation, 34 points. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Enable Banking D 47.3", "Yapily C 57.8", "scores" ], "h1": "Enable Banking vs Yapily", "image": "https://www.anchorterminal.com/assets/og/compare-enable-banking-vs-yapily.png", "path": "/compare/enable-banking-vs-yapily", "published": "2026-10-01", "section": "tools", "title": "Enable Banking vs Yapily for AI agents, D 47.3 vs C 57.8", "toc": null, "updated": "2026-10-04", "url": "https://www.anchorterminal.com/compare/enable-banking-vs-yapily" }, "tokens": { "markdown": 1400, "slim": 330 }, "version": 1 }