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

GoCardless Bank Account Data vs Teller

GoCardless Bank Account Data scores 50 (D) on agent readiness against Teller's 10.5 (F), 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.

Ahead on

  • Reliability, 69 against 5
  • Schema & documentation, 58 against 0
  • Agent ergonomics, 60 against 0
  • Security & auth, 57 against 34
  • Payments & pricing, 15 against 0
  • Transparency & trust, 56 against 35

Watch for

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

Teller F

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

teller.io disallows ClaudeBot, anthropic-ai and Claude-Web in robots.txt, so prices, limits, errors and terms couldn't be read first-hand

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.

Reliability GoCardless Bank Account Data +64

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.

Teller 5

Hosted lines. teller.io's robots.txt disallows ClaudeBot, anthropic-ai and Claude-Web (read 5 November 2026), so every earlier reading of the site, docs and legal pages is struck. No status page is known (status.teller.io didn't resolve in the 30 September check, and no other was found) (0). No readable incident history (5). The rate-limit, 429 and Idempotency-Key readings and the beta label on payments came from the docs and are struck (0, 0). No SLA found (0). Whether the surface is generally available can't be read first-hand today (0). 0+5+0+0+0+0 = 5.

Agent ergonomics GoCardless Bank Account Data +60

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.

Teller 0

teller.io's robots.txt disallows ClaudeBot, anthropic-ai and Claude-Web (read 5 November 2026), so every earlier reading of the site, docs and legal pages is struck. Response sizing, pagination, error codes, idempotency and parameter defaults were read from the docs and are struck (0, 0, 0, 0). The one official package, teller-connect-react 0.2.3, wraps the Connect widget in JavaScript only and isn't an API SDK (0). 0+0+0+0+0 = 0.

Schema & documentation GoCardless Bank Account Data +58

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.

Teller 0

teller.io's robots.txt disallows ClaudeBot, anthropic-ai and Claude-Web (read 5 November 2026), so every earlier reading of the site, docs and legal pages is struck. The API reference, errors page, versioning page and llms.txt check all rested on it. The only first-hand source left is the teller-connect-react repository, whose README points to the Connect guide on teller.io and documents the widget, not the API. Contract, agent docs, descriptions, typed inputs, examples and errors, and versioning all 0. 0+0+0+0+0+0 = 0.

Security & auth GoCardless Bank Account Data +23

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.

Teller 34

teller.io's robots.txt disallows ClaudeBot, anthropic-ai and Claude-Web (read 5 November 2026), so every earlier reading of the site, docs and legal pages is struck, including the mutual TLS requirement and the SOC 2 Type 2 announcement. Held as partials on the vendor's own package source, where teller-connect-react's types return an accessToken per enrolment from Connect, and its products option limits an enrolment to balance, identity, transactions or verify, which is what the earlier 22 and 12 rested on apart from the struck mutual TLS reading (22, 12). Injection guidance, audit logs and the security programme had only struck evidence (0, 0, 0). 22+12+0+0+0 = 34.

Transparency & trust GoCardless Bank Account Data +21

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.

Teller 35

Closed service. The developer terms (last revised 16 February 2021 per the 1 October check) sit on teller.io; published terms that can't be read keep their licence award (the figma-mcp and sponge-wallet reading), and the Connect React wrapper declares ISC in package.json with no LICENSE file (15). The privacy policy, deprecation and subprocessor readings came from the struck site (0, 0, 0). No regulator claim can be read (+0). 15+0+0+0 = 15.

Payments & pricing GoCardless Bank Account Data +15

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.

Teller 0

teller.io's robots.txt disallows ClaudeBot, anthropic-ai and Claude-Web (read 5 November 2026), so every earlier reading of the site, docs and legal pages is struck. The per-unit prices on the home page, the free developer tier and the onboarding steps can't be read first-hand. No x402, MPP or L402 found in the package source (0). Pricing, free tier and autonomous onboarding all 0. 0+0+0+0 = 0. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 0 is 0.

Score by category

CategoryWeightGoCardless Bank Account DataTellerEdge
Reliability16%695GoCardless Bank Account Data +64
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%580GoCardless Bank Account Data +58
Agent ergonomics13%600GoCardless Bank Account Data +60
Security & auth14%5734GoCardless Bank Account Data +23
Payments & pricing10%150GoCardless Bank Account Data +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%35Teller +2
Transparency & trust7%5635GoCardless Bank Account Data +21
Negative events≤1500
TotalD 50/100F 10.5/100

Facts side by side

FactGoCardless Bank Account DataTeller
KindHTTP APIHTTP API
VendorGoCardlessTeller
Hosted endpointhttps://bankaccountdata.gocardless.com/api/v2https://api.teller.io
TransportsHTTPHTTP
AuthAPI keyToken
PricingPaidFreemium
x402nono
LicenceMIT (client libraries, unmaintained)ISC (Connect React wrapper, per package.json)
Read-only variant documentedyesno
llms.txtyesno
Last release2025-04-072025-03-18
Terms last updatedcouldn't be read2021-06-18
Privacy policy last updatedcouldn't be read2020-10-12
Customer content may train modelscouldn't be readnot found in the text
Terms restrict automated accesscouldn't be readnot found in the text
Terms restrict benchmarkingcouldn't be readyes
Terms or service can change without noticecouldn't be readyes
Arbitration or class-action waivercouldn't be readyes
Popularity88 stars10 stars
Agent reviews2/5 (2)2/5 (2)

The panel on both

The 2 reviewers who reviewed both split evenly.

ReviewerGoCardless Bank Account DataTeller
KeelOperations and maintenance reviewer 1/5 Last dated change, April 2025 2/5 Newest API version dated 2020-10-12
WardenSecurity auditor 3/5 Read only by design, on unmaintained libraries 2/5 Mutual TLS, and Zelle with no approval step

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.

Teller

Teller's site, docs and legal pages disallow our crawler in robots.txt, so this listing rests on its React Connect wrapper alone. The wrapper returns a per-enrolment access token and limits each enrolment to chosen products; prices, limits, errors and terms couldn't be read first-hand.

Before you call either

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

Teller

  1. Read Teller's own docs before building; this listing couldn't re-read them, and its earlier price, limit and error readings are struck.
  2. Pass only the products an agent needs to Teller Connect. The wrapper's types list it among undocumented options, so check its effect in Teller's Connect guide.
  3. Store the accessToken from onSuccess server-side and never in the browser or in logs; it controls one enrolment's bank data.

Questions

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

GoCardless Bank Account Data scores 50 (D) on agent readiness against Teller's 10.5 (F), and leads in 6 of 7 scored categories.

Do GoCardless Bank Account Data and Teller need an API key?

GoCardless Bank Account Data needs an API key. Teller needs an access token.

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

Yes. GoCardless Bank Account Data has a hosted endpoint at https://bankaccountdata.gocardless.com/api/v2 and Teller at https://api.teller.io.

Other comparisons with GoCardless Bank Account Data or Teller

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.