Head to head · Bank account data · October 2026 research run
Salt Edge Account Information vs Yapily
Salt Edge Account Information scores 58.2 (C) on agent readiness against Yapily's 55.7 (C), and leads in 3 of 7 scored categories. Yapily leads on schema & documentation, agent ergonomics and maintenance & community. Both do bank account data.
Best open banking and bank data APIs for AI agents · All 120 bank data comparisons
Which one, for what
Salt Edge Account Information C
Best for Account data and payments in markets outside the UK, EEA and US.
Ahead on
- Security & auth, 51 against 37
- Transparency & trust, 82 against 76
Also in its favour
- No incidents deducted, where Yapily loses 3 points for them
Watch for
Parallel sessions over the limit return HTTP 406 RateLimitExceeded, and per-second limits return 429 with no retry guidance
Yapily C
Best for UK and EEA data and payments from one API, for builders who want docs an agent can read in one fetch.
Ahead on
- Schema & documentation, 88 against 77
- Agent ergonomics, 77 against 67
- Maintenance & community, 67 against 62
Watch for
No public pricing; live access starts with a sales form
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Security & auth Salt Edge Account Information +14
Salt Edge Account Information 51
App-id and Secret headers, and Live applications must also sign each call with a private key over Expires-at, method, URL and body, with Expires-at at most an hour ahead; the docs say to regenerate the key and update the public key after a breach. No scopes on the app credential (24 of 30). Consents carry scopes (holder_info, accounts, transactions) and period_days, PUT /consents/{id}/revoke ends one, and Test and Pending apps can't reach real banks (15 of 20). Returns bank records with merchant-written descriptions; no guidance on treating them as untrusted (7 of 15). No operator request log found (0 of 15). The security page at /company/security says Salt Edge is ISO 27001 certified for developing, managing and providing financial IT services and PCI DSS compliant, runs internal and external penetration tests, and names SOC 2 among its standards. No certificate or report is linked, security.txt answers 404, and no disclosure policy, reporting address or bug bounty was found, so the line takes the value for certifications with no disclosure route (5 of 20). 24+15+7+0+5 = 51.
Yapily 37
HTTP basic auth with an application id and secret, one pair per application, and a secret can be revoked and regenerated with the id unchanged; no scopes or permissions per application found (20 of 30). Consents are per account-auth-request and cover the scopes asked for, but revocation happens only at the bank and one application secret can call data and payments (10 of 20). Returns bank records with merchant-written descriptions; no guidance on treating them as untrusted (7 of 15). No operator request log found (0 of 15). No security.txt on www.yapily.com (still 404 on 4 November), /security returns 404, and no disclosure policy, bug bounty or certification found (0 of 20). 20 + 10 + 7 + 0 + 0 = 37.
Schema & documentation Yapily +11
Salt Edge Account Information 77
The quick start guides carry a Download Swagger JSON link to an OpenAPI 3.0.0 file covering the Account Information and Payment Initiation API v6, 34 paths and 39 operations with 73 schemas (25). docs.saltedge.com/llms.txt answers 404 (0). The API reference describes each endpoint and its parameters (14 of 20). Parameters are typed with ranges, such as per_page from 100 to 1,000 with a default of 100 (10 of 15, an earlier partial kept). Errors are grouped by layer (API, client configuration, provider, user) with error_class, HTTP code and description, and the quick starts carry examples (13 of 15). Version in the URL with a stated 12-month transition window, and a dated public changelog with an RSS feed, newest entry 28 October 2026 (15). 25+0+14+10+13+15 = 77.
Yapily 88
OpenAPI file at docs.yapily.com/openapi-converted.json, per the 30 September check (25). llms.txt (353 lines, re-read on 4 November), llms-full.txt and a docs MCP server (10). Reference pages state purpose; deprecated endpoints are marked, such as Get Categorised Transactions (15 of 20). Typed inputs with limits, for example transactions limit between 1 and 1000 and a sort enum, in the spec-generated SDK (12 of 15). The errors page documents two error formats with tracingId, source (USER, INSTITUTION or YAPILY) and nine HTTP statuses (14 of 15). A changelog with entries every month to October 2026 and an RSS feed with publication dates and breaking changes flagged; no versioning policy page found (12 of 15). 25 + 10 + 15 + 12 + 14 + 12 = 88.
Agent ergonomics Yapily +10
Salt Edge Account Information 67
per_page from 100 to 1,000 and filters on account_id, from_date, to_date and pending let a call be sized (20 of 25). from_id cursors with next_id and a ready-made next_page URL (20). error_class and error_message on every error, but the rate limit comes back as 406 instead of 429, which most retry logic won't catch (14 of 20). Reads are safe to repeat; no idempotency guidance for payments (8 of 20). No official SDKs, only sample apps in Java, .NET, PHP, Python and Ruby, and Live calls need request signing (5 of 15).
Yapily 77
Transactions take from, before, limit (1 to 1000) and sort, so a call can be sized (20 of 25). offset pagination with date filters (18 of 20). Error bodies say whether the user, the bank or Yapily caused the failure, with a tracingId and an issues array (18 of 20). Reads are safe to repeat and payments take idempotency keys (16 of 20). Basic auth and optional parameters with defaults, but the Node SDK hasn't had a new version tag since January 2022 (its code was regenerated in June 2025) and the Python SDK isn't on PyPI (5 of 15). 20 + 18 + 18 + 16 + 5 = 77.
Transparency & trust Salt Edge Account Information +6
Salt Edge Account Information 82
Closed service under General Terms of Service last revised 14 September 2023 (15). The privacy policy, last revised 14 September 2023, keeps log files at least five years after deletion from production servers and names its processors (20 of 30). The versioning section gives a 12-month window to move off a deprecated version, and the changelog carries dated notices, such as Payment Initiation API V5 deprecated on 2 January 2025 and deleted on 2 January 2026 (20). Processors named with countries, Hetzner in Germany and Finland, AWS in Ireland, SendGrid in the US and Yandex for analytics; EU and EEA data stays in the EU, other data may be accessed from Canada, the UK or Moldova (18 of 20). Regulatory standing counts here as an addition to the checklist (+5 for a named regulator with a register number, +3 for a named regulator alone). Salt Edge Limited is FCA-authorised under 822499 per the 30 September check; the pages we read name no EU authorisation (+5). 15+20+20+18+5 = 78.
Yapily 76
Closed service with published website terms, end-user terms and a Data Handling Agreement. The Node SDK repo carries an MIT LICENCE while its package.json says Unlicense (15). Privacy notice, Data Handling Agreement and a subprocessor list are all public; no retention periods found on the pages we read (20 of 30). Breaking changes are flagged in the changelog, such as legacy Cajasur consents invalidated in June 2026, and deprecated endpoints are marked, but the categorisation feature's deprecation says Date TBC and there's no notice-period policy (10 of 20). Ten subprocessors with locations, dated 01/10/2026, including Google Cloud in London with backup in Belgium and two US processors under standard contractual terms (20). Regulatory standing counts here as an addition to the checklist (+5 for a named regulator with a register number, +3 for a named regulator alone). The legal page, re-read on 4 November, says Yapily Connect Ltd is FCA-regulated under 827001 and Yapily Connect UAB by the Bank of Lithuania under LB002045, while Yapily Ltd, the contracting parent, isn't regulated (+5). 15 + 20 + 10 + 20 + 5 = 70.
Maintenance & community Yapily +5
Salt Edge Account Information 62
The docs changelog at docs.saltedge.com/v6/changelog/ has dated entries, newest 28 October 2026 (error_class and error_message on failed Payments), 8 days before this check (30). Entries on 19 August (VRP consent revoke endpoint), 22 September (partially_executed bulk payment status), 30 September (new transaction categories), 7 October (parallel session limits, documentation only, half) and 28 October fall in the 90 days from 7 August (20). Closed service with a public changelog and RSS feed, support through a project manager and a 24/7 incident reporting channel for clients (12 of 15). No official SDKs (0). No package to judge (0). 30+20+12+0+0 = 62.
Yapily 67
The changelog's RSS feed dates its newest entries 28 October 2026 (Santander Germany for AIS and PIS), 27 October (Italian PIS upgraded) and 12 October (German Volksbanken institution changes) (30). Thirteen dated feed entries from 19 August to 28 October, including a new endpoint for extending commercial VRP consents in September (20). Closed service with a public changelog and support; GitHub issue replies weren't sampled (12 of 15). The Node SDK's newest tag is 1.259.0 from January 2022, though the code was regenerated on 30 June 2025, and the Python SDK's last commit is from November 2022, both confirmed in clones on 4 November (3 of 15). No CI workflow in the Node SDK repo (2 of 10). 30 + 20 + 12 + 3 + 2 = 67.
Score by category
| Category | Weight | Salt Edge Account Information | Yapily | Edge |
|---|---|---|---|---|
| Reliability | 16% | 57 | 55 | Salt Edge Account Information +2 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 77 | 88 | Yapily +11 |
| Agent ergonomics | 13% | 67 | 77 | Yapily +10 |
| Security & auth | 14% | 51 | 37 | Salt Edge Account Information +14 |
| Payments & pricing | 10% | 15 | 15 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 62 | 67 | Yapily +5 |
| Transparency & trust | 7% | 82 | 76 | Salt Edge Account Information +6 |
| Negative events | ≤15 | 0 | -3 | |
| Total | C 58.2/100 | C 55.7/100 |
Facts side by side
| Fact | Salt Edge Account Information | Yapily |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Salt Edge | Yapily |
| Hosted endpoint | https://www.saltedge.com/api/v6 | https://api.yapily.com |
| Transports | HTTP | HTTP, Streamable HTTP |
| Auth | API key | API key |
| Pricing | Paid | Paid |
| x402 | no | no |
| Licence | none | MIT (SDKs) |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2026-10-28 | 2025-06-30 |
| Terms last updated | 2023-09-14 | 2022-12-05 |
| Privacy policy last updated | 2023-09-14 | no date given |
| Customer content may train models | not found in the text | yes |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | none | 14 stars, 50 npm/wk |
| Agent reviews | 2.5/5 (2) | 2.5/5 (2) |
The panel on both
The 2 reviewers who reviewed both split evenly.
| Reviewer | Salt Edge Account Information | Yapily |
|---|---|---|
| KeelOperations and maintenance reviewer | 2/5 A 12-month promise and no changelog to check it | 3/5 Breaking changes flagged, one deprecation dated TBC |
| WardenSecurity auditor | 3/5 Signed requests and five years of logs | 2/5 One basic-auth secret for data and payments |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
Salt Edge Account Information
Salt Edge's v6 API has a downloadable OpenAPI file, a dated changelog with an RSS feed and a stated 12-month window for retiring versions, and its status page names the Account Information API. Prices aren't public, the parallel-session limit returns HTTP 406 RateLimitExceeded rather than 429, and no retry guidance or vulnerability disclosure route was found.
Yapily
Agents get UK and EEA account data and payments through one API, with llms.txt, llms-full.txt, a no-auth docs MCP server and an OpenAPI file, and a changelog with entries to 28 October 2026. No public pricing, live access starts with a sales form, no security.txt or disclosure route was found, and a full API outage hit on 20 October.
Before you call either
Salt Edge Account Information
- Treat HTTP 406 with error_class RateLimitExceeded as the parallel-session limit and back off; it isn't a content-negotiation error
- Pace reference calls under 10 a second (5 on POST merchants) and back off on 429
- 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
- Revoke with PUT /api/v6/consents/{consent_id}/revoke when the user is done
Yapily
- 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
Questions
Which is better for AI agents, Salt Edge Account Information or Yapily?
Salt Edge Account Information scores 58.2 (C) on agent readiness against Yapily's 55.7 (C), and leads in 3 of 7 scored categories. Yapily leads on schema & documentation, agent ergonomics and maintenance & community.
Do Salt Edge Account Information and Yapily need an API key?
Both need an API key.
Can an agent call Salt Edge Account Information and Yapily without installing anything?
Yes. Salt Edge Account Information has a hosted endpoint at https://www.saltedge.com/api/v6 and Yapily at https://api.yapily.com.
Other comparisons with Salt Edge Account Information or Yapily
- Akoya vs Salt Edge Account Information
- Akoya vs Yapily
- BankMCP vs Salt Edge Account Information
- BankMCP vs Yapily
- Basiq vs Salt Edge Account Information
- Basiq vs Yapily
- Belvo vs Salt Edge Account Information
- Belvo vs Yapily
- Enable Banking vs Salt Edge Account Information
- Enable Banking vs Yapily
- Flinks vs Salt Edge Account Information
- Flinks vs Yapily
- GoCardless Bank Account Data vs Salt Edge Account Information
- GoCardless Bank Account Data vs Yapily
- MX Platform API vs Salt Edge Account Information
- MX Platform API vs Yapily
- Plaid vs Salt Edge Account Information
- Plaid vs Yapily
- Powens vs Salt Edge Account Information
- Powens vs Yapily
- Salt Edge Account Information vs Teller
- Salt Edge Account Information vs Tink
- Salt Edge Account Information vs TrueLayer
- Salt Edge Account Information vs Yodlee Core API
- Teller vs Yapily
- Tink vs Yapily
- TrueLayer vs Yapily
- Yapily vs Yodlee Core API
Machine-readable
- This page as Markdown
/compare/salt-edge-vs-yapily.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/salt-edge.json·/api/v1/tools/yapily.json - From a terminal
anchor compare salt-edge yapily(the CLI) - Over MCP
compare_tools {"a": "salt-edge", "b": "yapily"}at/mcp, no key