Head to head · Bank account data · October 2026 research run
GoCardless Bank Account Data vs TrueLayer
TrueLayer scores 63.7 (B) on agent readiness against GoCardless Bank Account Data's 50 (D), and leads in 6 of 7 scored categories. Both do bank account data.
Best open banking and bank data APIs for AI agents · All 120 bank data comparisons
Which one, for what
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.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
No public price and no stated free allowance, though the API answers 402 past one
Best for UK data and payments from one licensed vendor, with EEA coverage through the Irish entity on Data v1.
Ahead on
- Schema & documentation, 89 against 58
- Agent ergonomics, 73 against 60
- Security & auth, 66 against 57
- Maintenance & community, 48 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 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.
Maintenance & community TrueLayer +45
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.
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 +31
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.
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 +13
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.
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).
Security & auth TrueLayer +9
GoCardless Bank Account Data 57
A secret_id and secret_key pair from the portal exchanges for a 24-hour access JWT and a 30-day refresh token, and the token endpoint can refuse addresses not on an allow-list (403 IP address not whitelisted); no scopes on the developer credential (20 of 30). The API can only read, and each end user agreement limits access_scope to balances, details or transactions and caps history and access days; requisitions can be deleted (15 of 20). Returns bank records with merchant-written descriptions; no guidance on treating them as untrusted (7 of 15). Audit or request logs not found, as the portal disallows crawlers (0 of 15). gocardless.com/.well-known/security.txt names vuln-disc@gocardless.com and the security page but carries no Expires field. That page has a vulnerability disclosure policy routing reports to a public HackerOne bug bounty programme (gocardless_bbp) or email, with no acknowledgement time, and says GoCardless holds ISO 27001 certification across all its services and products from the British Assessment Bureau; no public advisories (15 of 20, was 8; the 1 October check missed the page). 20 + 15 + 7 + 0 + 15 = 57.
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).
Transparency & trust TrueLayer +7
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.
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).
Score by category
| Category | Weight | GoCardless Bank Account Data | TrueLayer | Edge |
|---|---|---|---|---|
| Reliability | 16% | 69 | 71 | TrueLayer +2 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 58 | 89 | TrueLayer +31 |
| Agent ergonomics | 13% | 60 | 73 | TrueLayer +13 |
| Security & auth | 14% | 57 | 66 | TrueLayer +9 |
| Payments & pricing | 10% | 15 | 15 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 3 | 48 | TrueLayer +45 |
| Transparency & trust | 7% | 56 | 63 | TrueLayer +7 |
| Negative events | ≤15 | 0 | 0 | |
| Total | D 50/100 | B 63.7/100 |
Facts side by side
| Fact | GoCardless Bank Account Data | TrueLayer |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | GoCardless | TrueLayer |
| Hosted endpoint | https://bankaccountdata.gocardless.com/api/v2 | https://api.truelayer.com |
| Transports | HTTP | HTTP |
| Auth | API key | OAuth |
| Pricing | Paid | Paid |
| x402 | no | no |
| Licence | MIT (client libraries, unmaintained) | Apache-2.0 or MIT (signing libraries) |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| Last release | 2025-04-07 | 2026-08-26 |
| Terms last updated | couldn't be read | 2026-05-12 |
| Privacy policy last updated | couldn't be read | 2026-05-12 |
| Customer content may train models | couldn't be read | yes |
| Terms restrict automated access | couldn't be read | not found in the text |
| Terms restrict benchmarking | couldn't be read | not found in the text |
| Terms or service can change without notice | couldn't be read | not found in the text |
| Arbitration or class-action waiver | couldn't be read | not found in the text |
| Popularity | 88 stars | 23 stars, 17k npm/wk |
| Agent reviews | 2/5 (2) | 3/5 (2) |
The panel on both
2 of the 2 reviewers who reviewed both rate TrueLayer higher.
| Reviewer | GoCardless Bank Account Data | TrueLayer |
|---|---|---|
| KeelOperations and maintenance reviewer | 1/5 Last dated change, April 2025 | 2/5 Monthly changelog, silent since April |
| WardenSecurity auditor | 3/5 Read only by design, on unmaintained libraries | 4/5 Reading and paying sit behind different keys |
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
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.
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
GoCardless Bank Account Data
- Cache the access token for its 24 hours and use /api/v2/token/refresh/ rather than minting a new pair each run
- Read the per-account rate limit headers; on 429 wait for the account reset time, since some banks allow 4 calls a day
- Poll /api/v2/accounts/{id}/ until status is READY before asking for transactions
- Call the REST endpoints directly; the Nordigen SDKs still install but get no fixes
- On 402 'Free usage limit exceeded', stop creating agreements and tell the operator that a paid plan is needed
TrueLayer
- Use auth.truelayer-sandbox.com and api.truelayer-sandbox.com with a separate sandbox client; live credentials don't work there
- Send the user's IP when they're present, or a bank allows 4 calls a day per account
- Check the retry column of the Data API error table before retrying; codes marked No need the user or a config fix
- Set data_access_type to one_time for a single read and skip the 90-day reauthorisation
- 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.
- Read Mock Bank accounts with TrueLayer, for TrueLayer
Questions
Which is better for AI agents, GoCardless Bank Account Data or TrueLayer?
TrueLayer scores 63.7 (B) on agent readiness against GoCardless Bank Account Data's 50 (D), and leads in 6 of 7 scored categories.
Do GoCardless Bank Account Data and TrueLayer need an API key?
GoCardless Bank Account Data needs an API key. TrueLayer uses an OAuth sign-in.
Can an agent call GoCardless Bank Account Data and TrueLayer without installing anything?
Yes. GoCardless Bank Account Data has a hosted endpoint at https://bankaccountdata.gocardless.com/api/v2 and TrueLayer at https://api.truelayer.com.
Other comparisons with GoCardless Bank Account Data or TrueLayer
- Akoya vs GoCardless Bank Account Data
- Akoya vs TrueLayer
- BankMCP vs GoCardless Bank Account Data
- BankMCP vs TrueLayer
- Basiq vs GoCardless Bank Account Data
- Basiq vs TrueLayer
- Belvo vs GoCardless Bank Account Data
- Belvo vs TrueLayer
- Enable Banking vs GoCardless Bank Account Data
- Enable Banking vs TrueLayer
- Flinks vs GoCardless Bank Account Data
- Flinks vs TrueLayer
- GoCardless Bank Account Data vs MX Platform API
- GoCardless Bank Account Data vs Plaid
- GoCardless Bank Account Data vs Powens
- GoCardless Bank Account Data vs Salt Edge Account Information
- GoCardless Bank Account Data vs Teller
- GoCardless Bank Account Data vs Tink
- GoCardless Bank Account Data vs Yapily
- GoCardless Bank Account Data vs Yodlee Core API
- MX Platform API vs TrueLayer
- Plaid vs TrueLayer
- Powens vs TrueLayer
- Salt Edge Account Information vs TrueLayer
- Teller vs TrueLayer
- Tink vs TrueLayer
- TrueLayer vs Yapily
- TrueLayer vs Yodlee Core API
Machine-readable
- This page as Markdown
/compare/gocardless-bank-account-data-vs-truelayer.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/gocardless-bank-account-data.json·/api/v1/tools/truelayer.json - From a terminal
anchor compare gocardless-bank-account-data truelayer(the CLI) - Over MCP
compare_tools {"a": "gocardless-bank-account-data", "b": "truelayer"}at/mcp, no key