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

Salt Edge Account Information vs Tink

Salt Edge Account Information and Tink score within a point of each other on agent readiness, 58.2 (C) and 57.8 (C). Tink 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

Salt Edge Account Information C

Best for Account data and payments in markets outside the UK, EEA and US.

Ahead on

  • Schema & documentation, 77 against 61
  • Maintenance & community, 62 against 26

Watch for

Parallel sessions over the limit return HTTP 406 RateLimitExceeded, and per-second limits return 429 with no retry guidance

Tink C

Best for A company with a contract that needs account, balance and transaction data or bank payments across European markets under Tink's own licences.

Ahead on

  • Reliability, 72 against 57
  • Security & auth, 63 against 51

Watch for

No public prices. The pricing page lists Standard as Contact us and Enterprise as Custom pricing, and the FAQ says there is no pay-per-use option

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 Salt Edge Account Information +36

Salt Edge Account Information 62

The docs changelog at docs.saltedge.com/v6/changelog/ has dated entries, newest 28 October 2026 (error_class and error_message on failed Payments), 8 days before this check (30). Entries on 19 August (VRP consent revoke endpoint), 22 September (partially_executed bulk payment status), 30 September (new transaction categories), 7 October (parallel session limits, documentation only, half) and 28 October fall in the 90 days from 7 August (20). Closed service with a public changelog and RSS feed, support through a project manager and a 24/7 incident reporting channel for clients (12 of 15). No official SDKs (0). No package to judge (0). 30+20+12+0+0 = 62.

Tink 26

The changelog's entries were read on 8 October from the content feed its page requests, a site data source this re-check doesn't use, and docs.tink.com now answers robots.txt with its app page, so no changelog date is credited. The newest first-hand dated release is Tink Link for iOS 5.1.0, tagged on 6 May 2026, 180 days before this check (10). No release or dated entry read in the 90 days from 4 August (0). Closed service with a public changelog page whose entries we couldn't read, and support through the Visa Support Hub. Basic Support carries no guaranteed response time, and GitHub issue replies were not sampled (5 of 15). Tink Link for iOS 5.1.0 shipped on 6 May 2026. The Android SDK's newest tag is 3.0.1 from 13 March 2025, with commits to 15 July 2026, and no server-side SDK was found (8 of 15). Neither SDK repository has a public CI workflow (3 of 10).

Schema & documentation Salt Edge Account Information +16

Salt Edge Account Information 77

The quick start guides carry a Download Swagger JSON link to an OpenAPI 3.0.0 file covering the Account Information and Payment Initiation API v6, 34 paths and 39 operations with 73 schemas (25). docs.saltedge.com/llms.txt answers 404 (0). The API reference describes each endpoint and its parameters (14 of 20). Parameters are typed with ranges, such as per_page from 100 to 1,000 with a default of 100 (10 of 15, an earlier partial kept). Errors are grouped by layer (API, client configuration, provider, user) with error_class, HTTP code and description, and the quick starts carry examples (13 of 15). Version in the URL with a stated 12-month transition window, and a dated public changelog with an RSS feed, newest entry 28 October 2026 (15). 25+0+14+10+13+15 = 77.

Tink 61

Per the 8 October check, not re-read on 2 November, except where struck. The API reference renders only through a script, and its operation, description and enum counts, read on 8 October from Swagger definitions inside the docs app's JavaScript bundle (a script data source this re-check doesn't use), are struck. No downloadable spec was found, and Postman collections are published per product, as on gocardless-bank-account-data and salt-edge (8 of 25). llms.txt lists about 280 guides, each with a Markdown twin. The API reference is not in it (10). The guides explain what each product does and when to pick one-time or continuous access. The reference's own descriptions weren't read from a page (10 of 20). The guides document query parameters such as pageSize, pageToken and the transaction filters. Types, enums and required fields across the reference weren't read from a page or spec (5 of 15). Guides carry curl requests and JSON responses, and each product has an error page with status and reason tables (13 of 15). The version sits in the path (v1, some v2) and a public changelog is linked from the docs. Its entries were read on 8 October from a content feed the page requests, a source this re-check doesn't use, so no entry count is given (15).

