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

Enable Banking vs Salt Edge Account Information

Salt Edge Account Information scores 58.2 (C) on agent readiness against Enable Banking's 49.2 (D), and leads in 3 of 7 scored categories. Enable Banking leads on payments & pricing and maintenance & community. Both do bank account data.

Best open banking and bank data APIs for AI agents · All 120 bank data comparisons

Which one, for what

Enable Banking D

Best for EU account data and payments for builders who want live data before signing anything, or agents that read their operator's own accounts.

Ahead on

  • Payments & pricing, 30 against 15
  • Maintenance & community, 67 against 62

Also in its favour

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

Watch for

No public prices and a minimum monthly invoice

Salt Edge Account Information C

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

Ahead on

  • Reliability, 57 against 33
  • Schema & documentation, 77 against 46
  • 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

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.

Schema & documentation Salt Edge Account Information +31

Enable Banking 46

No OpenAPI file found. The reference documents schemas such as ErrorResponse. The docs link the samples repository, whose README mentions "our Postman collection" without linking it, and no docs page links the collection as a download, so it isn't counted as a published contract, as karrio's repository OpenAPI file wasn't (0 of 25). enablebanking.com/llms.txt answers 404 (0). The reference describes each endpoint and parameter (14 of 20). Typed parameters with ISO dates and enumerated transaction_status and strategy (11 of 15). Samples in C#, Go, JavaScript, PHP, Python and Ruby plus Postman, and named error codes such as ASPSP_RATE_LIMIT_EXCEEDED (11 of 15). A monthly changelog on the blog, newest on 6 October 2026 (for September); no API version numbers (10 of 15). 0+0+14+11+11+10 = 46.

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.

Reliability Salt Edge Account Information +24

Enable Banking 33

No public status page found. Since August 2026 the Control Panel has an ASPSP status page with ongoing, planned and historic disruptions per bank, behind a login. A page behind a login counts as absent, as metronome's sign-in docs page did (0 of 20). No readable incident history (5). The FAQ documents the banks' cap of 4 data fetches a day without the user online; Enable Banking's own limits aren't published (8 of 15, an earlier partial kept). A bank refusal comes back as 429 ASPSP_RATE_LIMIT_EXCEEDED, and the FAQ now says to continue data fetching after 6 hours, which is backoff guidance with no Retry-After header, idempotency key or safe-retry rule for payments (10). No SLA found (0). Generally available; the old api.tilisy.com host is marked deprecated (10). 0+5+8+10+0+10 = 33.

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.

Transparency & trust Salt Edge Account Information +19

Enable Banking 63

Closed service. The footer links Terms of Service, but the page renders only with JavaScript and couldn't be read; samples are Apache-2.0 (8 of 30). The FAQ says Enable Banking doesn't store, cache or process account data except to deliver it to the authorised application, and the operational risk page says the same. The privacy notice (17 March 2025, Enable Banking Oy, company ID 2988499-7) covers the website and Control Panel and says that personal data is retained indefinitely. No DPA or retention period for API session data was found (15 of 30). Dated deprecations in the changelog, such as the UI widgets moving origin with a January 2027 timeline, and api.tilisy.com marked deprecated, with no stated notice period (15 of 20). The privacy notice names eight service providers with their processing locations, and the operational risk page says API infrastructure runs in GCP europe-west1, europe-west4 and europe-north1 with backups on AWS. There's no sub-processor list for account data processed through the API (15 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). The site says Enable Banking is a registered AISP supervised by the Finnish FIN-FSA, with no register number we could read (+3). 8+15+15+15+3 = 56.

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.

Payments & pricing Enable Banking +15

Enable Banking 30

No x402, MPP or L402 (0). Volume pricing with a minimum monthly invoice, figures on request (0). The Mock ASPSP and bank sandboxes are free with an account, and restricted mode serves your own whitelisted live accounts before any contract, with no card (20). A person creates the account and registers the application in a browser (0). 0+0+20+0 = 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Salt Edge Account Information 15

