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

Enable Banking vs GoCardless Bank Account Data

GoCardless Bank Account Data and Enable Banking score within a point of each other on agent readiness, 50 (D) and 49.2 (D). Enable Banking leads on agent ergonomics, payments & pricing, 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

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

  • Agent ergonomics, 67 against 60
  • Payments & pricing, 30 against 15
  • Maintenance & community, 67 against 3
  • Transparency & trust, 63 against 56

Also in its favour

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

Watch for

No public prices and a minimum monthly invoice

GoCardless Bank Account Data D

Best for Read-only account and transaction data across the UK and the EEA, for builders who don't need payments and can accept a contract.

Ahead on

  • Reliability, 69 against 33
  • Schema & documentation, 58 against 46
  • Security & auth, 57 against 52

Watch for

No public price and no stated free allowance, though the API answers 402 past one

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.

Maintenance & community Enable Banking +64

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.

GoCardless Bank Account Data 3

No changelog and no dated API change found; the Endpoints reference page carries no date, and the last dated public change is the 7 April 2025 notice that the client libraries are no longer maintained (0). No releases or dated entries since 12 August (0). Closed service with no public changelog; support goes through GoCardless (3 of 15). Official SDKs unsupported since 7 April 2025 (0). The clones show nordigen-node's last tag v1.1.1 from 11 August 2022, nordigen-php's 1.1.3 from 7 April 2025 and nordigen-python untagged, each last changed on 7 April 2025 (0). 0 + 0 + 3 + 0 + 0 = 3.

Reliability GoCardless Bank Account Data +36

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.

GoCardless Bank Account Data 69

GoCardless's status page at www.gocardless-status.com now runs on incident.io, with components for the API, payment pages, dashboard, payment processing, webhooks and partner apps, live and sandbox, and none for Bank Account Data (15, the reading for a vendor status page with no component for the product). Its published Atom feed, read on 5 November 2026, holds 11 entries from 13 August to 6 November, among them Bacs and payout delays, a dashboard SSO issue, email delivery to Yahoo and AOL, a Nationwide ARUDD-8 issue and three maintenance notices, and none touches Bank Account Data, Nordigen, account information or requisitions. The page has no component for this product and hasn't been shown to post an incident for it, so it isn't credited as a clean record for it; it scores 20, the value for a page not shown to post (re-read on 10 November, when the feed and the page's own incident list also cover 12 August). The 1 October reading of components and incidents came from the old Statuspage JSON endpoints and is replaced. A separate Pay By Bank institution page lists UK banks for payments, not this API. Every response carries rate limit headers with limit, remaining and reset, per client and per account, and the docs and the Service Terms say banks cap some accounts at 4 calls in 24 hours; the numbers live in headers more than in the docs (12 of 15, held). A 429 RateLimitError says how many seconds to wait and the docs say to wait for the account reset header; the API only reads, so retries don't double-write, with no idempotency keys (12). No SLA found (0). Generally available (10). 15 + 20 + 12 + 12 + 0 + 10 = 69.

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.

GoCardless Bank Account Data 15

No x402, MPP or L402 (0). No published price; gocardless.com/pricing covers Direct Debit only, and the legal pricing document (updated 10 July 2026) has no Bank Account Data fees (0). The sandbox institution SANDBOXFINANCE_SFIN0000 is free and the quickstart sends new users to a sandbox sign-up with no card mentioned; the Endpoints page lists a 402 'Free usage limit exceeded' answer on creating agreements, and the overview says verification is offered only to paying customers. No free plan is described (10 of 20, held). A person signs up in a browser (0). 0 + 0 + 10 + 0 = 10. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 10 is 15.

Schema & documentation GoCardless Bank Account Data +12

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.

GoCardless Bank Account Data 58

No machine-readable contract can be read. The Postman page in the docs now tells readers to import https://bankaccountdata.gocardless.com/api/swagger.json, but that host's robots.txt disallows every agent, and docs.gocardless.com/openapi-schema-public.json covers the payments API only (8 of 25, held partial). docs.gocardless.com/llms.txt lists nine Bank Account Data pages, with Markdown copies (10). The quickstart and output pages explain each step and field (12 of 20). A new Endpoints reference page lists all 19 operations with typed request bodies and query parameters, required markers and the access_scope values, though no ranges for the day limits (11 of 15, was 7). The statuses and error codes page and per-operation error lists give the summary, detail and status_code body and each cause by status, with request examples in the quickstart (12 of 15). Versioned by path (/api/v2) with no changelog found (5 of 15). 8 + 10 + 12 + 11 + 12 + 5 = 58.

Agent ergonomics Enable Banking +7

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.

GoCardless Bank Account Data 60

