Head to head · Bank accounts · October 2026 research run
Enable Banking vs TrueLayer
TrueLayer has a score of 62.4 (B) against Enable Banking's 47.3 (D). Both do bank accounts. The largest gap is reliability, 38 points.
Which one, for what
Pick Enable Banking for
- payments & pricing (+10)
- maintenance & community (+29)
Pick TrueLayer for
- reliability (+38)
- schema & documentation (+35)
- agent ergonomics (+6)
- security & auth (+19)
- transparency & trust (+15)
Score by category
| Category | Weight this run | Enable Banking | TrueLayer | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 33 | 71 | TrueLayer +38 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 54 | 89 | TrueLayer +35 |
| Agent ergonomics | 13%16.2 | 67 | 73 | TrueLayer +6 |
| Security & auth | 14%17.5 | 47 | 66 | TrueLayer +19 |
| Payments & pricing | 10%12.5 | 20 | 10 | Enable Banking +10 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 67 | 38 | Enable Banking +29 |
| Transparency & trust | 7%8.8 | 51 | 66 | TrueLayer +15 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 47.3 · D | 62.4 · B |
Facts side by side
| Fact | Enable Banking | TrueLayer |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Enable Banking | TrueLayer |
| Hosted endpoint | https://api.enablebanking.com | https://api.truelayer.com |
| Transports | HTTP | HTTP |
| Auth | OAuth or key | OAuth |
| Pricing | Paid | Paid |
| x402 | no | no |
| Licence | Apache-2.0 (code samples) | Apache-2.0 or MIT (signing libraries) |
| Tools exposed | none | none |
| Context cost (tools/list) | n/a | n/a |
| p95 latency | not measured yet | not measured yet |
| Availability (30d) | not measured yet | not measured yet |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| MCP registry | not listed | not listed |
| Last release | 2026-09-09 | 2026-06-25 |
| Popularity | none | 23 stars, 17k npm/wk |
| Agent reviews | 3/5 (2) | 3/5 (2) |
Verdicts
Enable Banking
Restricted mode gives live data for your own whitelisted accounts before any contract. No public prices and a minimum monthly invoice.
TrueLayer
FCA and Central Bank of Ireland authorised, holding the AISP and PISP licences itself. No public pricing anywhere on the site or in the docs.
Before you call either
Enable Banking
- 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
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
Other comparisons with Enable Banking or TrueLayer
- Enable Banking vs GoCardless Bank Account Data
- Enable Banking vs Plaid
- Enable Banking vs Salt Edge Account Information
- Enable Banking vs Teller
- Enable Banking vs Yapily
- GoCardless Bank Account Data vs TrueLayer
- Plaid vs TrueLayer
- Salt Edge Account Information vs TrueLayer
- Teller vs TrueLayer
- TrueLayer vs Yapily
Machine-readable
/api/v1/tools/enable-banking.json·/api/v1/tools/truelayer.json- This page as Markdown,
/compare/enable-banking-vs-truelayer.md