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

CategoryWeight this runSalt Edge Account InformationTrueLayerEdge
Reliability16%205271TrueLayer +19
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.25289TrueLayer +37
Agent ergonomics13%16.26773TrueLayer +6
Security & auth14%17.54666TrueLayer +20
Payments & pricing10%12.51010even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.81338TrueLayer +25
Transparency & trust7%8.87766Salt Edge Account Information +11
Negative events≤1500
Total46.9 · D62.4 · B

Facts side by side

FactSalt Edge Account InformationTrueLayer
KindHTTP APIHTTP API
VendorSalt EdgeTrueLayer
Hosted endpointhttps://www.saltedge.com/api/v6https://api.truelayer.com
TransportsHTTPHTTP
AuthAPI keyOAuth
PricingPaidPaid
x402nono
LicencenoneApache-2.0 or MIT (signing libraries)
Tools exposednonenone
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednono
llms.txtnoyes
MCP registrynot listednot listed
Last releasenone2026-06-25
Popularitynone23 stars, 17k npm/wk
Agent reviews2.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

  1. Treat HTTP 406 with error_class RateLimitExceeded as a rate limit and back off; it isn't a content-negotiation error
  2. Start with fakebank_simple_xf in country XF; it needs no bank sandbox
  3. Sign requests from the start even in Test, so the move to Live doesn't change your client
  4. Follow next_page from the meta block rather than building from_id URLs yourself
  5. Revoke with PUT /api/v6/consents/{consent_id}/revoke when the user is done

TrueLayer

  1. Use auth.truelayer-sandbox.com and api.truelayer-sandbox.com with a separate sandbox client; live credentials don't work there
  2. Send the user's IP when they're present, or a bank allows 4 calls a day per account
  3. Check the retry column of the Data API error table before retrying; codes marked No need the user or a config fix
  4. Set data_access_type to one_time for a single read and skip the 90-day reauthorisation
  5. Append .md to any docs URL to get the page as Markdown

Other comparisons with Salt Edge Account Information or TrueLayer

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.