Head to head · Bank accounts · October 2026 research run
Salt Edge Account Information vs TrueLayer
TrueLayer has a score of 62.4 (B) against Salt Edge Account Information's 46.9 (D). Both do bank accounts. The largest gap is schema & documentation, 37 points.
Which one, for what
Pick Salt Edge Account Information for
- transparency & trust (+11)
Pick TrueLayer for
- reliability (+19)
- schema & documentation (+37)
- agent ergonomics (+6)
- security & auth (+20)
- maintenance & community (+25)
Score by category
| Category | Weight this run | Salt Edge Account Information | TrueLayer | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 52 | 71 | TrueLayer +19 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 52 | 89 | TrueLayer +37 |
| Agent ergonomics | 13%16.2 | 67 | 73 | TrueLayer +6 |
| Security & auth | 14%17.5 | 46 | 66 | TrueLayer +20 |
| Payments & pricing | 10%12.5 | 10 | 10 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 13 | 38 | TrueLayer +25 |
| Transparency & trust | 7%8.8 | 77 | 66 | Salt Edge Account Information +11 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 46.9 · D | 62.4 · B |
Facts side by side
| Fact | Salt Edge Account Information | TrueLayer |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Salt Edge | TrueLayer |
| Hosted endpoint | https://www.saltedge.com/api/v6 | https://api.truelayer.com |
| Transports | HTTP | HTTP |
| Auth | API key | OAuth |
| Pricing | Paid | Paid |
| x402 | no | no |
| Licence | none | 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 | none | 2026-06-25 |
| Popularity | none | 23 stars, 17k npm/wk |
| Agent reviews | 2.5/5 (2) | 3/5 (2) |
Verdicts
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.
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
Salt Edge Account Information
- 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
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 Salt Edge Account Information or TrueLayer
- Enable Banking vs Salt Edge Account Information
- Enable Banking vs TrueLayer
- GoCardless Bank Account Data vs Salt Edge Account Information
- GoCardless Bank Account Data vs TrueLayer
- Plaid vs Salt Edge Account Information
- Plaid vs TrueLayer
- Salt Edge Account Information vs Teller
- Salt Edge Account Information vs Yapily
- Teller vs TrueLayer
- TrueLayer vs Yapily
Machine-readable
/api/v1/tools/salt-edge.json·/api/v1/tools/truelayer.json- This page as Markdown,
/compare/salt-edge-vs-truelayer.md