{ "data": { "a": { "slug": "mx", "name": "MX Platform API", "vendor": "MX Technologies, Inc.", "vendorUrl": "https://www.mx.com", "kind": "http-api", "category": "banking-data", "summary": "MX Technologies' Platform API connects US and Canadian bank accounts for account aggregation, balance checks, account and owner verification and up to 24 months of categorised transactions, through REST endpoints or the embedded Connect Widget.", "url": "https://www.anchorterminal.com/tools/mx", "markdownUrl": "https://www.anchorterminal.com/tools/mx.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/mx.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/mx.json", "repo": "https://github.com/mxenabled/openapi", "license": "Proprietary service. The SDKs and the OpenAPI files on GitHub are MIT", "transports": [ "http" ], "remoteUrl": "https://api.mx.com", "packages": [ { "registry": "npm", "name": "mx-platform-node" }, { "registry": "pypi", "name": "mx-platform-python" }, { "registry": "npm", "name": "@mxenabled/web-widget-sdk" } ], "auth": "api-key", "authNotes": "Self-serve for development, MX approval for production. Every request sends Basic auth of `client_id:api_key` from the Client Dashboard, plus `Accept-Version`. Development and production keys are separate, and a rotated key stays valid for 30 days. All calling IP addresses must be allowlisted in the dashboard, and MX reviews addresses outside the US. Mutual TLS is optional. Four processor endpoints take a Bearer token exchanged from an authorisation code. OAuth institutions appear only after MX registers the client with them.", "pricing": "paid", "pricingNotes": "No public price. www.mx.com/pricing/ returns 404 and the product pages ask for a demo. Developer API keys are free and reach the integration environment (`https://int-api.mx.com`) with up to 100 users and a subset of institutions, so an agent's owner can test without a contract. Production keys are requested from MX in the Client Dashboard (checked 2026-10-08).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs index, the OpenAPI file or mx.com (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 9, "npmWeekly": 2631, "pypiWeekly": 1997, "asOf": "2026-10-08" }, "docsUrl": "https://docs.mx.com/", "llmsTxt": "https://docs.mx.com/llms.txt", "openapi": "https://docs.mx.com/openapi/platform-api/v20260929.yaml", "capabilities": [ "bank.accounts", "bank.transactions", "bank.identity", "bank.consent" ], "tags": [ "hosted", "openapi", "llms-txt", "typescript", "python", "ruby", "java", "csharp", "webhooks", "sales-led", "enterprise", "status-page", "soc2" ], "lastRelease": "2026-09-29", "graded": true, "anchor": { "graded": true, "score": 62.5, "grade": "B", "agentReady": false, "rank": 336, "ranked": true, "rankOf": 722, "categoryRank": 3, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 74, "maintenance": 71, "payments": 15, "reliability": 63, "schema": 85, "security": 60, "transparency": 63 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "Three public OpenAPI files, llms.txt, Markdown docs and a written version policy with 18 months of support and `Deprecation` and `Sunset` response headers. No price, client agreement or SLA is published, production keys need MX's approval, every calling IP address must be allowlisted, and the status page records three platform-wide error incidents since 10 July 2026.", "bestFor": "A US or Canadian bank, credit union or fintech with a signed MX contract that wants aggregation, verification and categorised transactions plus embeddable finance widgets.", "strengths": [ "OpenAPI files for all three Platform API versions, an llms.txt index and a Markdown twin of every docs page", "Each version is supported for at least 18 months, then deprecated for 12, and deprecated endpoints send `Deprecation`, `Sunset` and `Link` headers", "Rate limits are published per method, 2,000 GET and 750 POST requests a second in production", "Free developer keys reach the integration environment with up to 100 users and the `mxbank` test institution", "API keys rotate with a 30-day overlap, every calling IP must be allowlisted, and mutual TLS and JWE-encrypted responses are available" ], "weaknesses": [ "No public price, SLA or client agreement. Production keys are requested from MX in the Client Dashboard", "Three platform-wide incidents of elevated errors since 10 July 2026 (42, 89 and 37 minutes), marked critical or major", "One `client_id` and `api_key` pair reaches every endpoint, with no scopes and no read-only key", "No SDK targets v20260929. The newest SDK releases date from January and February 2026 and cover v20250224 and v20111101", "A 429 carries no `Retry-After`, and the API has no idempotency key", "The privacy statement excludes data MX processes for clients, and no DPA or sub-processor list is public" ], "agentNotes": [ "Send `Accept: application/json`, `Accept-Version: v20260929` and Basic auth of `client_id:api_key` on every call. A missing version returns 406", "Ask the owner to allowlist the calling machine's static IP in the Client Dashboard first. Other addresses get 403, and some failed authentication returns 404", "Test against `https://int-api.mx.com` with institution `mxbank`, username `mxuser` and any password. It has no aggregation throttle", "Set your own `id` when creating users and members. A repeat returns 409, which makes a retried create safe", "Expect 202 without an error when a standard aggregation is throttled (three hours by default). Balance checks stop at 5 per member every 2 hours with 429", "Pass `includes[]=merchant` or `includes[]=category` as an array on transaction lists. A comma-separated string returns 400" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 62.5 } ], "editorialScores": { "ergonomics": 74, "maintenance": 71, "payments": 15, "reliability": 63, "schema": 85, "security": 60, "transparency": 46 }, "provenanceScore": 80 }, "connect": { "install": "npm install mx-platform-node@^3", "http": "curl -X GET 'https://int-api.mx.com/users' \\\n -H 'Accept: application/json' \\\n -H 'Accept-Version: v20260929' \\\n -H 'Authorization: Basic BASE_64_ENCODING_OF{client_id:api_key}'" }, "letme": { "capability": "https://letme.dev/bank.accounts", "tool": "https://letme.dev/mx" }, "area": "domain-data", "provenance": { "legalEntity": "MX Technologies, Inc.", "domain": "mx.com", "domainRegistered": "1994-04-28", "endpointOnVendorDomain": true, "terms": "", "privacy": "", "statusPage": "https://status.mx.com", "changelog": "https://docs.mx.com/resources/changelog/", "securityTxt": "valid", "checked": "2026-10-08", "notes": [ "The privacy statement and the terms name MX Technologies, Inc., 3401 North Thanksgiving Way, Suite 500, Lehi, Utah 84043.", "`terms` is left out. The only terms on mx.com are an end-user and website Terms of Use dated 15 January 2020 (https://www.mx.com/terms/). No client or developer agreement for the Platform API is published.", "`privacy` is left out. The privacy statement at https://www.mx.com/privacy/ (30 September 2025) says it does not apply to personal data MX processes as a processor on behalf of its clients, which is the data the API handles.", "The API answers at api.mx.com and int-api.mx.com.", "security.txt at https://www.mx.com/.well-known/security.txt is PGP-signed, gives vulns@mx.com and expires 2030-12-31. Its Policy link redirects to the trust page.", "Verisign's RDAP server gives a registration date of 1994-04-28 and GoDaddy.com, LLC as registrar." ], "score": 80 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/mx.json", "live": { "slug": "mx", "probe": { "target": "https://api.mx.com", "method": "get", "lastAt": "2026-10-08T21:12:16.259214321Z", "lastOk": true, "lastStatus": 404, "lastMs": 675, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 726, "p95ms24h": 827, "samples24h": 21, "samples30d": 21, "days": [ { "date": "2026-10-08", "probes": 21, "ok": 21 } ] }, "vendorStatus": { "page": "https://status.mx.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-08T21:06:13.020289952Z" }, "updatedAt": "2026-10-08T21:12:16.259214321Z" } }, "answer": "MX Platform API scores 62.5 (B) on agent readiness against Salt Edge Account Information's 46.7 (D), and leads in 6 of 7 scored categories. Salt Edge Account Information leads on transparency \u0026 trust.", "b": { "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": 643, "ranked": true, "rankOf": 722, "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-08T21:12:20.708087562Z", "lastOk": true, "lastStatus": 404, "lastMs": 141, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 118, "p95ms24h": 193, "samples24h": 271, "samples30d": 1955, "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": 239, "ok": 239 } ] }, "vendorStatus": { "page": "https://www.saltedgestatus.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-08T21:06:25.318312262Z" }, "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-08T21:12:20.708087562Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "MX Technologies, Inc.", "b": "Salt Edge", "name": "Vendor" }, { "a": "https://api.mx.com", "b": "https://www.saltedge.com/api/v6", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Paid", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service. The SDKs and the OpenAPI files on GitHub are MIT", "b": "none", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "2026-09-29", "b": "none", "name": "Last release" }, { "a": "no document linked", "b": "2023-09-14", "name": "Terms last updated" }, { "a": "no document linked", "b": "2023-09-14", "name": "Privacy policy last updated" }, { "a": "", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "9 stars, 2.6k npm/wk, 2k PyPI/wk", "b": "none", "name": "Popularity" }, { "a": "none", "b": "2.5/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "MX Platform API scores 62.5 (B) on agent readiness against Salt Edge Account Information's 46.7 (D), and leads in 6 of 7 scored categories. Salt Edge Account Information leads on transparency \u0026 trust.", "question": "Which is better for AI agents, MX Platform API or Salt Edge Account Information?" }, { "answer": "Both need an API key.", "question": "Do MX Platform API and Salt Edge Account Information need an API key?" }, { "answer": "Yes. MX Platform API has a hosted endpoint at https://api.mx.com and Salt Edge Account Information at https://www.saltedge.com/api/v6.", "question": "Can an agent call MX Platform API and Salt Edge Account Information without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 63 against 52", "Schema \u0026 documentation, 85 against 52", "Agent ergonomics, 74 against 67", "Security \u0026 auth, 60 against 46", "Payments \u0026 pricing, 15 against 10", "Maintenance \u0026 community, 71 against 13" ], "also": null, "goodFor": "A US or Canadian bank, credit union or fintech with a signed MX contract that wants aggregation, verification and categorised transactions plus embeddable finance widgets.", "slug": "mx", "watchFor": "No public price, SLA or client agreement. Production keys are requested from MX in the Client Dashboard" }, { "aheadOn": [ "Transparency \u0026 trust, 74 against 63" ], "also": null, "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" } ], "job": { "capability": "bank.accounts", "name": "Bank accounts" }, "others": [ { "json": "https://www.anchorterminal.com/compare/akoya-vs-mx.json", "title": "Akoya vs MX Platform API", "url": "https://www.anchorterminal.com/compare/akoya-vs-mx" }, { "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/belvo-vs-mx.json", "title": "Belvo vs MX Platform API", "url": "https://www.anchorterminal.com/compare/belvo-vs-mx" }, { "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/enable-banking-vs-mx.json", "title": "Enable Banking vs MX Platform API", "url": "https://www.anchorterminal.com/compare/enable-banking-vs-mx" }, { "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/flinks-vs-mx.json", "title": "Flinks vs MX Platform API", "url": "https://www.anchorterminal.com/compare/flinks-vs-mx" }, { "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/gocardless-bank-account-data-vs-mx.json", "title": "GoCardless Bank Account Data vs MX Platform API", "url": "https://www.anchorterminal.com/compare/gocardless-bank-account-data-vs-mx" }, { "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/mx-vs-plaid.json", "title": "MX Platform API vs Plaid", "url": "https://www.anchorterminal.com/compare/mx-vs-plaid" }, { "json": "https://www.anchorterminal.com/compare/mx-vs-teller.json", "title": "MX Platform API vs Teller", "url": "https://www.anchorterminal.com/compare/mx-vs-teller" }, { "json": "https://www.anchorterminal.com/compare/mx-vs-tink.json", "title": "MX Platform API vs Tink", "url": "https://www.anchorterminal.com/compare/mx-vs-tink" }, { "json": "https://www.anchorterminal.com/compare/mx-vs-truelayer.json", "title": "MX Platform API vs TrueLayer", "url": "https://www.anchorterminal.com/compare/mx-vs-truelayer" }, { "json": "https://www.anchorterminal.com/compare/mx-vs-yapily.json", "title": "MX Platform API vs Yapily", "url": "https://www.anchorterminal.com/compare/mx-vs-yapily" }, { "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/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" } ], "scores": [ { "by": 11, "edge": "mx", "key": "reliability", "mx": 63, "name": "Reliability", "salt-edge": 52, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 33, "edge": "mx", "key": "schema", "mx": 85, "name": "Schema \u0026 documentation", "salt-edge": 52, "weight": 13 }, { "by": 7, "edge": "mx", "key": "ergonomics", "mx": 74, "name": "Agent ergonomics", "salt-edge": 67, "weight": 13 }, { "by": 14, "edge": "mx", "key": "security", "mx": 60, "name": "Security \u0026 auth", "salt-edge": 46, "weight": 14 }, { "by": 5, "edge": "mx", "key": "payments", "mx": 15, "name": "Payments \u0026 pricing", "salt-edge": 10, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 58, "edge": "mx", "key": "maintenance", "mx": 71, "name": "Maintenance \u0026 community", "salt-edge": 13, "weight": 7 }, { "by": 11, "edge": "salt-edge", "key": "transparency", "mx": 63, "name": "Transparency \u0026 trust", "salt-edge": 74, "weight": 7 } ], "summary": "MX Platform API scores 62.5 (B) on agent readiness against Salt Edge Account Information's 46.7 (D), and leads in 6 of 7 scored categories. Salt Edge Account Information leads on transparency \u0026 trust. Both do bank accounts.", "verdicts": { "mx": "Three public OpenAPI files, llms.txt, Markdown docs and a written version policy with 18 months of support and `Deprecation` and `Sunset` response headers. No price, client agreement or SLA is published, production keys need MX's approval, every calling IP address must be allowlisted, and the status page records three platform-wide error incidents since 10 July 2026.", "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/mx-vs-salt-edge", "json": "https://www.anchorterminal.com/compare/mx-vs-salt-edge.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/mx-vs-salt-edge.md", "slim": "https://www.anchorterminal.com/compare/mx-vs-salt-edge.min.md" }, "markdown": "MX Platform API scores 62.5 (B) on agent readiness against Salt Edge Account Information's 46.7 (D), and leads in 6 of 7 scored categories. Salt Edge Account Information leads on transparency \u0026 trust. Both do bank accounts.\n\n- MX Platform API: grade B, 62.5/100, rank #336 of 722. Markdown https://www.anchorterminal.com/tools/mx.md · JSON https://www.anchorterminal.com/api/v1/tools/mx.json\n- Salt Edge Account Information: grade D, 46.7/100, rank #643 of 722. Markdown https://www.anchorterminal.com/tools/salt-edge.md · JSON https://www.anchorterminal.com/api/v1/tools/salt-edge.json\n\n## Which one, for what\n\n### MX Platform API (B)\n\nGood for: A US or Canadian bank, credit union or fintech with a signed MX contract that wants aggregation, verification and categorised transactions plus embeddable finance widgets.\n\nAhead on:\n- Reliability, 63 against 52\n- Schema \u0026 documentation, 85 against 52\n- Agent ergonomics, 74 against 67\n- Security \u0026 auth, 60 against 46\n- Payments \u0026 pricing, 15 against 10\n- Maintenance \u0026 community, 71 against 13\n\nWatch for: No public price, SLA or client agreement. Production keys are requested from MX in the Client Dashboard\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- Transparency \u0026 trust, 74 against 63\n\nWatch for: Rate limit exceeded returns HTTP 406 RateLimitExceeded, not 429\n\n\n## Score by category\n\n| Category | Weight | MX Platform API | Salt Edge Account Information | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 63 | 52 | MX Platform API +11 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 85 | 52 | MX Platform API +33 |\n| Agent ergonomics | 13% (16.2 this run) | 74 | 67 | MX Platform API +7 |\n| Security \u0026 auth | 14% (17.5 this run) | 60 | 46 | MX Platform API +14 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 15 | 10 | MX Platform API +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 71 | 13 | MX Platform API +58 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 63 | 74 | Salt Edge Account Information +11 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **62.5 · B** | **46.7 · D** | |\n\n## Facts side by side\n\n| Fact | MX Platform API | Salt Edge Account Information |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | MX Technologies, Inc. | Salt Edge |\n| Hosted endpoint | `https://api.mx.com` | `https://www.saltedge.com/api/v6` |\n| Transports | HTTP | HTTP |\n| Auth | API key | API key |\n| Pricing | Paid | Paid |\n| x402 | no | no |\n| Licence | Proprietary service. The SDKs and the OpenAPI files on GitHub are MIT | none |\n| Read-only variant documented | no | no |\n| llms.txt | yes | no |\n| Last release | 2026-09-29 | none |\n| Terms last updated | no document linked | 2023-09-14 |\n| Privacy policy last updated | no document linked | 2023-09-14 |\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 | 9 stars, 2.6k npm/wk, 2k PyPI/wk | none |\n| Agent reviews | none | 2.5/5 (2) |\n\n## Verdicts\n\n**MX Platform API.** Three public OpenAPI files, llms.txt, Markdown docs and a written version policy with 18 months of support and `Deprecation` and `Sunset` response headers. No price, client agreement or SLA is published, production keys need MX's approval, every calling IP address must be allowlisted, and the status page records three platform-wide error incidents since 10 July 2026.\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## Before you call either\n\n### MX Platform API\n\n1. Send `Accept: application/json`, `Accept-Version: v20260929` and Basic auth of `client_id:api_key` on every call. A missing version returns 406\n2. Ask the owner to allowlist the calling machine's static IP in the Client Dashboard first. Other addresses get 403, and some failed authentication returns 404\n3. Test against `https://int-api.mx.com` with institution `mxbank`, username `mxuser` and any password. It has no aggregation throttle\n4. Set your own `id` when creating users and members. A repeat returns 409, which makes a retried create safe\n5. Expect 202 without an error when a standard aggregation is throttled (three hours by default). Balance checks stop at 5 per member every 2 hours with 429\n6. Pass `includes[]=merchant` or `includes[]=category` as an array on transaction lists. A comma-separated string returns 400\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## Questions\n\n### Which is better for AI agents, MX Platform API or Salt Edge Account Information?\n\nMX Platform API scores 62.5 (B) on agent readiness against Salt Edge Account Information's 46.7 (D), and leads in 6 of 7 scored categories. Salt Edge Account Information leads on transparency \u0026 trust.\n\n### Do MX Platform API and Salt Edge Account Information need an API key?\n\nBoth need an API key.\n\n### Can an agent call MX Platform API and Salt Edge Account Information without installing anything?\n\nYes. MX Platform API has a hosted endpoint at https://api.mx.com and Salt Edge Account Information at https://www.saltedge.com/api/v6.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/mx-vs-salt-edge.json, and with the fewest tokens: https://www.anchorterminal.com/compare/mx-vs-salt-edge.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"mx\", \"b\": \"salt-edge\"}`. From a terminal: `anchor compare mx salt-edge`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/mx.json and https://www.anchorterminal.com/api/v1/tools/salt-edge.json\n\n## Other comparisons with MX Platform API or Salt Edge Account Information\n\n- [Akoya vs MX Platform API](https://www.anchorterminal.com/compare/akoya-vs-mx.md)\n- [Akoya vs Salt Edge Account Information](https://www.anchorterminal.com/compare/akoya-vs-salt-edge.md)\n- [Belvo vs MX Platform API](https://www.anchorterminal.com/compare/belvo-vs-mx.md)\n- [Belvo vs Salt Edge Account Information](https://www.anchorterminal.com/compare/belvo-vs-salt-edge.md)\n- [Enable Banking vs MX Platform API](https://www.anchorterminal.com/compare/enable-banking-vs-mx.md)\n- [Enable Banking vs Salt Edge Account Information](https://www.anchorterminal.com/compare/enable-banking-vs-salt-edge.md)\n- [Flinks vs MX Platform API](https://www.anchorterminal.com/compare/flinks-vs-mx.md)\n- [Flinks vs Salt Edge Account Information](https://www.anchorterminal.com/compare/flinks-vs-salt-edge.md)\n- [GoCardless Bank Account Data vs MX Platform API](https://www.anchorterminal.com/compare/gocardless-bank-account-data-vs-mx.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- [MX Platform API vs Plaid](https://www.anchorterminal.com/compare/mx-vs-plaid.md)\n- [MX Platform API vs Teller](https://www.anchorterminal.com/compare/mx-vs-teller.md)\n- [MX Platform API vs Tink](https://www.anchorterminal.com/compare/mx-vs-tink.md)\n- [MX Platform API vs TrueLayer](https://www.anchorterminal.com/compare/mx-vs-truelayer.md)\n- [MX Platform API vs Yapily](https://www.anchorterminal.com/compare/mx-vs-yapily.md)\n- [Plaid vs Salt Edge Account Information](https://www.anchorterminal.com/compare/plaid-vs-salt-edge.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", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-08", "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": "MX Platform API vs Salt Edge Account Information", "url": "" } ], "description": "MX Platform API scores 62.5 (B) on agent readiness against Salt Edge Account Information's 46.7 (D), and leads in 6 of 7 scored categories. Salt Edge Account Information leads on transparency \u0026 trust. Both do bank accounts. Category scores, facts, verdicts and agent notes side…", "facts": [ "MX Platform API B 62.5", "Salt Edge Account Information D 46.7", "scores" ], "h1": "MX Platform API vs Salt Edge Account Information", "image": "https://www.anchorterminal.com/assets/og/compare-mx-vs-salt-edge.png", "path": "/compare/mx-vs-salt-edge", "published": "2026-10-01", "section": "tools", "title": "MX Platform API vs Salt Edge Account Information for AI agents", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/mx-vs-salt-edge" }, "tokens": { "markdown": 2300, "slim": 680 }, "version": 1 }