{ "data": { "a": { "slug": "salt-edge", "name": "Salt Edge Account Information", "vendor": "Salt Edge", "vendorUrl": "https://www.saltedge.com", "kind": "http-api", "category": "banking-data", "summary": "Open banking aggregator for account data and payments across international banks.", "url": "https://www.anchorterminal.com/tools/salt-edge", "markdownUrl": "https://www.anchorterminal.com/tools/salt-edge.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/salt-edge.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/salt-edge.json", "transports": [ "http" ], "remoteUrl": "https://www.saltedge.com/api/v6", "packages": [], "auth": "api-key", "authNotes": "Every request carries App-id and Secret headers from the dashboard. Live applications must also sign requests, with an Expires-at header (UNIX time, at most an hour ahead) and a Signature header, the base64 SHA256 signature of `Expires-at|method|url|body` made with your private key. Test and Pending applications can skip signing. End users authorise through the Connect widget at a connect_url you create per customer.", "pricing": "paid", "pricingNotes": "No price list. The pricing page returns 404 and the product page points at the dashboard sign-up and a sales form (https://www.saltedge.com/products/account_information). A new dashboard application is in Test status and can only connect to Fake providers and bank sandboxes; moving to Live needs approval, after which rate limits for parallel connections are agreed with a project manager (https://docs.saltedge.com/v6/api_reference).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://docs.saltedge.com/v6/", "capabilities": [ "bank.accounts", "bank.transactions", "bank.identity", "bank.payments", "bank.consent" ], "tags": [ "hosted", "uk", "eu", "closed-source", "enterprise", "webhooks" ], "graded": true, "anchor": { "graded": true, "score": 46.9, "grade": "D", "agentReady": false, "rank": 393, "ranked": true, "rankOf": 452, "categoryRank": 5, "methodology": "0.3", "run": "2026-10-01", "scores": { "ergonomics": 67, "maintenance": 13, "payments": 10, "reliability": 52, "schema": 52, "security": 46, "transparency": 77 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "5,000-plus banks in more than 50 countries, by Salt Edge's own count. Rate limit exceeded returns HTTP 406 RateLimitExceeded, not 429.", "strengths": [ "5,000-plus banks in more than 50 countries, by Salt Edge's own count", "per_page up to 1,000, from_id cursors and filters on account, dates and pending", "Consent scopes and period_days, with PUT /consents/{id}/revoke to end one", "Fake providers for password, OAuth and SMS flows, plus your own CSV data", "Privacy policy names its processors and countries and keeps EU data in the EU" ], "weaknesses": [ "Rate limit exceeded returns HTTP 406 RateLimitExceeded, not 429", "No public pricing; parallel connection limits are negotiated", "No official SDKs, OpenAPI file, llms.txt or changelog", "No security.txt, security page, disclosure policy or certification found", "Status history readable only for the last fortnight; the JSON feed is blocked by robots.txt" ], "agentNotes": [ "Treat HTTP 406 with error_class RateLimitExceeded as a rate limit and back off; it isn't a content-negotiation error", "Start with fakebank_simple_xf in country XF; it needs no bank sandbox", "Sign requests from the start even in Test, so the move to Live doesn't change your client", "Follow next_page from the meta block rather than building from_id URLs yourself", "Revoke with PUT /api/v6/consents/{consent_id}/revoke when the user is done" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 2.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.3", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 46.9 } ], "editorialScores": { "ergonomics": 67, "maintenance": 13, "payments": 10, "reliability": 52, "schema": 52, "security": 46, "transparency": 73 }, "provenanceScore": 80 }, "connect": { "http": "curl https://www.saltedge.com/api/v6/countries -H \"App-id: $SALTEDGE_APP_ID\" -H \"Secret: $SALTEDGE_SECRET\" -H \"Accept: application/json\"" }, "letme": { "capability": "https://letme.dev/bank.accounts", "tool": "https://letme.dev/salt-edge" }, "area": "domain-data", "provenance": { "legalEntity": "Salt Edge Limited", "domain": "saltedge.com", "domainRegistered": "2013-12-16", "endpointOnVendorDomain": true, "terms": "https://www.saltedge.com/legal/terms_of_service", "privacy": "https://www.saltedge.com/legal/privacy_policy", "statusPage": "https://www.saltedgestatus.com/", "changelog": "", "securityTxt": "none", "checked": "2026-10-01", "notes": [ "Salt Edge Limited, registered in England and Wales, company 11178811, FCA 822499, is a subsidiary of Salt Edge Inc., which the privacy policy places in Canada, with offices in Canada, the UK and Moldova.", "The privacy policy was last updated 14 September 2023.", "The domain's registration expires 2026-12-16 per Verisign's RDAP record in the 30 September check; rdap.org returned 403.", "www.saltedge.com/.well-known/security.txt returned 404 in the 30 September check, and www.saltedge.com/security returns 404.", "No changelog found; product news appears on blog.saltedge.com." ], "score": 80 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/salt-edge.json", "live": { "slug": "salt-edge", "probe": { "target": "https://www.saltedge.com/api/v6", "method": "get", "lastAt": "2026-10-04T23:32:54.049263589Z", "lastOk": true, "lastStatus": 404, "lastMs": 107, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 116, "p95ms24h": 196, "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://www.saltedgestatus.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-04T23:28:01.946521615Z" }, "securityTxt": { "url": "https://saltedge.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-04T15:15:50.514458459Z" }, "domain": { "domain": "saltedge.com", "registered": "2013-12-16", "source": "https://rdap.verisign.com/com/v1/domain/saltedge.com", "checkedAt": "2026-10-04T13:05:42.743352908Z" }, "pages": [ { "url": "https://www.saltedge.com/legal/privacy_policy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-04T15:52:03.768552244Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "98095fe138d1" }, { "url": "https://www.saltedge.com/legal/terms_of_service", "kind": "terms", "status": 200, "checkedAt": "2026-10-04T15:52:05.993380052Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "d4d5435c5ee6" } ], "updatedAt": "2026-10-04T23:32:54.049263589Z" } }, "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 Salt Edge Account Information's 46.9 (D). Both do bank accounts. The largest gap is maintenance \u0026 community, 54 points." }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/salt-edge-vs-yapily", "json": "https://www.anchorterminal.com/compare/salt-edge-vs-yapily.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/salt-edge-vs-yapily.md", "slim": "https://www.anchorterminal.com/compare/salt-edge-vs-yapily.min.md" }, "markdown": "Yapily has a score of 57.8 (C) against Salt Edge Account Information's 46.9 (D). Both do bank accounts. The largest gap is maintenance \u0026 community, 54 points.\n\n- Salt Edge Account Information: grade D, 46.9/100, rank #393 of 452. Markdown https://www.anchorterminal.com/tools/salt-edge.md · JSON https://www.anchorterminal.com/api/v1/tools/salt-edge.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 Salt Edge Account Information for security \u0026 auth (+9).\n\nPick Yapily for schema \u0026 documentation (+36), agent ergonomics (+10), maintenance \u0026 community (+54).\n\n## Score by category\n\n| Category | Weight | Salt Edge Account Information | Yapily | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 52 | 55 | Yapily +3 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 52 | 88 | Yapily +36 |\n| Agent ergonomics | 13% (16.2 this run) | 67 | 77 | Yapily +10 |\n| Security \u0026 auth | 14% (17.5 this run) | 46 | 37 | Salt Edge Account Information +9 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 10 | 10 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 13 | 67 | Yapily +54 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 77 | 73 | Salt Edge Account Information +4 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **46.9 · D** | **57.8 · C** | |\n\n## Facts side by side\n\n| Fact | Salt Edge Account Information | Yapily |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Salt Edge | Yapily |\n| Hosted endpoint | `https://www.saltedge.com/api/v6` | `https://api.yapily.com` |\n| Transports | HTTP | HTTP, Streamable HTTP |\n| Auth | API key | API key |\n| Pricing | Paid | Paid |\n| x402 | no | no |\n| Licence | none | 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 | none | 2025-06-30 |\n| Popularity | none | 14 stars, 50 npm/wk |\n| Agent reviews | 2.5/5 (2) | 2.5/5 (2) |\n\n## Verdicts\n\n**Salt Edge Account Information.** 5,000-plus banks in more than 50 countries, by Salt Edge's own count. Rate limit exceeded returns HTTP 406 RateLimitExceeded, not 429.\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### Salt Edge Account Information\n\n1. Treat HTTP 406 with error_class RateLimitExceeded as a rate limit and back off; it isn't a content-negotiation error\n2. Start with fakebank_simple_xf in country XF; it needs no bank sandbox\n3. Sign requests from the start even in Test, so the move to Live doesn't change your client\n4. Follow next_page from the meta block rather than building from_id URLs yourself\n5. Revoke with PUT /api/v6/consents/{consent_id}/revoke when the user is done\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 Salt Edge Account Information or Yapily\n\n- [Enable Banking vs Salt Edge Account Information](https://www.anchorterminal.com/compare/enable-banking-vs-salt-edge.md)\n- [Enable Banking vs Yapily](https://www.anchorterminal.com/compare/enable-banking-vs-yapily.md)\n- [GoCardless Bank Account Data vs Salt Edge Account Information](https://www.anchorterminal.com/compare/gocardless-bank-account-data-vs-salt-edge.md)\n- [GoCardless Bank Account Data vs Yapily](https://www.anchorterminal.com/compare/gocardless-bank-account-data-vs-yapily.md)\n- [Plaid vs Salt Edge Account Information](https://www.anchorterminal.com/compare/plaid-vs-salt-edge.md)\n- [Plaid vs Yapily](https://www.anchorterminal.com/compare/plaid-vs-yapily.md)\n- [Salt Edge Account Information vs Teller](https://www.anchorterminal.com/compare/salt-edge-vs-teller.md)\n- [Salt Edge Account Information vs TrueLayer](https://www.anchorterminal.com/compare/salt-edge-vs-truelayer.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": "Salt Edge Account Information vs Yapily", "url": "" } ], "description": "Yapily has a score of 57.8 (C) against Salt Edge Account Information's 46.9 (D). Both do bank accounts. The largest gap is maintenance \u0026 community, 54 points. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Salt Edge Account Information D 46.9", "Yapily C 57.8", "scores" ], "h1": "Salt Edge Account Information vs Yapily", "image": "https://www.anchorterminal.com/assets/og/compare-salt-edge-vs-yapily.png", "path": "/compare/salt-edge-vs-yapily", "published": "2026-10-01", "section": "tools", "title": "Salt Edge Account Information vs Yapily for AI agents", "toc": null, "updated": "2026-10-04", "url": "https://www.anchorterminal.com/compare/salt-edge-vs-yapily" }, "tokens": { "markdown": 1400, "slim": 330 }, "version": 1 }