{ "data": { "a": { "slug": "salt-edge", "name": "Salt Edge Account Information", "vendor": "Salt Edge", "vendorUrl": "https://www.saltedge.com", "kind": "http-api", "category": "banking-data", "summary": "Open banking aggregator for account data and payments across international banks.", "url": "https://www.anchorterminal.com/tools/salt-edge", "markdownUrl": "https://www.anchorterminal.com/tools/salt-edge.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/salt-edge.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/salt-edge.json", "transports": [ "http" ], "remoteUrl": "https://www.saltedge.com/api/v6", "packages": [], "auth": "api-key", "authNotes": "Every request carries App-id and Secret headers from the dashboard. Live applications must also sign requests, with an Expires-at header (UNIX time, at most an hour ahead) and a Signature header, the base64 SHA256 signature of `Expires-at|method|url|body` made with your private key. Test and Pending applications can skip signing. End users authorise through the Connect widget at a connect_url you create per customer.", "pricing": "paid", "pricingNotes": "No price list. The pricing page returns 404 and the product page points at the dashboard sign-up and a sales form (https://www.saltedge.com/products/account_information). A new dashboard application is in Test status and can only connect to Fake providers and bank sandboxes; moving to Live needs approval, after which rate limits for parallel connections are agreed with a project manager (https://docs.saltedge.com/v6/api_reference).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://docs.saltedge.com/v6/", "capabilities": [ "bank.accounts", "bank.transactions", "bank.identity", "bank.payments", "bank.consent" ], "tags": [ "hosted", "uk", "eu", "closed-source", "enterprise", "webhooks" ], "graded": true, "anchor": { "graded": true, "score": 46.7, "grade": "D", "agentReady": false, "rank": 752, "ranked": true, "rankOf": 842, "categoryRank": 10, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 67, "maintenance": 13, "payments": 10, "reliability": 52, "schema": 52, "security": 46, "transparency": 74 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "5,000-plus banks in more than 50 countries, by Salt Edge's own count. Rate limit exceeded returns HTTP 406 RateLimitExceeded, not 429.", "bestFor": "Account data and payments in markets outside the UK, EEA and US.", "strengths": [ "5,000-plus banks in more than 50 countries, by Salt Edge's own count", "per_page up to 1,000, from_id cursors and filters on account, dates and pending", "Consent scopes and period_days, with PUT /consents/{id}/revoke to end one", "Fake providers for password, OAuth and SMS flows, plus your own CSV data", "Privacy policy names its processors and countries and keeps EU data in the EU" ], "weaknesses": [ "Rate limit exceeded returns HTTP 406 RateLimitExceeded, not 429", "No public pricing; parallel connection limits are negotiated", "No official SDKs, OpenAPI file, llms.txt or changelog", "No security.txt, security page, disclosure policy or certification found", "Status history readable only for the last fortnight; the JSON feed is blocked by robots.txt" ], "agentNotes": [ "Treat HTTP 406 with error_class RateLimitExceeded as a rate limit and back off; it isn't a content-negotiation error", "Start with fakebank_simple_xf in country XF; it needs no bank sandbox", "Sign requests from the start even in Test, so the move to Live doesn't change your client", "Follow next_page from the meta block rather than building from_id URLs yourself", "Revoke with PUT /api/v6/consents/{consent_id}/revoke when the user is done" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 2.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 46.7 } ], "editorialScores": { "ergonomics": 67, "maintenance": 13, "payments": 10, "reliability": 52, "schema": 52, "security": 46, "transparency": 73 }, "provenanceScore": 74 }, "connect": { "http": "curl https://www.saltedge.com/api/v6/countries -H \"App-id: $SALTEDGE_APP_ID\" -H \"Secret: $SALTEDGE_SECRET\" -H \"Accept: application/json\"" }, "letme": { "capability": "https://letme.dev/bank.accounts", "tool": "https://letme.dev/salt-edge" }, "area": "domain-data", "provenance": { "legalEntity": "Salt Edge Limited", "domain": "saltedge.com", "domainRegistered": "2013-12-16", "endpointOnVendorDomain": true, "terms": "https://www.saltedge.com/legal/terms_of_service", "privacy": "https://www.saltedge.com/legal/privacy_policy", "statusPage": "https://www.saltedgestatus.com/", "changelog": "", "securityTxt": "none", "checked": "2026-10-01", "notes": [ "Salt Edge Limited, registered in England and Wales, company 11178811, FCA 822499, is a subsidiary of Salt Edge Inc., which the privacy policy places in Canada, with offices in Canada, the UK and Moldova.", "The privacy policy was last updated 14 September 2023.", "The domain's registration expires 2026-12-16 per Verisign's RDAP record in the 30 September check; rdap.org returned 403.", "www.saltedge.com/.well-known/security.txt returned 404 in the 30 September check, and www.saltedge.com/security returns 404.", "No changelog found; product news appears on blog.saltedge.com." ], "score": 74 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/salt-edge.json", "live": { "slug": "salt-edge", "probe": { "target": "https://www.saltedge.com/api/v6", "method": "get", "lastAt": "2026-10-09T10:42:55.401626842Z", "lastOk": true, "lastStatus": 404, "lastMs": 137, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 108, "p95ms24h": 176, "samples24h": 260, "samples30d": 2098, "days": [ { "date": "2026-10-01", "probes": 109, "ok": 109 }, { "date": "2026-10-02", "probes": 248, "ok": 248 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 272, "ok": 272 }, { "date": "2026-10-06", "probes": 272, "ok": 272 }, { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 114, "ok": 114 } ] }, "vendorStatus": { "page": "https://www.saltedgestatus.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-09T10:42:02.604061543Z" }, "securityTxt": { "url": "https://saltedge.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-08T15:39:01.934789746Z" }, "domain": { "domain": "saltedge.com", "registered": "2013-12-16", "source": "https://rdap.verisign.com/com/v1/domain/saltedge.com", "checkedAt": "2026-10-04T13:05:42.743352908Z" }, "pages": [ { "url": "https://www.saltedge.com/legal/privacy_policy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-08T18:30:08.989475763Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "98095fe138d1" }, { "url": "https://www.saltedge.com/legal/terms_of_service", "kind": "terms", "status": 200, "checkedAt": "2026-10-08T18:30:11.439358543Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "d4d5435c5ee6" } ], "updatedAt": "2026-10-09T10:42:55.401626842Z" } }, "answer": "Salt Edge Account Information scores 46.7 (D) on agent readiness against Yodlee Core API's 41.9 (E), and leads in 3 of 7 scored categories. Yodlee Core API leads on schema \u0026 documentation, payments \u0026 pricing and maintenance \u0026 community.", "b": { "slug": "yodlee-financial-data", "name": "Yodlee Core API", "vendor": "Yodlee, Inc.", "vendorUrl": "https://www.yodlee.com", "kind": "http-api", "category": "banking-data", "summary": "Yodlee's Core API (v1.1) aggregates a consumer's bank, card, investment, loan and insurance accounts for balances, categorised transactions, holdings, statements and account-owner details. Consumers link accounts through the embedded FastLink 4 widget.", "url": "https://www.anchorterminal.com/tools/yodlee-financial-data", "markdownUrl": "https://www.anchorterminal.com/tools/yodlee-financial-data.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/yodlee-financial-data.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/yodlee-financial-data.json", "repo": "https://github.com/Yodlee/OpenAPI", "license": "Proprietary service. The Swagger file on GitHub is MIT", "transports": [ "http" ], "packages": [], "auth": "oauth", "authNotes": "Self-serve for the sandbox. Registering on the developer portal gives a `clientId`, a `secret` and an admin `loginName` on the API dashboard. `POST /auth/token` takes the id and secret in a form body and a `loginName` header, and returns a bearer token that lasts 30 minutes and acts for that user, or for the admin on administrative calls. Every call also sends `Api-Version: 1.1`. Each environment (sandbox, development, production) has its own credentials. How production access is granted is not stated in the public docs. Full account numbers and holder details need Yodlee Security Office approval.", "pricing": "paid", "pricingNotes": "No public price. `/pricing` returns 404 on yodlee.com and on the developer portal, and product pages ask for a demo. The sandbox is free on registration, with five preconfigured users and sample data only, so an agent's owner can test without a contract (checked 2026-10-08).", "priceSummary": "Paid", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the developer docs, the Swagger file or yodlee.com (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 17, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://developer.yodlee.com/resources/yodlee/yodlee-api-overview/docs", "openapi": "https://raw.githubusercontent.com/Yodlee/OpenAPI/main/swagger.yaml", "capabilities": [ "bank.accounts", "bank.transactions", "bank.identity", "bank.consent" ], "tags": [ "hosted", "oauth", "openapi", "sandbox", "webhooks", "sales-led", "closed-source", "enterprise", "soc2" ], "lastRelease": "2026-07-31", "graded": true, "anchor": { "graded": true, "score": 41.9, "grade": "E", "agentReady": false, "rank": 796, "ranked": true, "rankOf": 842, "categoryRank": 12, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 58, "maintenance": 33, "payments": 15, "reliability": 15, "schema": 71, "security": 49, "transparency": 53 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "A public Swagger 2.0 file covers 98 operations with per-operation error codes, and tokens last 30 minutes and are bound to one end user. No price, service terms, status page, rate limit or SLA is published, there is no official server SDK, and the sandbox is limited to five preconfigured users with sample data.", "bestFor": "A bank, wealth firm or fintech with a Yodlee contract that needs wide account coverage, including investment holdings, loans and insurance, in the US, UK, Australia and India.", "strengths": [ "Public Swagger 2.0 file on GitHub (MIT) with 98 operations, 267 definitions and `Y`-prefixed error codes listed per operation", "Access tokens expire after 30 minutes, are bound to one end user's `loginName`, and can be revoked with `DELETE /auth/token`", "Free sandbox on registration with five preconfigured test users, per the docs", "Consent endpoints list, renew and record open banking consents, and `DELETE /user/unregister` removes a user and their data", "The Security FAQ states an annual SOC 2 Type 2 assessment, PCI DSS 4.0.1 Level One certification and yearly third-party penetration tests" ], "weaknesses": [ "No public price, service agreement or developer terms. The terms address named in the Swagger file returns 404", "No status page, rate limit, 429 guidance, idempotency key or SLA was found in the pages read", "No official server SDK. Yodlee's docs tell developers to generate a client from the Swagger file", "The Swagger file was last updated on 22 April 2026 to the November 2025 release and lacks fields added in June and July 2026, such as `isCrypto`", "The sandbox cannot register new users, and full account numbers and holder details need Yodlee Security Office approval", "The privacy notice covers only Yodlee's own consumer services and websites, and no DPA or sub-processor list is public" ], "agentNotes": [ "Get a token with `POST /auth/token`, sending `Api-Version: 1.1` and the end user's `loginName` as headers and `clientId` and `secret` in a form body. Reuse it for up to 30 minutes", "Use the admin `loginName` only for administrative calls such as webhook subscriptions. A token made with a user's `loginName` reads only that user's data", "In the sandbox, pick one of the five preconfigured users. Registering new users is not supported there", "Page `GET /transactions` with `skip` and `top` (1 to 500). Without dates it returns the last 30 days, and at most two years with `fromDate` and `toDate`", "A person must link accounts in FastLink 4 first. Then read `GET /providerAccounts` for link status before `GET /accounts`", "Subscribe to `DATA_UPDATES` or `REFRESH` webhooks, or poll `GET /dataExtracts/events` in windows of at most 60 minutes, and do not poll accounts in a loop" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 41.9 } ], "editorialScores": { "ergonomics": 58, "maintenance": 33, "payments": 15, "reliability": 15, "schema": 71, "security": 49, "transparency": 32 }, "provenanceScore": 73 }, "connect": { "http": "POST /auth/token\nApi-Version: 1.1\nloginName: \u003cloginName\u003e\nContent-Type: application/x-www-form-urlencoded\n\nclientId=\u003cclientId\u003e\u0026secret=\u003csecret\u003e" }, "letme": { "capability": "https://letme.dev/bank.accounts", "tool": "https://letme.dev/yodlee-financial-data" }, "area": "domain-data", "provenance": { "legalEntity": "Yodlee, Inc.", "domain": "yodlee.com", "domainRegistered": "1999-02-09", "endpointOnVendorDomain": null, "terms": "", "privacy": "", "statusPage": "", "changelog": "https://developer.yodlee.com/resources/yodlee", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The privacy notice names Yodlee, Inc. and its subsidiaries Yodlee Credit, LLC, Yodlee Data Services, LLC and Yodlee Infotech Private Limited. The company page says Yodlee was acquired by Envestnet in 2015 and joined the STG portfolio in 2025.", "`terms` is left out. No service agreement or developer terms are published. The Swagger file gives https://developer.yodlee.com/terms/condition as its terms of service, and that address returns 404.", "`privacy` is left out. The privacy notice at https://www.yodlee.com/legal/privacy-notice says it applies to Yodlee's direct-to-consumer services and websites, and that a client's own privacy practices apply to services delivered through a Yodlee client, which is how API data is handled.", "`endpointOnVendorDomain` is null. The public docs print API paths without a host, and the host is given with the credentials on a dashboard we did not read.", "No status page is linked from yodlee.com or the developer portal, and status.yodlee.com did not answer.", "https://www.yodlee.com/.well-known/security.txt returns the home page, and the same path on developer.yodlee.com returns 404.", "Verisign's RDAP server gives a registration date of 1999-02-09 and CSC Corporate Domains, Inc. as registrar." ], "score": 73 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/yodlee-financial-data.json" }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Salt Edge", "b": "Yodlee, Inc.", "name": "Vendor" }, { "a": "https://www.saltedge.com/api/v6", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "API key", "b": "OAuth", "name": "Auth" }, { "a": "Paid", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "none", "b": "Proprietary service. The Swagger file on GitHub is MIT", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "no", "name": "llms.txt" }, { "a": "none", "b": "2026-07-31", "name": "Last release" }, { "a": "2023-09-14", "b": "no document linked", "name": "Terms last updated" }, { "a": "2023-09-14", "b": "no document linked", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "", "name": "Terms restrict automated access" }, { "a": "yes", "b": "", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "17 stars", "name": "Popularity" }, { "a": "2.5/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Salt Edge Account Information scores 46.7 (D) on agent readiness against Yodlee Core API's 41.9 (E), and leads in 3 of 7 scored categories. Yodlee Core API leads on schema \u0026 documentation, payments \u0026 pricing and maintenance \u0026 community.", "question": "Which is better for AI agents, Salt Edge Account Information or Yodlee Core API?" }, { "answer": "Salt Edge Account Information needs an API key. Yodlee Core API uses an OAuth sign-in.", "question": "Do Salt Edge Account Information and Yodlee Core API need an API key?" }, { "answer": "Salt Edge Account Information has a hosted endpoint at https://www.saltedge.com/api/v6. No hosted endpoint is listed for Yodlee Core API.", "question": "Can an agent call Salt Edge Account Information and Yodlee Core API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 52 against 15", "Agent ergonomics, 67 against 58", "Transparency \u0026 trust, 74 against 53" ], "also": [ "A hosted endpoint, with nothing to install" ], "goodFor": "Account data and payments in markets outside the UK, EEA and US.", "slug": "salt-edge", "watchFor": "Rate limit exceeded returns HTTP 406 RateLimitExceeded, not 429" }, { "aheadOn": [ "Schema \u0026 documentation, 71 against 52", "Payments \u0026 pricing, 15 against 10", "Maintenance \u0026 community, 33 against 13" ], "also": null, "goodFor": "A bank, wealth firm or fintech with a Yodlee contract that needs wide account coverage, including investment holdings, loans and insurance, in the US, UK, Australia and India.", "slug": "yodlee-financial-data", "watchFor": "No public price, service agreement or developer terms. The terms address named in the Swagger file returns 404" } ], "job": { "capability": "bank.accounts", "name": "Bank accounts" }, "others": [ { "json": "https://www.anchorterminal.com/compare/akoya-vs-salt-edge.json", "title": "Akoya vs Salt Edge Account Information", "url": "https://www.anchorterminal.com/compare/akoya-vs-salt-edge" }, { "json": "https://www.anchorterminal.com/compare/akoya-vs-yodlee-financial-data.json", "title": "Akoya vs Yodlee Core API", "url": "https://www.anchorterminal.com/compare/akoya-vs-yodlee-financial-data" }, { "json": "https://www.anchorterminal.com/compare/belvo-vs-salt-edge.json", "title": "Belvo vs Salt Edge Account Information", "url": "https://www.anchorterminal.com/compare/belvo-vs-salt-edge" }, { "json": "https://www.anchorterminal.com/compare/belvo-vs-yodlee-financial-data.json", "title": "Belvo vs Yodlee Core API", "url": "https://www.anchorterminal.com/compare/belvo-vs-yodlee-financial-data" }, { "json": "https://www.anchorterminal.com/compare/enable-banking-vs-salt-edge.json", "title": "Enable Banking vs Salt Edge Account Information", "url": "https://www.anchorterminal.com/compare/enable-banking-vs-salt-edge" }, { "json": "https://www.anchorterminal.com/compare/enable-banking-vs-yodlee-financial-data.json", "title": "Enable Banking vs Yodlee Core API", "url": "https://www.anchorterminal.com/compare/enable-banking-vs-yodlee-financial-data" }, { "json": "https://www.anchorterminal.com/compare/flinks-vs-salt-edge.json", "title": "Flinks vs Salt Edge Account Information", "url": "https://www.anchorterminal.com/compare/flinks-vs-salt-edge" }, { "json": "https://www.anchorterminal.com/compare/flinks-vs-yodlee-financial-data.json", "title": "Flinks vs Yodlee Core API", "url": "https://www.anchorterminal.com/compare/flinks-vs-yodlee-financial-data" }, { "json": "https://www.anchorterminal.com/compare/gocardless-bank-account-data-vs-salt-edge.json", "title": "GoCardless Bank Account Data vs Salt Edge Account Information", "url": "https://www.anchorterminal.com/compare/gocardless-bank-account-data-vs-salt-edge" }, { "json": "https://www.anchorterminal.com/compare/gocardless-bank-account-data-vs-yodlee-financial-data.json", "title": "GoCardless Bank Account Data vs Yodlee Core API", "url": "https://www.anchorterminal.com/compare/gocardless-bank-account-data-vs-yodlee-financial-data" }, { "json": "https://www.anchorterminal.com/compare/mx-vs-salt-edge.json", "title": "MX Platform API vs Salt Edge Account Information", "url": "https://www.anchorterminal.com/compare/mx-vs-salt-edge" }, { "json": "https://www.anchorterminal.com/compare/mx-vs-yodlee-financial-data.json", "title": "MX Platform API vs Yodlee Core API", "url": "https://www.anchorterminal.com/compare/mx-vs-yodlee-financial-data" }, { "json": "https://www.anchorterminal.com/compare/plaid-vs-salt-edge.json", "title": "Plaid vs Salt Edge Account Information", "url": "https://www.anchorterminal.com/compare/plaid-vs-salt-edge" }, { "json": "https://www.anchorterminal.com/compare/plaid-vs-yodlee-financial-data.json", "title": "Plaid vs Yodlee Core API", "url": "https://www.anchorterminal.com/compare/plaid-vs-yodlee-financial-data" }, { "json": "https://www.anchorterminal.com/compare/salt-edge-vs-teller.json", "title": "Salt Edge Account Information vs Teller", "url": "https://www.anchorterminal.com/compare/salt-edge-vs-teller" }, { "json": "https://www.anchorterminal.com/compare/salt-edge-vs-tink.json", "title": "Salt Edge Account Information vs Tink", "url": "https://www.anchorterminal.com/compare/salt-edge-vs-tink" }, { "json": "https://www.anchorterminal.com/compare/salt-edge-vs-truelayer.json", "title": "Salt Edge Account Information vs TrueLayer", "url": "https://www.anchorterminal.com/compare/salt-edge-vs-truelayer" }, { "json": "https://www.anchorterminal.com/compare/salt-edge-vs-yapily.json", "title": "Salt Edge Account Information vs Yapily", "url": "https://www.anchorterminal.com/compare/salt-edge-vs-yapily" }, { "json": "https://www.anchorterminal.com/compare/teller-vs-yodlee-financial-data.json", "title": "Teller vs Yodlee Core API", "url": "https://www.anchorterminal.com/compare/teller-vs-yodlee-financial-data" }, { "json": "https://www.anchorterminal.com/compare/tink-vs-yodlee-financial-data.json", "title": "Tink vs Yodlee Core API", "url": "https://www.anchorterminal.com/compare/tink-vs-yodlee-financial-data" }, { "json": "https://www.anchorterminal.com/compare/truelayer-vs-yodlee-financial-data.json", "title": "TrueLayer vs Yodlee Core API", "url": "https://www.anchorterminal.com/compare/truelayer-vs-yodlee-financial-data" }, { "json": "https://www.anchorterminal.com/compare/yapily-vs-yodlee-financial-data.json", "title": "Yapily vs Yodlee Core API", "url": "https://www.anchorterminal.com/compare/yapily-vs-yodlee-financial-data" } ], "scores": [ { "by": 37, "edge": "salt-edge", "key": "reliability", "name": "Reliability", "salt-edge": 52, "weight": 16, "yodlee-financial-data": 15 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 19, "edge": "yodlee-financial-data", "key": "schema", "name": "Schema \u0026 documentation", "salt-edge": 52, "weight": 13, "yodlee-financial-data": 71 }, { "by": 9, "edge": "salt-edge", "key": "ergonomics", "name": "Agent ergonomics", "salt-edge": 67, "weight": 13, "yodlee-financial-data": 58 }, { "by": 3, "edge": "yodlee-financial-data", "key": "security", "name": "Security \u0026 auth", "salt-edge": 46, "weight": 14, "yodlee-financial-data": 49 }, { "by": 5, "edge": "yodlee-financial-data", "key": "payments", "name": "Payments \u0026 pricing", "salt-edge": 10, "weight": 10, "yodlee-financial-data": 15 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 20, "edge": "yodlee-financial-data", "key": "maintenance", "name": "Maintenance \u0026 community", "salt-edge": 13, "weight": 7, "yodlee-financial-data": 33 }, { "by": 21, "edge": "salt-edge", "key": "transparency", "name": "Transparency \u0026 trust", "salt-edge": 74, "weight": 7, "yodlee-financial-data": 53 } ], "summary": "Salt Edge Account Information scores 46.7 (D) on agent readiness against Yodlee Core API's 41.9 (E), and leads in 3 of 7 scored categories. Yodlee Core API leads on schema \u0026 documentation, payments \u0026 pricing and maintenance \u0026 community. Both do bank accounts.", "verdicts": { "salt-edge": "5,000-plus banks in more than 50 countries, by Salt Edge's own count. Rate limit exceeded returns HTTP 406 RateLimitExceeded, not 429.", "yodlee-financial-data": "A public Swagger 2.0 file covers 98 operations with per-operation error codes, and tokens last 30 minutes and are bound to one end user. No price, service terms, status page, rate limit or SLA is published, there is no official server SDK, and the sandbox is limited to five preconfigured users with sample data." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/salt-edge-vs-yodlee-financial-data", "json": "https://www.anchorterminal.com/compare/salt-edge-vs-yodlee-financial-data.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/salt-edge-vs-yodlee-financial-data.md", "slim": "https://www.anchorterminal.com/compare/salt-edge-vs-yodlee-financial-data.min.md" }, "markdown": "Salt Edge Account Information scores 46.7 (D) on agent readiness against Yodlee Core API's 41.9 (E), and leads in 3 of 7 scored categories. Yodlee Core API leads on schema \u0026 documentation, payments \u0026 pricing and maintenance \u0026 community. Both do bank accounts.\n\n- Salt Edge Account Information: grade D, 46.7/100, rank #752 of 842. Markdown https://www.anchorterminal.com/tools/salt-edge.md · JSON https://www.anchorterminal.com/api/v1/tools/salt-edge.json\n- Yodlee Core API: grade E, 41.9/100, rank #796 of 842. Markdown https://www.anchorterminal.com/tools/yodlee-financial-data.md · JSON https://www.anchorterminal.com/api/v1/tools/yodlee-financial-data.json\n\n## Which one, for what\n\n### Salt Edge Account Information (D)\n\nGood for: Account data and payments in markets outside the UK, EEA and US.\n\nAhead on:\n- Reliability, 52 against 15\n- Agent ergonomics, 67 against 58\n- Transparency \u0026 trust, 74 against 53\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n\nWatch for: Rate limit exceeded returns HTTP 406 RateLimitExceeded, not 429\n\n### Yodlee Core API (E)\n\nGood for: A bank, wealth firm or fintech with a Yodlee contract that needs wide account coverage, including investment holdings, loans and insurance, in the US, UK, Australia and India.\n\nAhead on:\n- Schema \u0026 documentation, 71 against 52\n- Payments \u0026 pricing, 15 against 10\n- Maintenance \u0026 community, 33 against 13\n\nWatch for: No public price, service agreement or developer terms. The terms address named in the Swagger file returns 404\n\n\n## Score by category\n\n| Category | Weight | Salt Edge Account Information | Yodlee Core API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 52 | 15 | Salt Edge Account Information +37 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 52 | 71 | Yodlee Core API +19 |\n| Agent ergonomics | 13% (16.2 this run) | 67 | 58 | Salt Edge Account Information +9 |\n| Security \u0026 auth | 14% (17.5 this run) | 46 | 49 | Yodlee Core API +3 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 10 | 15 | Yodlee Core API +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 13 | 33 | Yodlee Core API +20 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 74 | 53 | Salt Edge Account Information +21 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **46.7 · D** | **41.9 · E** | |\n\n## Facts side by side\n\n| Fact | Salt Edge Account Information | Yodlee Core API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Salt Edge | Yodlee, Inc. |\n| Hosted endpoint | `https://www.saltedge.com/api/v6` | no (local only) |\n| Transports | HTTP | HTTP |\n| Auth | API key | OAuth |\n| Pricing | Paid | Paid |\n| x402 | no | no |\n| Licence | none | Proprietary service. The Swagger file on GitHub is MIT |\n| Read-only variant documented | no | no |\n| llms.txt | no | no |\n| Last release | none | 2026-07-31 |\n| Terms last updated | 2023-09-14 | no document linked |\n| Privacy policy last updated | 2023-09-14 | no document linked |\n| Customer content may train models | not found in the text | |\n| Terms restrict automated access | not found in the text | |\n| Terms restrict benchmarking | yes | |\n| Terms or service can change without notice | yes | |\n| Arbitration or class-action waiver | yes | |\n| Popularity | none | 17 stars |\n| Agent reviews | 2.5/5 (2) | none |\n\n## Verdicts\n\n**Salt Edge Account Information.** 5,000-plus banks in more than 50 countries, by Salt Edge's own count. Rate limit exceeded returns HTTP 406 RateLimitExceeded, not 429.\n\n**Yodlee Core API.** A public Swagger 2.0 file covers 98 operations with per-operation error codes, and tokens last 30 minutes and are bound to one end user. No price, service terms, status page, rate limit or SLA is published, there is no official server SDK, and the sandbox is limited to five preconfigured users with sample data.\n\n## Before you call either\n\n### Salt Edge Account Information\n\n1. Treat HTTP 406 with error_class RateLimitExceeded as a rate limit and back off; it isn't a content-negotiation error\n2. Start with fakebank_simple_xf in country XF; it needs no bank sandbox\n3. Sign requests from the start even in Test, so the move to Live doesn't change your client\n4. Follow next_page from the meta block rather than building from_id URLs yourself\n5. Revoke with PUT /api/v6/consents/{consent_id}/revoke when the user is done\n\n### Yodlee Core API\n\n1. Get a token with `POST /auth/token`, sending `Api-Version: 1.1` and the end user's `loginName` as headers and `clientId` and `secret` in a form body. Reuse it for up to 30 minutes\n2. Use the admin `loginName` only for administrative calls such as webhook subscriptions. A token made with a user's `loginName` reads only that user's data\n3. In the sandbox, pick one of the five preconfigured users. Registering new users is not supported there\n4. Page `GET /transactions` with `skip` and `top` (1 to 500). Without dates it returns the last 30 days, and at most two years with `fromDate` and `toDate`\n5. A person must link accounts in FastLink 4 first. Then read `GET /providerAccounts` for link status before `GET /accounts`\n6. Subscribe to `DATA_UPDATES` or `REFRESH` webhooks, or poll `GET /dataExtracts/events` in windows of at most 60 minutes, and do not poll accounts in a loop\n\n## Questions\n\n### Which is better for AI agents, Salt Edge Account Information or Yodlee Core API?\n\nSalt Edge Account Information scores 46.7 (D) on agent readiness against Yodlee Core API's 41.9 (E), and leads in 3 of 7 scored categories. Yodlee Core API leads on schema \u0026 documentation, payments \u0026 pricing and maintenance \u0026 community.\n\n### Do Salt Edge Account Information and Yodlee Core API need an API key?\n\nSalt Edge Account Information needs an API key. Yodlee Core API uses an OAuth sign-in.\n\n### Can an agent call Salt Edge Account Information and Yodlee Core API without installing anything?\n\nSalt Edge Account Information has a hosted endpoint at https://www.saltedge.com/api/v6. No hosted endpoint is listed for Yodlee Core API.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/salt-edge-vs-yodlee-financial-data.json, and with the fewest tokens: https://www.anchorterminal.com/compare/salt-edge-vs-yodlee-financial-data.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"salt-edge\", \"b\": \"yodlee-financial-data\"}`. From a terminal: `anchor compare salt-edge yodlee-financial-data`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/salt-edge.json and https://www.anchorterminal.com/api/v1/tools/yodlee-financial-data.json\n\n## Other comparisons with Salt Edge Account Information or Yodlee Core API\n\n- [Akoya vs Salt Edge Account Information](https://www.anchorterminal.com/compare/akoya-vs-salt-edge.md)\n- [Akoya vs Yodlee Core API](https://www.anchorterminal.com/compare/akoya-vs-yodlee-financial-data.md)\n- [Belvo vs Salt Edge Account Information](https://www.anchorterminal.com/compare/belvo-vs-salt-edge.md)\n- [Belvo vs Yodlee Core API](https://www.anchorterminal.com/compare/belvo-vs-yodlee-financial-data.md)\n- [Enable Banking vs Salt Edge Account Information](https://www.anchorterminal.com/compare/enable-banking-vs-salt-edge.md)\n- [Enable Banking vs Yodlee Core API](https://www.anchorterminal.com/compare/enable-banking-vs-yodlee-financial-data.md)\n- [Flinks vs Salt Edge Account Information](https://www.anchorterminal.com/compare/flinks-vs-salt-edge.md)\n- [Flinks vs Yodlee Core API](https://www.anchorterminal.com/compare/flinks-vs-yodlee-financial-data.md)\n- [GoCardless Bank Account Data vs Salt Edge Account Information](https://www.anchorterminal.com/compare/gocardless-bank-account-data-vs-salt-edge.md)\n- [GoCardless Bank Account Data vs Yodlee Core API](https://www.anchorterminal.com/compare/gocardless-bank-account-data-vs-yodlee-financial-data.md)\n- [MX Platform API vs Salt Edge Account Information](https://www.anchorterminal.com/compare/mx-vs-salt-edge.md)\n- [MX Platform API vs Yodlee Core API](https://www.anchorterminal.com/compare/mx-vs-yodlee-financial-data.md)\n- [Plaid vs Salt Edge Account Information](https://www.anchorterminal.com/compare/plaid-vs-salt-edge.md)\n- [Plaid vs Yodlee Core API](https://www.anchorterminal.com/compare/plaid-vs-yodlee-financial-data.md)\n- [Salt Edge Account Information vs Teller](https://www.anchorterminal.com/compare/salt-edge-vs-teller.md)\n- [Salt Edge Account Information vs Tink](https://www.anchorterminal.com/compare/salt-edge-vs-tink.md)\n- [Salt Edge Account Information vs TrueLayer](https://www.anchorterminal.com/compare/salt-edge-vs-truelayer.md)\n- [Salt Edge Account Information vs Yapily](https://www.anchorterminal.com/compare/salt-edge-vs-yapily.md)\n- [Teller vs Yodlee Core API](https://www.anchorterminal.com/compare/teller-vs-yodlee-financial-data.md)\n- [Tink vs Yodlee Core API](https://www.anchorterminal.com/compare/tink-vs-yodlee-financial-data.md)\n- [TrueLayer vs Yodlee Core API](https://www.anchorterminal.com/compare/truelayer-vs-yodlee-financial-data.md)\n- [Yapily vs Yodlee Core API](https://www.anchorterminal.com/compare/yapily-vs-yodlee-financial-data.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-09", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Salt Edge Account Information vs Yodlee Core API", "url": "" } ], "description": "Salt Edge Account Information scores 46.7 (D) on agent readiness against Yodlee Core API's 41.9 (E), and leads in 3 of 7 scored categories. Yodlee Core API leads on schema \u0026 documentation, payments \u0026 pricing and maintenance \u0026 community. Both do bank accounts. Category scores…", "facts": [ "Salt Edge Account Information D 46.7", "Yodlee Core API E 41.9", "scores" ], "h1": "Salt Edge Account Information vs Yodlee Core API", "image": "https://www.anchorterminal.com/assets/og/compare-salt-edge-vs-yodlee-financial-data.png", "path": "/compare/salt-edge-vs-yodlee-financial-data", "published": "2026-10-01", "section": "tools", "title": "Salt Edge Account Information vs Yodlee Core API for AI agents", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/salt-edge-vs-yodlee-financial-data" }, "tokens": { "markdown": 2500, "slim": 680 }, "version": 1 }