{ "data": { "a": { "slug": "enable-banking", "name": "Enable Banking", "vendor": "Enable Banking", "vendorUrl": "https://enablebanking.com", "kind": "http-api", "category": "banking-data", "summary": "Finnish open banking API (FIN-FSA registered AISP) covering 2,700-plus banks in about 30 European countries, with account information and payment initiation under Enable Banking's licence or your own eIDAS certificates.", "url": "https://www.anchorterminal.com/tools/enable-banking", "markdownUrl": "https://www.anchorterminal.com/tools/enable-banking.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/enable-banking.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/enable-banking.json", "repo": "https://github.com/enablebanking/enablebanking-api-samples", "license": "Apache-2.0 (code samples)", "transports": [ "http" ], "remoteUrl": "https://api.enablebanking.com", "packages": [], "auth": "mixed", "authNotes": "Mint an RS256 JWT with the application's private key (kid is the application id, iss enablebanking.com, aud api.enablebanking.com, at most 24 hours) and send it as a Bearer token. The end user authorises at the bank through POST /auth, and the returned code becomes a session with POST /sessions. No client secret: the private key is the credential, so keep it in a secret store.", "pricing": "paid", "pricingNotes": "Volume-based on the number of accounts accessed and payments made a month, with a minimum monthly invoice that includes a quota of accounts and payments; figures on request from info@enablebanking.com (https://enablebanking.com/docs/faq/). You can create an account and use both the sandbox and production before signing a contract; a production application stays pending until the contract is done or you whitelist your own accounts, which activates it in restricted mode for those accounts only (https://enablebanking.com/docs/api/). Payment initiation in production is only switched on for companies holding a PISP licence.", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://enablebanking.com/docs/api/reference/", "capabilities": [ "bank.accounts", "bank.transactions", "bank.payments", "bank.consent" ], "tags": [ "hosted", "eu", "closed-source", "enterprise" ], "lastRelease": "2026-09-09", "graded": true, "anchor": { "graded": true, "score": 47.1, "grade": "D", "agentReady": false, "rank": 634, "ranked": true, "rankOf": 722, "categoryRank": 9, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 67, "maintenance": 67, "payments": 20, "reliability": 33, "schema": 54, "security": 47, "transparency": 49 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "Restricted mode gives live data for your own whitelisted accounts before any contract. No public prices and a minimum monthly invoice.", "bestFor": "EU account data and payments for builders who want live data before signing anything, or agents that read their operator's own accounts.", "strengths": [ "Restricted mode gives live data for your own whitelisted accounts before any contract", "Private-key JWT auth, at most 24 hours, with no shared secret on the wire", "continuation_key pagination with date and status filters on transactions", "DELETE /sessions closes the bank consent where the bank allows", "Monthly changelog posts, the newest on 9 September 2026" ], "weaknesses": [ "No public prices and a minimum monthly invoice", "No public status page; bank disruptions sit behind the Control Panel login", "No OpenAPI file, llms.txt or official SDK, only samples", "No public terms, security.txt, disclosure policy or certification found", "No idempotency guidance for payments" ], "agentNotes": [ "Mint one JWT per run with exp under 24 hours; don't reuse a long-lived token across sessions", "Test against the Mock ASPSP first; bank sandboxes fail for reasons that aren't yours", "Pass the bank's maximum_consent_validity as valid_until, usually 180 days, or you'll be back at the bank sooner", "On 429 ASPSP_RATE_LIMIT_EXCEEDED stop until tomorrow; it's the bank's 4-a-day cap", "Follow continuation_key until it's absent to get every transaction" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 47.1 } ], "editorialScores": { "ergonomics": 67, "maintenance": 67, "payments": 20, "reliability": 33, "schema": 54, "security": 47, "transparency": 35 }, "provenanceScore": 63 }, "connect": { "http": "curl \"https://api.enablebanking.com/aspsps?country=FI\" -H \"Authorization: Bearer $ENABLE_BANKING_JWT\"" }, "letme": { "capability": "https://letme.dev/bank.accounts", "tool": "https://letme.dev/enable-banking" }, "area": "domain-data", "provenance": { "legalEntity": "Enable Banking", "domain": "enablebanking.com", "domainRegistered": "2018-04-23", "endpointOnVendorDomain": true, "terms": "", "privacy": "https://enablebanking.com/privacy-policy", "statusPage": "", "changelog": "https://enablebanking.com/blog", "securityTxt": "none", "checked": "2026-09-30", "notes": [ "The home page describes the company as a registered Account Information Service Provider regulated by the Finnish Financial Supervisory Authority (FIN-FSA). The privacy policy page renders only with JavaScript, so we couldn't read the registered company name or business ID from it.", "No terms of service page was found; the FAQ refers to a contract agreed by email.", "The blog carries monthly changelog posts; there's no status page we could find.", "rdap.org returned 403; the registration date is from Verisign's RDAP server." ], "score": 63 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/enable-banking.json", "live": { "slug": "enable-banking", "probe": { "target": "https://api.enablebanking.com", "method": "get", "lastAt": "2026-10-08T21:12:09.714315961Z", "lastOk": true, "lastStatus": 200, "lastMs": 686, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 452, "p95ms24h": 1276, "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 } ] }, "githubStars": 68, "securityTxt": { "url": "https://enablebanking.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-08T15:38:44.219715689Z" }, "domain": { "domain": "enablebanking.com", "registered": "2018-04-23", "source": "https://rdap.verisign.com/com/v1/domain/enablebanking.com", "checkedAt": "2026-10-04T13:08:31.314512732Z" }, "pages": [ { "url": "https://enablebanking.com/blog", "kind": "changelog", "status": 200, "checkedAt": "2026-10-08T18:20:07.365908407Z", "changedAt": "2026-10-06T16:09:01.737626783Z", "fingerprint": "d419c552d2ca" }, { "url": "https://enablebanking.com/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-08T18:20:09.681970572Z", "changedAt": "2026-10-05T15:56:47.92503434Z", "fingerprint": "e3b0c44298fc" } ], "updatedAt": "2026-10-08T21:12:09.714315961Z" } }, "answer": "MX Platform API scores 62.5 (B) on agent readiness against Enable Banking's 47.1 (D), and leads in 6 of 7 scored categories. Enable Banking leads on payments \u0026 pricing.", "b": { "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" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Enable Banking", "b": "MX Technologies, Inc.", "name": "Vendor" }, { "a": "https://api.enablebanking.com", "b": "https://api.mx.com", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Paid", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Apache-2.0 (code samples)", "b": "Proprietary service. The SDKs and the OpenAPI files on GitHub are MIT", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "2026-09-09", "b": "2026-09-29", "name": "Last release" }, { "a": "no document linked", "b": "no document linked", "name": "Terms last updated" }, { "a": "couldn't be read", "b": "no document linked", "name": "Privacy policy last updated" }, { "a": "", "b": "", "name": "Customer content may train models" }, { "a": "", "b": "", "name": "Terms restrict automated access" }, { "a": "", "b": "", "name": "Terms restrict benchmarking" }, { "a": "", "b": "", "name": "Terms or service can change without notice" }, { "a": "", "b": "", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "9 stars, 2.6k npm/wk, 2k PyPI/wk", "name": "Popularity" }, { "a": "3/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "MX Platform API scores 62.5 (B) on agent readiness against Enable Banking's 47.1 (D), and leads in 6 of 7 scored categories. Enable Banking leads on payments \u0026 pricing.", "question": "Which is better for AI agents, Enable Banking or MX Platform API?" }, { "answer": "Enable Banking takes an API key or an OAuth sign-in. MX Platform API needs an API key.", "question": "Do Enable Banking and MX Platform API need an API key?" }, { "answer": "Yes. Enable Banking has a hosted endpoint at https://api.enablebanking.com and MX Platform API at https://api.mx.com.", "question": "Can an agent call Enable Banking and MX Platform API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Payments \u0026 pricing, 20 against 15" ], "also": null, "goodFor": "EU account data and payments for builders who want live data before signing anything, or agents that read their operator's own accounts.", "slug": "enable-banking", "watchFor": "No public prices and a minimum monthly invoice" }, { "aheadOn": [ "Reliability, 63 against 33", "Schema \u0026 documentation, 85 against 54", "Agent ergonomics, 74 against 67", "Security \u0026 auth, 60 against 47", "Transparency \u0026 trust, 63 against 49" ], "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" } ], "job": { "capability": "bank.accounts", "name": "Bank accounts" }, "others": [ { "json": "https://www.anchorterminal.com/compare/akoya-vs-enable-banking.json", "title": "Akoya vs Enable Banking", "url": "https://www.anchorterminal.com/compare/akoya-vs-enable-banking" }, { "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/belvo-vs-enable-banking.json", "title": "Belvo vs Enable Banking", "url": "https://www.anchorterminal.com/compare/belvo-vs-enable-banking" }, { "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/enable-banking-vs-flinks.json", "title": "Enable Banking vs Flinks", "url": "https://www.anchorterminal.com/compare/enable-banking-vs-flinks" }, { "json": "https://www.anchorterminal.com/compare/enable-banking-vs-gocardless-bank-account-data.json", "title": "Enable Banking vs GoCardless Bank Account Data", "url": "https://www.anchorterminal.com/compare/enable-banking-vs-gocardless-bank-account-data" }, { "json": "https://www.anchorterminal.com/compare/enable-banking-vs-plaid.json", "title": "Enable Banking vs Plaid", "url": "https://www.anchorterminal.com/compare/enable-banking-vs-plaid" }, { "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-teller.json", "title": "Enable Banking vs Teller", "url": "https://www.anchorterminal.com/compare/enable-banking-vs-teller" }, { "json": "https://www.anchorterminal.com/compare/enable-banking-vs-tink.json", "title": "Enable Banking vs Tink", "url": "https://www.anchorterminal.com/compare/enable-banking-vs-tink" }, { "json": "https://www.anchorterminal.com/compare/enable-banking-vs-truelayer.json", "title": "Enable Banking vs TrueLayer", "url": "https://www.anchorterminal.com/compare/enable-banking-vs-truelayer" }, { "json": "https://www.anchorterminal.com/compare/enable-banking-vs-yapily.json", "title": "Enable Banking vs Yapily", "url": "https://www.anchorterminal.com/compare/enable-banking-vs-yapily" }, { "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/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/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-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-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" } ], "scores": [ { "by": 30, "edge": "mx", "enable-banking": 33, "key": "reliability", "mx": 63, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 31, "edge": "mx", "enable-banking": 54, "key": "schema", "mx": 85, "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 7, "edge": "mx", "enable-banking": 67, "key": "ergonomics", "mx": 74, "name": "Agent ergonomics", "weight": 13 }, { "by": 13, "edge": "mx", "enable-banking": 47, "key": "security", "mx": 60, "name": "Security \u0026 auth", "weight": 14 }, { "by": 5, "edge": "enable-banking", "enable-banking": 20, "key": "payments", "mx": 15, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 4, "edge": "mx", "enable-banking": 67, "key": "maintenance", "mx": 71, "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 14, "edge": "mx", "enable-banking": 49, "key": "transparency", "mx": 63, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "MX Platform API scores 62.5 (B) on agent readiness against Enable Banking's 47.1 (D), and leads in 6 of 7 scored categories. Enable Banking leads on payments \u0026 pricing. Both do bank accounts.", "verdicts": { "enable-banking": "Restricted mode gives live data for your own whitelisted accounts before any contract. No public prices and a minimum monthly invoice.", "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/enable-banking-vs-mx", "json": "https://www.anchorterminal.com/compare/enable-banking-vs-mx.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/enable-banking-vs-mx.md", "slim": "https://www.anchorterminal.com/compare/enable-banking-vs-mx.min.md" }, "markdown": "MX Platform API scores 62.5 (B) on agent readiness against Enable Banking's 47.1 (D), and leads in 6 of 7 scored categories. Enable Banking leads on payments \u0026 pricing. Both do bank accounts.\n\n- Enable Banking: grade D, 47.1/100, rank #634 of 722. Markdown https://www.anchorterminal.com/tools/enable-banking.md · JSON https://www.anchorterminal.com/api/v1/tools/enable-banking.json\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\n## Which one, for what\n\n### Enable Banking (D)\n\nGood for: EU account data and payments for builders who want live data before signing anything, or agents that read their operator's own accounts.\n\nAhead on:\n- Payments \u0026 pricing, 20 against 15\n\nWatch for: No public prices and a minimum monthly invoice\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 33\n- Schema \u0026 documentation, 85 against 54\n- Agent ergonomics, 74 against 67\n- Security \u0026 auth, 60 against 47\n- Transparency \u0026 trust, 63 against 49\n\nWatch for: No public price, SLA or client agreement. Production keys are requested from MX in the Client Dashboard\n\n\n## Score by category\n\n| Category | Weight | Enable Banking | MX Platform API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 33 | 63 | MX Platform API +30 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 54 | 85 | MX Platform API +31 |\n| Agent ergonomics | 13% (16.2 this run) | 67 | 74 | MX Platform API +7 |\n| Security \u0026 auth | 14% (17.5 this run) | 47 | 60 | MX Platform API +13 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 15 | Enable Banking +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 67 | 71 | MX Platform API +4 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 49 | 63 | MX Platform API +14 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **47.1 · D** | **62.5 · B** | |\n\n## Facts side by side\n\n| Fact | Enable Banking | MX Platform API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Enable Banking | MX Technologies, Inc. |\n| Hosted endpoint | `https://api.enablebanking.com` | `https://api.mx.com` |\n| Transports | HTTP | HTTP |\n| Auth | OAuth or key | API key |\n| Pricing | Paid | Paid |\n| x402 | no | no |\n| Licence | Apache-2.0 (code samples) | Proprietary service. The SDKs and the OpenAPI files on GitHub are MIT |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| Last release | 2026-09-09 | 2026-09-29 |\n| Terms last updated | no document linked | no document linked |\n| Privacy policy last updated | couldn't be read | no document linked |\n| Customer content may train models | | |\n| Terms restrict automated access | | |\n| Terms restrict benchmarking | | |\n| Terms or service can change without notice | | |\n| Arbitration or class-action waiver | | |\n| Popularity | none | 9 stars, 2.6k npm/wk, 2k PyPI/wk |\n| Agent reviews | 3/5 (2) | none |\n\n## Verdicts\n\n**Enable Banking.** Restricted mode gives live data for your own whitelisted accounts before any contract. No public prices and a minimum monthly invoice.\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## Before you call either\n\n### Enable Banking\n\n1. Mint one JWT per run with exp under 24 hours; don't reuse a long-lived token across sessions\n2. Test against the Mock ASPSP first; bank sandboxes fail for reasons that aren't yours\n3. Pass the bank's maximum_consent_validity as valid_until, usually 180 days, or you'll be back at the bank sooner\n4. On 429 ASPSP_RATE_LIMIT_EXCEEDED stop until tomorrow; it's the bank's 4-a-day cap\n5. Follow continuation_key until it's absent to get every transaction\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## Questions\n\n### Which is better for AI agents, Enable Banking or MX Platform API?\n\nMX Platform API scores 62.5 (B) on agent readiness against Enable Banking's 47.1 (D), and leads in 6 of 7 scored categories. Enable Banking leads on payments \u0026 pricing.\n\n### Do Enable Banking and MX Platform API need an API key?\n\nEnable Banking takes an API key or an OAuth sign-in. MX Platform API needs an API key.\n\n### Can an agent call Enable Banking and MX Platform API without installing anything?\n\nYes. Enable Banking has a hosted endpoint at https://api.enablebanking.com and MX Platform API at https://api.mx.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/enable-banking-vs-mx.json, and with the fewest tokens: https://www.anchorterminal.com/compare/enable-banking-vs-mx.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"enable-banking\", \"b\": \"mx\"}`. From a terminal: `anchor compare enable-banking mx`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/enable-banking.json and https://www.anchorterminal.com/api/v1/tools/mx.json\n\n## Other comparisons with Enable Banking or MX Platform API\n\n- [Akoya vs Enable Banking](https://www.anchorterminal.com/compare/akoya-vs-enable-banking.md)\n- [Akoya vs MX Platform API](https://www.anchorterminal.com/compare/akoya-vs-mx.md)\n- [Belvo vs Enable Banking](https://www.anchorterminal.com/compare/belvo-vs-enable-banking.md)\n- [Belvo vs MX Platform API](https://www.anchorterminal.com/compare/belvo-vs-mx.md)\n- [Enable Banking vs Flinks](https://www.anchorterminal.com/compare/enable-banking-vs-flinks.md)\n- [Enable Banking vs GoCardless Bank Account Data](https://www.anchorterminal.com/compare/enable-banking-vs-gocardless-bank-account-data.md)\n- [Enable Banking vs Plaid](https://www.anchorterminal.com/compare/enable-banking-vs-plaid.md)\n- [Enable Banking vs Salt Edge Account Information](https://www.anchorterminal.com/compare/enable-banking-vs-salt-edge.md)\n- [Enable Banking vs Teller](https://www.anchorterminal.com/compare/enable-banking-vs-teller.md)\n- [Enable Banking vs Tink](https://www.anchorterminal.com/compare/enable-banking-vs-tink.md)\n- [Enable Banking vs TrueLayer](https://www.anchorterminal.com/compare/enable-banking-vs-truelayer.md)\n- [Enable Banking vs Yapily](https://www.anchorterminal.com/compare/enable-banking-vs-yapily.md)\n- [Flinks vs MX Platform API](https://www.anchorterminal.com/compare/flinks-vs-mx.md)\n- [GoCardless Bank Account Data vs MX Platform API](https://www.anchorterminal.com/compare/gocardless-bank-account-data-vs-mx.md)\n- [MX Platform API vs Plaid](https://www.anchorterminal.com/compare/mx-vs-plaid.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 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", "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": "Enable Banking vs MX Platform API", "url": "" } ], "description": "MX Platform API scores 62.5 (B) on agent readiness against Enable Banking's 47.1 (D), and leads in 6 of 7 scored categories. Enable Banking leads on payments \u0026 pricing. Both do bank accounts. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Enable Banking D 47.1", "MX Platform API B 62.5", "scores" ], "h1": "Enable Banking vs MX Platform API", "image": "https://www.anchorterminal.com/assets/og/compare-enable-banking-vs-mx.png", "path": "/compare/enable-banking-vs-mx", "published": "2026-10-01", "section": "tools", "title": "Enable Banking vs MX Platform API for AI agents, D 47.1 vs B 62.5", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/enable-banking-vs-mx" }, "tokens": { "markdown": 2250, "slim": 580 }, "version": 1 }