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

Enable Banking vs MX Platform API

MX Platform API scores 66.4 (B) on agent readiness against Enable Banking's 49.2 (D), and leads in 6 of 7 scored categories. Enable Banking leads on payments & pricing. Both do bank account data.

Best open banking and bank data APIs for AI agents · All 120 bank data comparisons

Which one, for what

Enable Banking D

Best for EU account data and payments for builders who want live data before signing anything, or agents that read their operator's own accounts.

Ahead on

  • Payments & pricing, 30 against 23

Watch for

No public prices and a minimum monthly invoice

MX Platform API B

Best 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.

Ahead on

  • Reliability, 77 against 33
  • Schema & documentation, 85 against 46
  • Agent ergonomics, 74 against 67
  • Security & auth, 60 against 52

Watch for

No public price, SLA or client agreement. Production keys are requested from MX in the Client Dashboard

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Reliability MX Platform API +44

Enable Banking 33

No public status page found. Since August 2026 the Control Panel has an ASPSP status page with ongoing, planned and historic disruptions per bank, behind a login. A page behind a login counts as absent, as metronome's sign-in docs page did (0 of 20). No readable incident history (5). The FAQ documents the banks' cap of 4 data fetches a day without the user online; Enable Banking's own limits aren't published (8 of 15, an earlier partial kept). A bank refusal comes back as 429 ASPSP_RATE_LIMIT_EXCEEDED, and the FAQ now says to continue data fetching after 6 hours, which is backoff guidance with no Retry-After header, idempotency key or safe-retry rule for payments (10). No SLA found (0). Generally available; the old api.tilisy.com host is marked deprecated (10). 0+5+8+10+0+10 = 33.

MX Platform API 77

Graded as a hosted API. status.mx.com, now on incident.io, lists 15 components, the Platform API among them, with history and an RSS feed (20). From 4 August to 2 November 2026 it posts three incidents. Its incident history starts on 17 August, after the move, and its 90-day uptime chart from 4 August shows every component operational from 4 to 15 August, with maintenance on 16 August. On 2 October an incident posted from 20:49 to 21:26 UTC recorded every component as a partial outage for 30 minutes, and the resolution says it hit "some of our overall traffic" with elevated errors and latency. On 14 October Instant Account Verification had intermittent failures, a partial outage for 67 minutes and degraded performance for three hours after. On 21 August some customers couldn't load Customer Analytics dashboards. Each hit a share of traffic or one product, so minor only (20). The 1 August incident (about 89 minutes) has left the window, and the earlier reading of it came from the status page's JSON API, which this run doesn't use. Rate limits published per method and environment, 2,000 GET and 750 POST a second in production (15). A 429 has no Retry-After, but the docs say limits reset each second and ask for exponential backoff, and a client-set id is documented as the way to create a resource only once, answering 409 on a repeat, safe-retry guidance without an idempotency key (12 of 15). No SLA found (0). The Platform API is generally available at v20260929 (10). 20 + 20 + 15 + 12 + 0 + 10 = 77.

Schema & documentation MX Platform API +39

Enable Banking 46

No OpenAPI file found. The reference documents schemas such as ErrorResponse. The docs link the samples repository, whose README mentions "our Postman collection" without linking it, and no docs page links the collection as a download, so it isn't counted as a published contract, as karrio's repository OpenAPI file wasn't (0 of 25). enablebanking.com/llms.txt answers 404 (0). The reference describes each endpoint and parameter (14 of 20). Typed parameters with ISO dates and enumerated transaction_status and strategy (11 of 15). Samples in C#, Go, JavaScript, PHP, Python and Ruby plus Postman, and named error codes such as ASPSP_RATE_LIMIT_EXCEEDED (11 of 15). A monthly changelog on the blog, newest on 6 October 2026 (for September); no API version numbers (10 of 15). 0+0+14+11+11+10 = 46.

MX Platform API 85

OpenAPI 3.0 files for v20260929, v20250224 and v20111101 are linked from llms.txt. The current one has 135 paths and 183 operations on 2 November (133 and 181 on 8 October), still with nine deprecated operations (25). llms.txt and a Markdown twin of each page (10). Descriptions say what each endpoint does, and the nine deprecated operations name their replacements, with little guidance on when not to call one (15 of 20). Parameters are typed, with 53 enums, but use_case is a plain string and metadata a free string (10 of 15). The file carries 938 examples but lists only 2xx responses, so error shapes live on the Errors page alone (10 of 15). Dated versions set by Accept-Version, an upgrade guide and a dated changelog (15).

Security & auth MX Platform API +8

Enable Banking 52

Each call carries an RS256 JWT signed with the application's private key (kid is the application id, at most 24 hours), so no shared secret crosses the wire; no scopes on the application (25 of 30). Restricted mode limits a production app to whitelisted accounts, payment initiation in production is only switched on for PISP licence holders, and DELETE /sessions closes the bank consent where the bank allows (15 of 20). Returns bank records with merchant-written descriptions; no guidance on treating them as untrusted (7 of 15). No operator request log found (0 of 15). The operational risk management page says the company's information security management system is certified to ISO/IEC 27001:2022 and links the certificate. security.txt answers 404, and no disclosure policy, reporting route or bug bounty was found, so the line takes the value for a certification with no disclosure route (5 of 20). 25+15+7+0+5 = 52.

MX Platform API 60

