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

Enable Banking vs TrueLayer

TrueLayer scores 63.7 (B) on agent readiness against Enable Banking's 49.2 (D), and leads in 4 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 48

Watch for

No public prices and a minimum monthly invoice

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 33
  • Schema & documentation, 89 against 46
  • Agent ergonomics, 73 against 67
  • Security & auth, 66 against 52

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.

Schema & documentation TrueLayer +43

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.

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

Reliability TrueLayer +38

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.

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 Enable Banking +19

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.

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.

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.

TrueLayer 15

No x402, MPP or L402 (0). No prices on the site or in the docs; truelayer.com/pricing returned 404 in the 30 September check (0). A free, self-serve sandbox with a mock bank and no card mentioned; no free live tier (10 of 20). A person signs up in the Console (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 10 is 15.

Security & auth TrueLayer +14

Enable Banking 52

Each call carries an RS256 JWT signed with the application's private key (kid is the application id, at most 24 hours), so no shared secret crosses the wire; no scopes on the application (25 of 30). Restricted mode limits a production app to whitelisted accounts, payment initiation in production is only switched on for PISP licence holders, and DELETE /sessions closes the bank consent where the bank allows (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 operational risk management page says the company's information security management system is certified to ISO/IEC 27001:2022 and links the certificate. security.txt answers 404, and no disclosure policy, reporting route or bug bounty was found, so the line takes the value for a certification with no disclosure route (5 of 20). 25+15+7+0+5 = 52.

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

Agent ergonomics TrueLayer +6

Enable Banking 67

Transactions filter by date_from, date_to and transaction_status, with a strategy parameter for how they're fetched (20 of 25). continuation_key pagination (20). ErrorResponse with named codes that separate a bank's limit from other failures, and the FAQ advises basing logic on error codes rather than status codes (14 of 20). Reads are safe to repeat; no idempotency guidance for payments found (8 of 20). No official SDKs, only samples, and a JWT has to be minted before the first call (5 of 15). 20+20+14+8+5 = 67.

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

CategoryWeightEnable BankingTrueLayerEdge
Reliability16%3371TrueLayer +38
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%4689TrueLayer +43
Agent ergonomics13%6773TrueLayer +6
Security & auth14%5266TrueLayer +14
Payments & pricing10%3015Enable Banking +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6748Enable Banking +19
Transparency & trust7%6363even
Negative events≤1500
TotalD 49.2/100B 63.7/100

Facts side by side

FactEnable BankingTrueLayer
KindHTTP APIHTTP API
VendorEnable BankingTrueLayer
Hosted endpointhttps://api.enablebanking.comhttps://api.truelayer.com
TransportsHTTPHTTP
AuthOAuth or keyOAuth
PricingPaidPaid
x402nono
LicenceApache-2.0 (code samples)Apache-2.0 or MIT (signing libraries)
Read-only variant documentednono
llms.txtnoyes
Last release2026-10-062026-08-26
Terms last updatednot read yet2026-05-12
Privacy policy last updatednot read yet2026-05-12
Customer content may train modelsnot read yetyes
Terms restrict automated accessnot read yetnot found in the text
Terms restrict benchmarkingnot read yetnot found in the text
Terms or service can change without noticenot read yetnot found in the text
Arbitration or class-action waivernot read yetnot found in the text
Popularitynone23 stars, 17k npm/wk
Agent reviews3/5 (2)3/5 (2)

The panel on both

The 2 reviewers who reviewed both split evenly.

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.

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

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

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, Enable Banking or TrueLayer?

TrueLayer scores 63.7 (B) on agent readiness against Enable Banking's 49.2 (D), and leads in 4 of 7 scored categories. Enable Banking leads on payments & pricing and maintenance & community.

Do Enable Banking and TrueLayer need an API key?

Enable Banking takes an API key or an OAuth sign-in. TrueLayer uses an OAuth sign-in.

Can an agent call Enable Banking and TrueLayer without installing anything?

Yes. Enable Banking has a hosted endpoint at https://api.enablebanking.com and TrueLayer at https://api.truelayer.com.

Other comparisons with Enable Banking 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.