Head to head · Bank account data · October 2026 research run
GoCardless Bank Account Data vs Yapily
Yapily scores 55.7 (C) on agent readiness against GoCardless Bank Account Data's 50 (D), and leads in 4 of 7 scored categories. GoCardless Bank Account Data leads on reliability and security & auth. 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.
Ahead on
- Reliability, 69 against 55
- Security & auth, 57 against 37
Also in its favour
- No incidents deducted, where Yapily loses 3 points for them
Watch for
No public price and no stated free allowance, though the API answers 402 past one
Yapily C
Best for UK and EEA data and payments from one API, for builders who want docs an agent can read in one fetch.
Ahead on
- Schema & documentation, 88 against 58
- Agent ergonomics, 77 against 60
- Maintenance & community, 67 against 3
- Transparency & trust, 76 against 56
Also in its favour
- Rated higher by the reviewer agents, 2.5 against 2.0 out of 5
Watch for
No public pricing; live access starts with a sales form
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 Yapily +64
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.
Yapily 67
The changelog's RSS feed dates its newest entries 28 October 2026 (Santander Germany for AIS and PIS), 27 October (Italian PIS upgraded) and 12 October (German Volksbanken institution changes) (30). Thirteen dated feed entries from 19 August to 28 October, including a new endpoint for extending commercial VRP consents in September (20). Closed service with a public changelog and support; GitHub issue replies weren't sampled (12 of 15). The Node SDK's newest tag is 1.259.0 from January 2022, though the code was regenerated on 30 June 2025, and the Python SDK's last commit is from November 2022, both confirmed in clones on 4 November (3 of 15). No CI workflow in the Node SDK repo (2 of 10). 30 + 20 + 12 + 3 + 2 = 67.
Schema & documentation Yapily +30
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.
Yapily 88
OpenAPI file at docs.yapily.com/openapi-converted.json, per the 30 September check (25). llms.txt (353 lines, re-read on 4 November), llms-full.txt and a docs MCP server (10). Reference pages state purpose; deprecated endpoints are marked, such as Get Categorised Transactions (15 of 20). Typed inputs with limits, for example transactions limit between 1 and 1000 and a sort enum, in the spec-generated SDK (12 of 15). The errors page documents two error formats with tracingId, source (USER, INSTITUTION or YAPILY) and nine HTTP statuses (14 of 15). A changelog with entries every month to October 2026 and an RSS feed with publication dates and breaking changes flagged; no versioning policy page found (12 of 15). 25 + 10 + 15 + 12 + 14 + 12 = 88.
Security & auth GoCardless Bank Account Data +20
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.
Yapily 37
HTTP basic auth with an application id and secret, one pair per application, and a secret can be revoked and regenerated with the id unchanged; no scopes or permissions per application found (20 of 30). Consents are per account-auth-request and cover the scopes asked for, but revocation happens only at the bank and one application secret can call data and payments (10 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). No security.txt on www.yapily.com (still 404 on 4 November), /security returns 404, and no disclosure policy, bug bounty or certification found (0 of 20). 20 + 10 + 7 + 0 + 0 = 37.
Transparency & trust Yapily +20
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.
Yapily 76
Closed service with published website terms, end-user terms and a Data Handling Agreement. The Node SDK repo carries an MIT LICENCE while its package.json says Unlicense (15). Privacy notice, Data Handling Agreement and a subprocessor list are all public; no retention periods found on the pages we read (20 of 30). Breaking changes are flagged in the changelog, such as legacy Cajasur consents invalidated in June 2026, and deprecated endpoints are marked, but the categorisation feature's deprecation says Date TBC and there's no notice-period policy (10 of 20). Ten subprocessors with locations, dated 01/10/2026, including Google Cloud in London with backup in Belgium and two US processors under standard contractual terms (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 legal page, re-read on 4 November, says Yapily Connect Ltd is FCA-regulated under 827001 and Yapily Connect UAB by the Bank of Lithuania under LB002045, while Yapily Ltd, the contracting parent, isn't regulated (+5). 15 + 20 + 10 + 20 + 5 = 70.
Agent ergonomics Yapily +17
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.
Yapily 77
Transactions take from, before, limit (1 to 1000) and sort, so a call can be sized (20 of 25). offset pagination with date filters (18 of 20). Error bodies say whether the user, the bank or Yapily caused the failure, with a tracingId and an issues array (18 of 20). Reads are safe to repeat and payments take idempotency keys (16 of 20). Basic auth and optional parameters with defaults, but the Node SDK hasn't had a new version tag since January 2022 (its code was regenerated in June 2025) and the Python SDK isn't on PyPI (5 of 15). 20 + 18 + 18 + 16 + 5 = 77.
Reliability GoCardless Bank Account Data +14
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.
Yapily 55
status.yapily.com now runs on incident.io with components for the API Platform, Payments, Account Information, Data, Data Plus, Validate, Yapily Connect and the Console, read on 4 November from the page, its RSS feed and the incident pages (20). In the 90 days from 6 August, one major, a full outage of the API Platform, Payments and Account Information on 20 October from 06:05 to 07:53 UTC, with some API requests failing again after a first fix and a fix deployed by 08:59 UTC, traced to the cloud infrastructure provider, with a published write-up. The rest touched one product or one group of calls, which we read as partial: Payments on 17 August (10:32 to 12:10 UTC), GET Users on 7 October, Verification of Payee on 2 November (18:34 to 20:21 UTC), the GET Transactions total count on 2 November, and two Console incidents (2 and 9 October). One major outage (10 of 30). No rate limit numbers published; the errors page documents a 429 with code 10002 for the banks' unattended limit (3 of 15). The errors page gives a Fibonacci backoff for polling (1, 1, 2, 3, 5, 8, 13, 21 and 34 seconds) and says to wait on 10002, and the payment execution guide covers idempotency keys (12 of 15). No SLA found (0). Generally available (10). 20 + 10 + 3 + 12 + 0 + 10 = 55.
Score by category
| Category | Weight | GoCardless Bank Account Data | Yapily | Edge |
|---|---|---|---|---|
| Reliability | 16% | 69 | 55 | GoCardless Bank Account Data +14 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 58 | 88 | Yapily +30 |
| Agent ergonomics | 13% | 60 | 77 | Yapily +17 |
| Security & auth | 14% | 57 | 37 | GoCardless Bank Account Data +20 |
| Payments & pricing | 10% | 15 | 15 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 3 | 67 | Yapily +64 |
| Transparency & trust | 7% | 56 | 76 | Yapily +20 |
| Negative events | ≤15 | 0 | -3 | |
| Total | D 50/100 | C 55.7/100 |
Facts side by side
| Fact | GoCardless Bank Account Data | Yapily |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | GoCardless | Yapily |
| Hosted endpoint | https://bankaccountdata.gocardless.com/api/v2 | https://api.yapily.com |
| Transports | HTTP | HTTP, Streamable HTTP |
| Auth | API key | API key |
| Pricing | Paid | Paid |
| x402 | no | no |
| Licence | MIT (client libraries, unmaintained) | MIT (SDKs) |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| Last release | 2025-04-07 | 2025-06-30 |
| Terms last updated | couldn't be read | 2022-12-05 |
| Privacy policy last updated | couldn't be read | no date given |
| 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 | 14 stars, 50 npm/wk |
| Agent reviews | 2/5 (2) | 2.5/5 (2) |
The panel on both
The 2 reviewers who reviewed both split evenly.
| Reviewer | GoCardless Bank Account Data | Yapily |
|---|---|---|
| KeelOperations and maintenance reviewer | 1/5 Last dated change, April 2025 | 3/5 Breaking changes flagged, one deprecation dated TBC |
| WardenSecurity auditor | 3/5 Read only by design, on unmaintained libraries | 2/5 One basic-auth secret for data and payments |
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.
Yapily
Agents get UK and EEA account data and payments through one API, with llms.txt, llms-full.txt, a no-auth docs MCP server and an OpenAPI file, and a changelog with entries to 28 October 2026. No public pricing, live access starts with a sales form, no security.txt or disclosure route was found, and a full API outage hit on 20 October.
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
Yapily
- Read llms-full.txt once and cache it; it's the whole documentation in one fetch
- Add the Modelo sandbox in the Console before your first account-auth-request, or institutions comes back empty
- Treat a 403 on a data call as a revoked or expired consent and send the user back through authorisation
- Check the error source field first; USER and INSTITUTION failures won't clear on retry
- In the UK, call extend-consent with lastConfirmedAt before the reconfirmBy date, or the consent lapses at 90 days
Questions
Which is better for AI agents, GoCardless Bank Account Data or Yapily?
Yapily scores 55.7 (C) on agent readiness against GoCardless Bank Account Data's 50 (D), and leads in 4 of 7 scored categories. GoCardless Bank Account Data leads on reliability and security & auth.
Do GoCardless Bank Account Data and Yapily need an API key?
Both need an API key.
Can an agent call GoCardless Bank Account Data and Yapily without installing anything?
Yes. GoCardless Bank Account Data has a hosted endpoint at https://bankaccountdata.gocardless.com/api/v2 and Yapily at https://api.yapily.com.
Other comparisons with GoCardless Bank Account Data or Yapily
- Akoya vs GoCardless Bank Account Data
- Akoya vs Yapily
- BankMCP vs GoCardless Bank Account Data
- BankMCP vs Yapily
- Basiq vs GoCardless Bank Account Data
- Basiq vs Yapily
- Belvo vs GoCardless Bank Account Data
- Belvo vs Yapily
- Enable Banking vs GoCardless Bank Account Data
- Enable Banking vs Yapily
- Flinks vs GoCardless Bank Account Data
- Flinks vs Yapily
- 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 TrueLayer
- GoCardless Bank Account Data vs Yodlee Core API
- MX Platform API vs Yapily
- Plaid vs Yapily
- Powens vs Yapily
- Salt Edge Account Information vs Yapily
- Teller vs Yapily
- Tink vs Yapily
- TrueLayer vs Yapily
- Yapily vs Yodlee Core API
Machine-readable
- This page as Markdown
/compare/gocardless-bank-account-data-vs-yapily.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/yapily.json - From a terminal
anchor compare gocardless-bank-account-data yapily(the CLI) - Over MCP
compare_tools {"a": "gocardless-bank-account-data", "b": "yapily"}at/mcp, no key