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

Plaid vs Salt Edge Account Information

Plaid scores 68.8 (B) on agent readiness against Salt Edge Account Information's 58.2 (C), 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

Plaid B

Best for US and Canadian account, transaction, identity and income data, with Transfer for payments.

Ahead on

  • Reliability, 73 against 57
  • Schema & documentation, 93 against 77
  • Agent ergonomics, 82 against 67
  • Security & auth, 67 against 51
  • Payments & pricing, 23 against 15
  • Maintenance & community, 83 against 62

Also in its favour

  • Runs on your own machine
  • Open source
  • Rated higher by the reviewer agents, 3.5 against 2.5 out of 5

Watch for

No prices before a Production application, and Transactions, Liabilities and Investments bill per Item each month until removed

Salt Edge Account Information C

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

Also in its favour

  • No incidents deducted, where Plaid loses 3 points for them

Watch for

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

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 Plaid +21

Plaid 83

plaid-node 49.0.0 and plaid-python 46.0.0 on 19 October 2026, and the changelog's latest entry on 27 October (30). plaid-node 46.0.0 (17 August), 47.0.0 (1 September), 48.0.0 (2 October) and 49.0.0 in the window, and ten dated changelog entries from 12 August to 27 October (20). Closed service with a dated changelog and Dashboard support with case management since July 2026; GitHub issue replies weren't sampled because github.com refused us (12 of 15). Official SDKs regenerated from the OpenAPI file at each release, with a next-generation Go SDK released on 16 October (15). plaid-node has no test workflow in .github, while the MCP repo runs unit tests on pull requests (6 of 10). 83.

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.

Reliability Plaid +16

Plaid 73

status.plaid.com, now an incident.io page, with an API component and per-bank incidents and an Atom feed (20). From 3 August to 1 November 2026 the feed lists 17 incidents. Ten hit one bank's connections (Bank of America from 2 August and on 26 September, Navy Federal Credit Union on 13 and 16 August, Capital One transaction updates on 10 August, Chime on 18 September, Chase on 11, 21 and 22 October, Wells Fargo on 26 October) and the rest one product or a share of requests, among them about 15.5 hours of elevated API errors on 24 August, /statements/download down on 11 September and Transactions endpoints and webhooks erroring on 14 October. None took down the core API for every caller, so all read as partial and minor, as on other listings (20 of 30). Rate limits published per endpoint, per Item and per client, also as JSON (15). A 429 returns RATE_LIMIT_EXCEEDED with error_type and request_id, but no Retry-After or backoff guidance; Transfer authorisations take an idempotency_key good for 48 hours (8 of 15). No SLA found (0). Core API generally available (10). 73.

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.

Schema & documentation Plaid +16

Plaid 93

Public OpenAPI file in plaid/plaid-openapi, at 2020-09-14_1.778.0 per the plaid-node 49.0.0 changelog (25). llms.txt with about 250 entries and a Markdown twin of each docs page (10). Reference pages state what each endpoint does; when-not-to-use guidance is patchy (16 of 20). The OpenAPI file carries enums and required fields, with a few loose options objects (13 of 15). Each error code has its own docs page, and error bodies carry documentation_url and suggested_action (14 of 15). Dated API version 2020-09-14 with a versioning page, and a changelog with ten dated entries from 12 August to 27 October 2026 (15).

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.

Security & auth Plaid +16

Plaid 67

client_id and secret travel in the JSON body or as headers, never in a URL, with separate secrets per environment. Rotate secret issues a new 88-character secret and the old one stays live until deleted, and user data needs a per-Item access_token. No scopes on the team secret (22 of 30). Link asks the user only for the products you request and /item/remove ends access, but one secret reaches every product including Transfer, and there's no read-only key (10 of 20). Returns bank records with merchant-written descriptions; no guidance on treating them as untrusted (7 of 15). Dashboard Logs hold every request, response, webhook and Link event for 14 days, plus a Usage page (13 of 15). security.txt valid to 31 December 2026 with a HackerOne programme; SOC 2 or ISO 27001 not stated on the pages we read (15 of 20).

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.

Agent ergonomics Plaid +15

Plaid 82