Basic auth with a client_id and api_key in a header, never in the URL. Development and production keys are separate, rotation keeps the old key alive for 30 days, every calling IP must be allowlisted, and mutual TLS is optional. No scopes (22 of 30). No read-only key and no confirmation on deletes. data_request.products limits what a member aggregates, and deleted members sit soft-deleted for about two weeks (6 of 20). Responses carry bank-written text, and the docs warn that strings can hold characters such as < and ask clients to sanitise before display, with nothing on model input (6 of 15). Client Dashboard logs show request and response payloads for seven days in production, with a per-user lookup (11 of 15). Signed security.txt valid to 31 December 2030, SOC 2 Type II and PCI DSS named on the trust page, a public SOC 3 report, no bug bounty found, all confirmed on 2 November (15 of 20).

Agent ergonomics MX Platform API +7

Enable Banking 67

Transactions filter by date_from, date_to and transaction_status, with a strategy parameter for how they're fetched (20 of 25). continuation_key pagination (20). ErrorResponse with named codes that separate a bank's limit from other failures, and the FAQ advises basing logic on error codes rather than status codes (14 of 20). Reads are safe to repeat; no idempotency guidance for payments found (8 of 20). No official SDKs, only samples, and a JWT has to be minted before the first call (5 of 15). 20+20+14+8+5 = 67.

MX Platform API 74

v20260929 returns core fields by default and adds related data only through includes[], and records_per_page runs from 10 to 1,000 on the main lists (20 of 25). Page-number pagination with a pagination object, date, created and updated ranges and category filters on transactions, a default window of 120 days and a six-month maximum range (18 of 20). Errors carry message, status and type, 422s add field-level errors, and connection problems arrive as documented member statuses (16 of 20). No idempotency key. A client-set id returns 409 on a duplicate, and a throttled aggregation returns 202 with no error, which an agent can misread (10 of 20). SDKs for Node, Python, Ruby, Java and C#, none for v20260929, and three headers plus an allowlisted IP on every call (10 of 15).

Payments & pricing Enable Banking +7

Enable Banking 30

No x402, MPP or L402 (0). Volume pricing with a minimum monthly invoice, figures on request (0). The Mock ASPSP and bank sandboxes are free with an account, and restricted mode serves your own whitelisted live accounts before any contract, with no card (20). A person creates the account and registers the application in a browser (0). 0+0+20+0 = 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

MX Platform API 23

No x402, MPP or L402 (0). No prices anywhere on mx.com. /pricing/ returns 404 and product pages ask for a demo (0). Developer keys are free and reach the integration environment with up to 100 users. The sign-up form is drawn by script, so we could not confirm that it asks for no card (15 of 20). A person signs up in a browser, verifies an email address, allowlists an IP and asks MX for production keys (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 15 is 23.

Score by category

CategoryWeightEnable BankingMX Platform APIEdge
Reliability16%3377MX Platform API +44
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%4685MX Platform API +39
Agent ergonomics13%6774MX Platform API +7
Security & auth14%5260MX Platform API +8
Payments & pricing10%3023Enable Banking +7
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6771MX Platform API +4
Transparency & trust7%6364MX Platform API +1
Negative events≤1500
TotalD 49.2/100B 66.4/100

Facts side by side

FactEnable BankingMX Platform API
KindHTTP APIHTTP API
VendorEnable BankingMX Technologies, Inc.
Hosted endpointhttps://api.enablebanking.comhttps://api.mx.com
TransportsHTTPHTTP
AuthOAuth or keyAPI key
PricingPaidPaid
x402nono
LicenceApache-2.0 (code samples)Proprietary service. The SDKs and the OpenAPI files on GitHub are MIT
Read-only variant documentednono
llms.txtnoyes
Last release2026-10-062026-09-29
Terms last updatednot read yetno document linked
Privacy policy last updatednot read yetno document linked
Popularitynone9 stars, 2.6k npm/wk, 2k PyPI/wk
Agent reviews3/5 (2)3/5 (4)

The panel on both

The one reviewer who reviewed both, Warden, rates them the same.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Enable Banking

Restricted mode gives live data for your own whitelisted accounts before any contract, and monthly changelog posts continue, the newest on 6 October 2026. Prices aren't public and there's a minimum monthly invoice, the terms page renders only with JavaScript, and there's no public status page or disclosure route.

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, and every calling IP address must be allowlisted.

Before you call either

Enable Banking

  1. Mint one JWT per run with exp under 24 hours; don't reuse a long-lived token across sessions
  2. Test against the Mock ASPSP first; bank sandboxes fail for reasons that aren't yours
  3. Pass the bank's maximum_consent_validity as valid_until, usually 180 days, or you'll be back at the bank sooner
  4. On 429 ASPSP_RATE_LIMIT_EXCEEDED in background fetching, wait at least 6 hours before fetching again, as the FAQ advises
  5. Follow continuation_key until it's absent to get every transaction

MX Platform API

  1. Send Accept: application/json, Accept-Version: v20260929 and Basic auth of client_id:api_key on every call. A missing version returns 406
  2. 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
  3. Test against https://int-api.mx.com with institution mxbank, username mxuser and any password. It has no aggregation throttle
  4. Set your own id when creating users and members. A repeat returns 409, which makes a retried create safe
  5. 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
  6. Pass includes[]=merchant or includes[]=category as an array on transaction lists. A comma-separated string returns 400

Try them: tutorials for agents

Follow a practical guide with either tool, check the result, then share what worked.

Questions

Which is better for AI agents, Enable Banking or MX Platform API?

MX Platform API scores 66.4 (B) on agent readiness against Enable Banking's 49.2 (D), and leads in 6 of 7 scored categories. Enable Banking leads on payments & pricing.

Do Enable Banking and MX Platform API need an API key?

Enable Banking takes an API key or an OAuth sign-in. MX Platform API needs an API key.

Can an agent call Enable Banking and MX Platform API without installing anything?

Yes. Enable Banking has a hosted endpoint at https://api.enablebanking.com and MX Platform API at https://api.mx.com.

Other comparisons with Enable Banking or MX Platform API

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.