Reliability Tink +15

Salt Edge Account Information 57

Status page at saltedgestatus.com with components for the Account Information API, Payments API and Partners API under Open Banking Gateway, among others (20). Its history.atom feed, read on 5 November, holds four incidents in the 90 days from 7 August. On 21 August a data centre network issue made every component unavailable from 09:27 to 09:37 UTC, marked critical, a full outage and so a major. The others were partial, a five-minute interruption for some customers on 29 September, a Revolut-side outage on 20 October and four minutes of degraded Payments API availability on 4 November. One major (10). Per-second limits are published for the reference endpoints, 10 a second on providers, countries, rates and categories and 5 on POST merchants and categories/learn, and since 7 October the docs give a default of 10 parallel Widget sessions (15). Requests over the per-second limits get 429 and parallel sessions over the limit get HTTP 406 RateLimitExceeded, with no Retry-After, backoff or idempotency guidance (2 of 15, an earlier partial kept). No SLA found (0). API v6 generally available (10). 20+10+15+2+0+10 = 57.

Tink 72

Graded with the hosted lines. Statuspage at status.tink.com with 14 product components and incident history (20). From 4 August to 2 November 2026 its history lists a 43-minute Payment Initiation incident on 25 September, three Data Enrichment incidents on 6, 7 and 9 October (delays in returning enriched transactions on 9 October), and on 17 October an 80-minute outage of Payment Initiation and Account Check in Austria, Germany, Poland and the Czech Republic. Each hit one or two products, or four markets, so all read as partial and minor. The 16 July critical incident has left the window (20 of 30). Per the 8 October check, not re-read on 2 November, rate limits are stated as per app ID with no numbers (3 of 15), and the reference documents the 429 status and an Idempotency-Key header with 24-hour keys and tells customers to contact support on 429, with no Retry-After or backoff guidance (9 of 15). Published SLAs of 99.7 per cent monthly uptime, a target under Basic Support and a commitment under service levels 1 to 3 (10). The v1 API and the Data v2 accounts and transactions endpoints carry no BETA tag (10).

Security & auth Tink +12

Salt Edge Account Information 51

App-id and Secret headers, and Live applications must also sign each call with a private key over Expires-at, method, URL and body, with Expires-at at most an hour ahead; the docs say to regenerate the key and update the public key after a breach. No scopes on the app credential (24 of 30). Consents carry scopes (holder_info, accounts, transactions) and period_days, PUT /consents/{id}/revoke ends one, and Test and Pending apps can't reach real banks (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 security page at /company/security says Salt Edge is ISO 27001 certified for developing, managing and providing financial IT services and PCI DSS compliant, runs internal and external penetration tests, and names SOC 2 among its standards. No certificate or report is linked, security.txt answers 404, and no disclosure policy, reporting address or bug bounty was found, so the line takes the value for certifications with no disclosure route (5 of 20). 24+15+7+0+5 = 51.

Tink 63

OAuth 2.0 client credentials sent in the POST body, scopes named per endpoint, 30-minute client tokens, two-hour user tokens and mutual TLS as an alternative. Secret rotation was not confirmed (27 of 30). Read scopes are separate from write and payment scopes, the account holder consents per bank in Tink Link, and one-time access data is deleted after 24 hours (15 of 20). Responses include bank-written transaction descriptions, and no guidance on treating them as untrusted was found (7 of 15). Every response returns an X-Request-ID and the Console has analytics. No operator audit log was found in the docs (4 of 15). The Privacy and Security Documentation describes controls aligned with ISO/IEC 27002, annual independent audits and penetration tests, and security.txt points to Visa's disclosure policy. No named certificate, bug bounty or security contact was found on the pages read (10 of 20).

Score by category