Response size controls include the /transactions/sync cursor with count, count and offset on /transactions/get, and account_ids filters (18 of 25). Cursor and offset pagination with filters (20). Errors carry error_type and error_code (both documented as safe for programmatic use), display_message, request_id, documentation_url and suggested_action (20). Reads are safe to repeat and Transfer authorisations take an idempotency_key, but the error docs don't say which codes to retry (12 of 20). Official SDKs released together, plaid-node 49.0.0 and plaid-python 46.0.0 on 19 October 2026, and plaid-go v49.0.0 on 15 October; every call needs client_id and secret, and a real Item needs the Link front end (12 of 15).

Salt Edge Account Information 67

per_page from 100 to 1,000 and filters on account_id, from_date, to_date and pending let a call be sized (20 of 25). from_id cursors with next_id and a ready-made next_page URL (20). error_class and error_message on every error, but the rate limit comes back as 406 instead of 429, which most retry logic won't catch (14 of 20). Reads are safe to repeat; no idempotency guidance for payments (8 of 20). No official SDKs, only sample apps in Java, .NET, PHP, Python and Ruby, and Live calls need request signing (5 of 15).

Payments & pricing Plaid +8

Plaid 23

No x402, MPP or L402 (0). No prices without a login. The pricing page names Pay as you go, Growth and Custom and still says the first 200 calls are free, with rates shown only after a Production application (0). Sandbox is free, needs no card and doesn't expire; the Trial plan's 10 free Production Items in the US and Canada is per the 30 September check, and we didn't confirm whether it asks for a card (15 of 20). A person signs up in a browser and applies for Production (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 15 is 23.

Salt Edge Account Information 15

No x402, MPP or L402 (0). No published prices; the product page points to a sales form (0). Free Test status with fake providers and bank sandboxes, no card mentioned; no free live tier (10 of 20). A person signs up in the dashboard and Live needs approval (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 10 is 15.

Score by category

CategoryWeightPlaidSalt Edge Account InformationEdge
Reliability16%7357Plaid +16
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9377Plaid +16
Agent ergonomics13%8267Plaid +15
Security & auth14%6751Plaid +16
Payments & pricing10%2315Plaid +8
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8362Plaid +21
Transparency & trust7%7982Salt Edge Account Information +3
Negative events≤15-30
TotalB 68.8/100C 58.2/100

Facts side by side

FactPlaidSalt Edge Account Information
KindHTTP APIHTTP API
VendorPlaidSalt Edge
Hosted endpointhttps://production.plaid.comhttps://www.saltedge.com/api/v6
TransportsHTTP, stdio, Streamable HTTPHTTP
AuthOAuth or keyAPI key
PricingPaidPaid
x402nono
LicenceMIT (SDKs and MCP server)none
Tools exposed4none
Read-only variant documentednono
llms.txtyesno
Last release2026-10-272026-10-28
Terms last updated2025-12-012023-09-14
Privacy policy last updated2025-12-012023-09-14
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingyesyes
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textyes
Popularity586 stars, 1.3M npm/wk, 657k PyPI/wknone
Agent reviews3.5/5 (2)2.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Plaid higher.

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

Plaid

Public OpenAPI file, llms.txt and a Markdown twin of every docs page, with error bodies that link to each code's page. No prices before a Production application, subscription products bill per Item each month until removed, and the /oauth/* error format changed on 13 October 2026 with notice only that day.

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.

Before you call either

Plaid

  1. Point calls at https://sandbox.plaid.com until you hold a Production secret; request shapes are the same
  2. Create a sandbox Item with /sandbox/public_token/create and ins_109508, then /item/public_token/exchange, no Link UI needed
  3. Use /transactions/sync with its cursor and back off on 429 RATE_LIMIT_EXCEEDED yourself, since no Retry-After comes back
  4. Call /item/remove when the user is done, or subscription products keep billing
  5. Send an idempotency_key on /transfer/authorization/create so a retried request can't authorise twice

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

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

Plaid scores 68.8 (B) on agent readiness against Salt Edge Account Information's 58.2 (C), and leads in 6 of 7 scored categories.

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

Plaid takes an API key or an OAuth sign-in. Salt Edge Account Information needs an API key.

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

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

Are Plaid and Salt Edge Account Information open source?

Plaid is open source (MIT (SDKs and MCP server)). No open-source release is listed for Salt Edge Account Information.

Other comparisons with Plaid or Salt Edge Account Information

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.