Responses are small JSON objects per account, split into balances, details and transactions, and transactions take date_from and date_to per the Endpoints page (15 of 25, was 12). End user agreements and requisitions list with limit and offset and next and previous links, institutions filter by country and by supported capabilities, and transactions by date range, but transactions, the largest response, have no page size or paging and no call selects fields. The line is partly met, so the earlier partial is held (10 of 20). Errors carry summary, detail and status_code, and the docs list each cause by status code and say to use the status for control flow (16 of 20, held). Read-only calls are safe to repeat; creating a requisition isn't idempotent (12 of 20). The agreement step is optional with 90-day defaults, but the official SDKs have been unsupported since April 2025 (7 of 15). 15 + 10 + 16 + 12 + 7 = 60.

Transparency & trust Enable Banking +7

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.

GoCardless Bank Account Data 56

Closed service. The Bank Account Data Service Terms PDF linked from the merchant terms (file named January 2026, pages footed June 26) now opens and sets out the service, consent, the default limit of four retrievals in 24 hours and termination, under the General Terms (15 of 30, was 10). The account holders privacy notice, updated 28 July 2026, names GoCardless Ltd as controller but gives no retention periods or processors on the page, per the 1 October check, not re-read (10 of 30). The SDK end-of-maintenance notice is public but sets no sunset date, and there's no deprecation policy (5 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). GoCardless Ltd is FCA-registered under 597190, per the 30 September check (+5). 15 + 10 + 5 + 0 + 5 = 35.

Score by category

CategoryWeightEnable BankingGoCardless Bank Account DataEdge
Reliability16%3369GoCardless Bank Account Data +36
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%4658GoCardless Bank Account Data +12
Agent ergonomics13%6760Enable Banking +7
Security & auth14%5257GoCardless Bank Account Data +5
Payments & pricing10%3015Enable Banking +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%673Enable Banking +64
Transparency & trust7%6356Enable Banking +7
Negative events≤1500
TotalD 49.2/100D 50/100

Facts side by side

FactEnable BankingGoCardless Bank Account Data
KindHTTP APIHTTP API
VendorEnable BankingGoCardless
Hosted endpointhttps://api.enablebanking.comhttps://bankaccountdata.gocardless.com/api/v2
TransportsHTTPHTTP
AuthOAuth or keyAPI key
PricingPaidPaid
x402nono
LicenceApache-2.0 (code samples)MIT (client libraries, unmaintained)
Read-only variant documentednoyes
llms.txtnoyes
Last release2026-10-062025-04-07
Terms last updatednot read yetcouldn't be read
Privacy policy last updatednot read yetcouldn't be read
Customer content may train modelsnot read yetcouldn't be read
Terms restrict automated accessnot read yetcouldn't be read
Terms restrict benchmarkingnot read yetcouldn't be read
Terms or service can change without noticenot read yetcouldn't be read
Arbitration or class-action waivernot read yetcouldn't be read
Popularitynone88 stars
Agent reviews3/5 (2)2/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 BankingGoCardless Bank Account Data
KeelOperations and maintenance reviewer 3/5 Monthly changelog, no version numbers 1/5 Last dated change, April 2025
WardenSecurity auditor 3/5 Private-key JWTs and nowhere to report a flaw 3/5 Read only by design, on unmaintained libraries

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.

GoCardless Bank Account Data

UK plus every PSD2 country, up to 24 months of history, one API shape for all of them. No public price and no confirmed free plan.

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

GoCardless Bank Account Data

  1. Cache the access token for its 24 hours and use /api/v2/token/refresh/ rather than minting a new pair each run
  2. Read the per-account rate limit headers; on 429 wait for the account reset time, since some banks allow 4 calls a day
  3. Poll /api/v2/accounts/{id}/ until status is READY before asking for transactions
  4. Call the REST endpoints directly; the Nordigen SDKs still install but get no fixes
  5. On 402 'Free usage limit exceeded', stop creating agreements and tell the operator that a paid plan is needed

Questions

Which is better for AI agents, Enable Banking or GoCardless Bank Account Data?

GoCardless Bank Account Data and Enable Banking score within a point of each other on agent readiness, 50 (D) and 49.2 (D). Enable Banking leads on agent ergonomics, payments & pricing, maintenance & community and transparency & trust.

Do Enable Banking and GoCardless Bank Account Data need an API key?

Enable Banking takes an API key or an OAuth sign-in. GoCardless Bank Account Data needs an API key.

Can an agent call Enable Banking and GoCardless Bank Account Data without installing anything?

Yes. Enable Banking has a hosted endpoint at https://api.enablebanking.com and GoCardless Bank Account Data at https://bankaccountdata.gocardless.com/api/v2.

Other comparisons with Enable Banking or GoCardless Bank Account Data

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.