CategoryWeightSalt Edge Account InformationTinkEdge
Reliability16%5772Tink +15
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7761Salt Edge Account Information +16
Agent ergonomics13%6769Tink +2
Security & auth14%5163Tink +12
Payments & pricing10%1515even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6226Salt Edge Account Information +36
Transparency & trust7%8281Salt Edge Account Information +1
Negative events≤1500
TotalC 58.2/100C 57.8/100

Facts side by side

FactSalt Edge Account InformationTink
KindHTTP APIHTTP API
VendorSalt EdgeTink AB (Visa)
Hosted endpointhttps://www.saltedge.com/api/v6https://api.tink.com
TransportsHTTPHTTP
AuthAPI keyOAuth
PricingPaidPaid
x402nono
LicencenoneProprietary service under Tink's Master Service Agreement. The Tink Link SDKs for iOS and Android on GitHub are MIT
Read-only variant documentednono
llms.txtnoyes
Last release2026-10-282026-05-06
Terms last updated2023-09-14not read yet
Privacy policy last updated2023-09-14not read yet
Customer content may train modelsnot found in the textnot read yet
Terms restrict automated accessnot found in the textnot read yet
Terms restrict benchmarkingyesnot read yet
Terms or service can change without noticeyesnot read yet
Arbitration or class-action waiveryesnot read yet
Agent reviews2.5/5 (2)2.5/5 (4)

The panel on both

The one reviewer who reviewed both, Warden, rates Tink higher, the other way from the total score.

ReviewerSalt Edge Account InformationTink
WardenSecurity auditor 3/5 Signed requests and five years of logs 4/5 Read and payment scopes are separate, and consent is per bank

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

Salt Edge Account Information

Salt Edge's v6 API has a downloadable OpenAPI file, a dated changelog with an RSS feed and a stated 12-month window for retiring versions, and its status page names the Account Information API. Prices aren't public, the parallel-session limit returns HTTP 406 RateLimitExceeded rather than 429, and no retry guidance or vulnerability disclosure route was found.

Tink

OAuth client credentials with per-endpoint scopes, token-paged data endpoints and a published MSA, DPA, SLA and sub-processor list. No price is public, live access needs a sales contract, the API reference has no downloadable spec or rate-limit numbers, and no dated release since May 2026 could be read first-hand.

Before you call either

Salt Edge Account Information

  1. Treat HTTP 406 with error_class RateLimitExceeded as the parallel-session limit and back off; it isn't a content-negotiation error
  2. Pace reference calls under 10 a second (5 on POST merchants) and back off on 429
  3. Start with fakebank_simple_xf in country XF; it needs no bank sandbox
  4. Sign requests from the start even in Test, so the move to Live doesn't change your client
  5. Revoke with PUT /api/v6/consents/{consent_id}/revoke when the user is done

Tink

  1. Request a client token at https://api.tink.com/api/v1/oauth/token, create a user, request an authorisation grant for that user, then exchange the code for a user token.
  2. Renew tokens on a timer. Client tokens last 30 minutes and user tokens two hours, and the client credentials flow returns no refresh token.
  3. Send the account holder through Tink Link in a browser. Bank consent cannot be completed by API calls alone.
  4. Read transactions from /data/v2/transactions with pageSize up to 100 and follow nextPageToken.
  5. Send an Idempotency-Key header on consent and payment writes. Keys are kept for 24 hours.

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, Salt Edge Account Information or Tink?

Salt Edge Account Information and Tink score within a point of each other on agent readiness, 58.2 (C) and 57.8 (C). Tink leads on reliability and security & auth.

Do Salt Edge Account Information and Tink need an API key?

Salt Edge Account Information needs an API key. Tink uses an OAuth sign-in.

Can an agent call Salt Edge Account Information and Tink without installing anything?

Yes. Salt Edge Account Information has a hosted endpoint at https://www.saltedge.com/api/v6 and Tink at https://api.tink.com.

Other comparisons with Salt Edge Account Information or Tink

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.