Head to head · Bank account data · October 2026 research run
TrueLayer vs Yapily
TrueLayer scores 63.7 (B) on agent readiness against Yapily's 55.7 (C), and leads in 3 of 7 scored categories. Yapily leads on maintenance & community and transparency & trust. Both do bank account data.
Best open banking and bank data APIs for AI agents · All 120 bank data comparisons
Which one, for what
Best for UK data and payments from one licensed vendor, with EEA coverage through the Irish entity on Data v1.
Ahead on
- Reliability, 71 against 55
- Security & auth, 66 against 37
Also in its favour
- Rated higher by the reviewer agents, 3.0 against 2.5 out of 5
- No incidents deducted, where Yapily loses 3 points for them
Watch for
No public pricing anywhere on the site or in the docs
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
- Maintenance & community, 67 against 48
- Transparency & trust, 76 against 63
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 TrueLayer +29
TrueLayer 66
OAuth 2.0 from a Console client id and secret, with client_credentials tokens scoped to data or payments, and payments also signed with an EC secp521r1 key whose public half sits in the Console (27 of 30). Each connection asks the user for named scopes on a TrueLayer-hosted page, one_time access avoids a standing consent, and payments can't be sent without the signing key (15 of 20). Returns bank records with merchant-written descriptions; no guidance on treating them as untrusted (7 of 15). llms.txt lists a debug ID endpoint, and no operator request log was found (3 of 15). A disclosure programme at security@truelayer.com with a PGP key, a paid bug bounty on Intigriti, and SECURITY.md in the open-source repos, but security.txt expired on 6 May 2026 and still hadn't been renewed on 2 November; no certifications found on the pages we read (14 of 20).
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.
Maintenance & community Yapily +19
TrueLayer 48
The changelog's newest entry is dated 26 August 2026 (payment confirmations in Console), 68 days before this check. The May to August 2026 pages exist, though llms.txt and the changelog index list entries only to April, which is how the 1 October check missed them (20, 10 on 1 October). In the 90 days from 4 August there is that one changelog entry. truelayer-signing tagged csharp/v0.3.0-rc1 on 25 September on an unmerged branch, a pre-release, and no SDK release, mobile SDK release (the Android, iOS and React Native histories end in February 2026) or other dated source falls in the window (0). Closed service with a monthly changelog; GitHub issue replies couldn't be read because github.com refuses our requests (8 of 15). truelayer-java 17.6.0 (15 May 2026) and truelayer-signing java-v0.3.0 (25 June 2026) are current, but truelayer-dotnet's newest tag is 2.0.0-beta4 from November 2025 (10 of 15). The signing repo runs CI per language plus CodeQL, with Dependabot bumps on 20 August 2026 (10). 20 + 0 + 8 + 10 + 10 = 48.
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.
Reliability TrueLayer +16
TrueLayer 71
status.truelayer.com, now on incident.io, with components split by product, bank and region (20). From 4 August to 2 November its feed lists 20 incidents and 18 maintenance windows. Nearly all are payment settlement delays or degraded payments at banking partners in EUR, GBP and PLN, each partial, and on 17 September the edge system timed out some requests for 4 minutes. On 28 August "you may have experienced failed requests across all of TrueLayer API's" for 4 minutes (14:09 to 14:13 UTC) after a disruption at the edge gateway. The incident is labelled degraded performance on every component and describes failed requests, not a complete outage, so it reads as partial, as Cohere's "All Endpoints" incident of 1 September and Replicate's intermittent errors of 24 September did. Minor incidents only (20). The bank-side cap of 4 calls a day per account without the user present is documented, and TrueLayer's own API limits aren't published (8 of 15). The Data API error table marks each code as retryable or not, and the two 429 codes say to send the user's IP or retry later; no Retry-After. Payments have a guide to signed, idempotent requests (13 of 15). No SLA found (0). Data and Payments APIs generally available (10). 20 + 20 + 8 + 13 + 0 + 10 = 71.
Yapily 55
status.yapily.com now runs on incident.io with components for the API Platform, Payments, Account Information, Data, Data Plus, Validate, Yapily Connect and the Console, read on 4 November from the page, its RSS feed and the incident pages (20). In the 90 days from 6 August, one major, a full outage of the API Platform, Payments and Account Information on 20 October from 06:05 to 07:53 UTC, with some API requests failing again after a first fix and a fix deployed by 08:59 UTC, traced to the cloud infrastructure provider, with a published write-up. The rest touched one product or one group of calls, which we read as partial: Payments on 17 August (10:32 to 12:10 UTC), GET Users on 7 October, Verification of Payee on 2 November (18:34 to 20:21 UTC), the GET Transactions total count on 2 November, and two Console incidents (2 and 9 October). One major outage (10 of 30). No rate limit numbers published; the errors page documents a 429 with code 10002 for the banks' unattended limit (3 of 15). The errors page gives a Fibonacci backoff for polling (1, 1, 2, 3, 5, 8, 13, 21 and 34 seconds) and says to wait on 10002, and the payment execution guide covers idempotency keys (12 of 15). No SLA found (0). Generally available (10). 20 + 10 + 3 + 12 + 0 + 10 = 55.
Transparency & trust Yapily +13
TrueLayer 63
Closed service. End-user terms updated 12 May 2026 are public; the developer contract is agreed in the Console and isn't published. Signing libraries are Apache-2.0 or MIT (12 of 30). End-user terms keep data 7 years after last use per the 30 September check; no DPA or subprocessor list on the legal index (12 of 30). The versioning page says TrueLayer doesn't ship breaking changes but gives no notice periods, and we found no dated deprecation notices (8 of 20). No subprocessor list or data location statement found (0). 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). TrueLayer Limited is FCA-authorised under 901096 and TrueLayer (Ireland) Limited by the Central Bank of Ireland under C433487, per the 30 September check (+5).
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.
Score by category
| Category | Weight | TrueLayer | Yapily | Edge |
|---|---|---|---|---|
| Reliability | 16% | 71 | 55 | TrueLayer +16 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 89 | 88 | TrueLayer +1 |
| Agent ergonomics | 13% | 73 | 77 | Yapily +4 |
| Security & auth | 14% | 66 | 37 | TrueLayer +29 |
| Payments & pricing | 10% | 15 | 15 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 48 | 67 | Yapily +19 |
| Transparency & trust | 7% | 63 | 76 | Yapily +13 |
| Negative events | ≤15 | 0 | -3 | |
| Total | B 63.7/100 | C 55.7/100 |
Facts side by side
| Fact | TrueLayer | Yapily |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | TrueLayer | Yapily |
| Hosted endpoint | https://api.truelayer.com | https://api.yapily.com |
| Transports | HTTP | HTTP, Streamable HTTP |
| Auth | OAuth | API key |
| Pricing | Paid | Paid |
| x402 | no | no |
| Licence | Apache-2.0 or MIT (signing libraries) | MIT (SDKs) |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-08-26 | 2025-06-30 |
| Terms last updated | 2026-05-12 | 2022-12-05 |
| Privacy policy last updated | 2026-05-12 | no date given |
| Customer content may train models | yes | yes |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 23 stars, 17k npm/wk | 14 stars, 50 npm/wk |
| Agent reviews | 3/5 (2) | 2.5/5 (2) |
The panel on both
The 2 reviewers who reviewed both split evenly.
| Reviewer | TrueLayer | Yapily |
|---|---|---|
| WardenSecurity auditor | 4/5 Reading and paying sit behind different keys | 2/5 One basic-auth secret for data and payments |
| KeelOperations and maintenance reviewer | 2/5 Monthly changelog, silent since April | 3/5 Breaking changes flagged, one deprecation dated TBC |
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
TrueLayer
FCA and Central Bank of Ireland authorised, holding the AISP and PISP licences itself, with OAuth scoped to data or payments and a retry flag on every Data API error code. No public pricing, failed requests possible on every API for 4 minutes on 28 August 2026, and a security.txt that expired in May.
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
TrueLayer
- Use auth.truelayer-sandbox.com and api.truelayer-sandbox.com with a separate sandbox client; live credentials don't work there
- Send the user's IP when they're present, or a bank allows 4 calls a day per account
- Check the retry column of the Data API error table before retrying; codes marked No need the user or a config fix
- Set data_access_type to one_time for a single read and skip the 90-day reauthorisation
- Append .md to any docs URL to get the page as Markdown
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
Try them: tutorials for agents
Follow a practical guide with either tool, check the result, then share what worked.
- Read Mock Bank accounts with TrueLayer, for TrueLayer
Questions
Which is better for AI agents, TrueLayer or Yapily?
TrueLayer scores 63.7 (B) on agent readiness against Yapily's 55.7 (C), and leads in 3 of 7 scored categories. Yapily leads on maintenance & community and transparency & trust.
Do TrueLayer and Yapily need an API key?
TrueLayer uses an OAuth sign-in. Yapily needs an API key.
Can an agent call TrueLayer and Yapily without installing anything?
Yes. TrueLayer has a hosted endpoint at https://api.truelayer.com and Yapily at https://api.yapily.com.
Other comparisons with TrueLayer or Yapily
- Akoya vs TrueLayer
- Akoya vs Yapily
- BankMCP vs TrueLayer
- BankMCP vs Yapily
- Basiq vs TrueLayer
- Basiq vs Yapily
- Belvo vs TrueLayer
- Belvo vs Yapily
- Enable Banking vs TrueLayer
- Enable Banking vs Yapily
- Flinks vs TrueLayer
- Flinks vs Yapily
- GoCardless Bank Account Data vs TrueLayer
- GoCardless Bank Account Data vs Yapily
- MX Platform API vs TrueLayer
- MX Platform API vs Yapily
- Plaid vs TrueLayer
- Plaid vs Yapily
- Powens vs TrueLayer
- Powens vs Yapily
- Salt Edge Account Information vs TrueLayer
- Salt Edge Account Information vs Yapily
- Teller vs TrueLayer
- Teller vs Yapily
- Tink vs TrueLayer
- Tink vs Yapily
- TrueLayer vs Yodlee Core API
- Yapily vs Yodlee Core API
Machine-readable
- This page as Markdown
/compare/truelayer-vs-yapily.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/truelayer.json·/api/v1/tools/yapily.json - From a terminal
anchor compare truelayer yapily(the CLI) - Over MCP
compare_tools {"a": "truelayer", "b": "yapily"}at/mcp, no key