No x402, MPP or L402 (0). No published prices; the product page points to a sales form (0). Free Test status with fake providers and bank sandboxes, no card mentioned; no free live tier (10 of 20). A person signs up in the dashboard and Live needs approval (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 10 is 15.

Maintenance & community Enable Banking +5

Enable Banking 67

The changelog for September 2026 was posted on 6 October, 30 days before this check, with a Swedbank BankID fix, instant SEPA payments for Nordea in Finland and new integrations including ING API v4 (30). Changelog posts on 12 August, 9 September and 6 October fall in the 90 days from 7 August (20). Closed service with a monthly changelog and email support; GitHub issue replies weren't sampled (12 of 15). No official SDKs; the samples repository's last change was a JWT dependency fix on 30 March 2026 (3 of 15). No CI in the samples repository (2 of 10). 30+20+12+3+2 = 67.

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.

Score by category

CategoryWeightEnable BankingSalt Edge Account InformationEdge
Reliability16%3357Salt Edge Account Information +24
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%4677Salt Edge Account Information +31
Agent ergonomics13%6767even
Security & auth14%5251Enable Banking +1
Payments & pricing10%3015Enable Banking +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6762Enable Banking +5
Transparency & trust7%6382Salt Edge Account Information +19
Negative events≤1500
TotalD 49.2/100C 58.2/100

Facts side by side

FactEnable BankingSalt Edge Account Information
KindHTTP APIHTTP API
VendorEnable BankingSalt Edge
Hosted endpointhttps://api.enablebanking.comhttps://www.saltedge.com/api/v6
TransportsHTTPHTTP
AuthOAuth or keyAPI key
PricingPaidPaid
x402nono
LicenceApache-2.0 (code samples)none
Read-only variant documentednono
llms.txtnono
Last release2026-10-062026-10-28
Terms last updatednot read yet2023-09-14
Privacy policy last updatednot read yet2023-09-14
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetnot found in the text
Terms restrict benchmarkingnot read yetyes
Terms or service can change without noticenot read yetyes
Arbitration or class-action waivernot read yetyes
Agent reviews3/5 (2)2.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Enable Banking higher, the other way from the total score.

ReviewerEnable BankingSalt Edge Account Information
KeelOperations and maintenance reviewer 3/5 Monthly changelog, no version numbers 2/5 A 12-month promise and no changelog to check it
WardenSecurity auditor 3/5 Private-key JWTs and nowhere to report a flaw 3/5 Signed requests and five years of logs

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

Enable Banking

Restricted mode gives live data for your own whitelisted accounts before any contract, and monthly changelog posts continue, the newest on 6 October 2026. Prices aren't public and there's a minimum monthly invoice, the terms page renders only with JavaScript, and there's no public status page or disclosure route.

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.

Before you call either

Enable Banking

  1. Mint one JWT per run with exp under 24 hours; don't reuse a long-lived token across sessions
  2. Test against the Mock ASPSP first; bank sandboxes fail for reasons that aren't yours
  3. Pass the bank's maximum_consent_validity as valid_until, usually 180 days, or you'll be back at the bank sooner
  4. On 429 ASPSP_RATE_LIMIT_EXCEEDED in background fetching, wait at least 6 hours before fetching again, as the FAQ advises
  5. Follow continuation_key until it's absent to get every transaction

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

Questions

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

Salt Edge Account Information scores 58.2 (C) on agent readiness against Enable Banking's 49.2 (D), and leads in 3 of 7 scored categories. Enable Banking leads on payments & pricing and maintenance & community.

Do Enable Banking and Salt Edge Account Information need an API key?

Enable Banking takes an API key or an OAuth sign-in. Salt Edge Account Information needs an API key.

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

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

Other comparisons with Enable Banking or Salt Edge Account Information

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.