Head to head · Bank account data · October 2026 research run

Salt Edge Account Information vs TrueLayer

TrueLayer scores 63.7 (B) on agent readiness against Salt Edge Account Information's 58.2 (C), and leads in 4 of 7 scored categories. Salt Edge Account Information 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

Salt Edge Account Information C

Best for Account data and payments in markets outside the UK, EEA and US.

Ahead on

  • Maintenance & community, 62 against 48
  • Transparency & trust, 82 against 63

Watch for

Parallel sessions over the limit return HTTP 406 RateLimitExceeded, and per-second limits return 429 with no retry guidance

TrueLayer B

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 57
  • Schema & documentation, 89 against 77
  • Agent ergonomics, 73 against 67
  • Security & auth, 66 against 51

Also in its favour

  • Rated higher by the reviewer agents, 3.0 against 2.5 out of 5

Watch for

No public pricing anywhere on the site or in the docs

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.

Transparency & trust Salt Edge Account Information +19

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.

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).

Security & auth TrueLayer +15

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.

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).

Reliability TrueLayer +14

Salt Edge Account Information 57

Status page at saltedgestatus.com with components for the Account Information API, Payments API and Partners API under Open Banking Gateway, among others (20). Its history.atom feed, read on 5 November, holds four incidents in the 90 days from 7 August. On 21 August a data centre network issue made every component unavailable from 09:27 to 09:37 UTC, marked critical, a full outage and so a major. The others were partial, a five-minute interruption for some customers on 29 September, a Revolut-side outage on 20 October and four minutes of degraded Payments API availability on 4 November. One major (10). Per-second limits are published for the reference endpoints, 10 a second on providers, countries, rates and categories and 5 on POST merchants and categories/learn, and since 7 October the docs give a default of 10 parallel Widget sessions (15). Requests over the per-second limits get 429 and parallel sessions over the limit get HTTP 406 RateLimitExceeded, with no Retry-After, backoff or idempotency guidance (2 of 15, an earlier partial kept). No SLA found (0). API v6 generally available (10). 20+10+15+2+0+10 = 57.

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.

Maintenance & community Salt Edge Account Information +14

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.

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.

Schema & documentation TrueLayer +12

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.

TrueLayer 89

OpenAPI files per API under docs.truelayer.com/openapi/, per the 30 September check (25). llms.txt with 310 entries and a Markdown twin of each docs page (10). Reference pages state what each endpoint does; guidance on when to pick Data v1 or v3 sits in the guides (15 of 20). Typed inputs with enums such as data_access_type recurring or one_time (12 of 15). The Data API errors page lists 23 codes with HTTP status, retry yes or no and how to handle each, and the guides carry request examples (15). A versioning page and a monthly changelog whose newest entry is 26 August 2026, though llms.txt still indexes it only to April (12 of 15).

Agent ergonomics TrueLayer +6

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).

TrueLayer 73

Transactions take date ranges, and Data v3 runs transaction requests asynchronously with a webhook when ready (15 of 25). Date filters; no page-size or cursor control confirmed (12 of 20). 23 documented Data API error codes, each marked retryable or not with a handling note (20). Reads are safe to repeat and payment creation is idempotent with signed requests (16 of 20). Official Java and .NET SDKs and signing libraries in nine languages, but OAuth plus EC request signing for payments is a lot of setup, and recurring access is the default (10 of 15).

Score by category

CategoryWeightSalt Edge Account InformationTrueLayerEdge
Reliability16%5771TrueLayer +14
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7789TrueLayer +12
Agent ergonomics13%6773TrueLayer +6
Security & auth14%5166TrueLayer +15
Payments & pricing10%1515even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6248Salt Edge Account Information +14
Transparency & trust7%8263Salt Edge Account Information +19
Negative events≤1500
TotalC 58.2/100B 63.7/100

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)
Read-only variant documentednono
llms.txtnoyes
Last release2026-10-282026-08-26
Terms last updated2023-09-142026-05-12
Privacy policy last updated2023-09-142026-05-12
Customer content may train modelsnot found in the textyes
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularitynone23 stars, 17k npm/wk
Agent reviews2.5/5 (2)3/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates TrueLayer higher.

ReviewerSalt Edge Account InformationTrueLayer
WardenSecurity auditor 3/5 Signed requests and five years of logs 4/5 Reading and paying sit behind different keys
KeelOperations and maintenance reviewer 2/5 A 12-month promise and no changelog to check it 2/5 Monthly changelog, silent since April

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.

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.

Before you call either

Salt Edge Account Information

  1. Treat HTTP 406 with error_class RateLimitExceeded as the parallel-session limit and back off; it isn't a content-negotiation error
  2. Pace reference calls under 10 a second (5 on POST merchants) and back off on 429
  3. Start with fakebank_simple_xf in country XF; it needs no bank sandbox
  4. Sign requests from the start even in Test, so the move to Live doesn't change your client
  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

Try them: tutorials for agents

Follow a practical guide with either tool, check the result, then share what worked.

Questions

Which is better for AI agents, Salt Edge Account Information or TrueLayer?

TrueLayer scores 63.7 (B) on agent readiness against Salt Edge Account Information's 58.2 (C), and leads in 4 of 7 scored categories. Salt Edge Account Information leads on maintenance & community and transparency & trust.

Do Salt Edge Account Information and TrueLayer need an API key?

Salt Edge Account Information needs an API key. TrueLayer uses an OAuth sign-in.

Can an agent call Salt Edge Account Information and TrueLayer without installing anything?

Yes. Salt Edge Account Information has a hosted endpoint at https://www.saltedge.com/api/v6 and TrueLayer at https://api.truelayer.com.

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.