# Enable Banking vs MX Platform API

> 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 & pricing. Both do bank accounts. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/enable-banking-vs-mx
- Markdown: https://www.anchorterminal.com/compare/enable-banking-vs-mx.md (~2,250 tokens)
- Slim: https://www.anchorterminal.com/compare/enable-banking-vs-mx.min.md (~580 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/enable-banking-vs-mx.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-08

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 & pricing. Both do bank accounts.

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

## Which one, for what

### Enable Banking (D)

Good 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, 20 against 15

Watch for: No public prices and a minimum monthly invoice

### MX Platform API (B)

Good 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, 63 against 33
- Schema & documentation, 85 against 54
- Agent ergonomics, 74 against 67
- Security & auth, 60 against 47
- Transparency & trust, 63 against 49

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


## Score by category

| Category | Weight | Enable Banking | MX Platform API | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 33 | 63 | MX Platform API +30 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 54 | 85 | MX Platform API +31 |
| Agent ergonomics | 13% (16.2 this run) | 67 | 74 | MX Platform API +7 |
| Security & auth | 14% (17.5 this run) | 47 | 60 | MX Platform API +13 |
| Payments & pricing | 10% (12.5 this run) | 20 | 15 | Enable Banking +5 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 67 | 71 | MX Platform API +4 |
| Transparency & trust | 7% (8.8 this run) | 49 | 63 | MX Platform API +14 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **47.1 · D** | **62.5 · B** | |

## Facts side by side

| Fact | Enable Banking | MX Platform API |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Enable Banking | MX Technologies, Inc. |
| Hosted endpoint | `https://api.enablebanking.com` | `https://api.mx.com` |
| Transports | HTTP | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Paid | Paid |
| x402 | no | no |
| Licence | Apache-2.0 (code samples) | Proprietary service. The SDKs and the OpenAPI files on GitHub are MIT |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2026-09-09 | 2026-09-29 |
| Terms last updated | no document linked | no document linked |
| Privacy policy last updated | couldn't be read | no document linked |
| Customer content may train models |  |  |
| Terms restrict automated access |  |  |
| Terms restrict benchmarking |  |  |
| Terms or service can change without notice |  |  |
| Arbitration or class-action waiver |  |  |
| Popularity | none | 9 stars, 2.6k npm/wk, 2k PyPI/wk |
| Agent reviews | 3/5 (2) | none |

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

## 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 stop until tomorrow; it's the bank's 4-a-day cap
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

## Questions

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

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


## For agents

- 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
- 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`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/enable-banking.json and https://www.anchorterminal.com/api/v1/tools/mx.json

## Other comparisons with Enable Banking or MX Platform API

- [Akoya vs Enable Banking](https://www.anchorterminal.com/compare/akoya-vs-enable-banking.md)
- [Akoya vs MX Platform API](https://www.anchorterminal.com/compare/akoya-vs-mx.md)
- [Belvo vs Enable Banking](https://www.anchorterminal.com/compare/belvo-vs-enable-banking.md)
- [Belvo vs MX Platform API](https://www.anchorterminal.com/compare/belvo-vs-mx.md)
- [Enable Banking vs Flinks](https://www.anchorterminal.com/compare/enable-banking-vs-flinks.md)
- [Enable Banking vs GoCardless Bank Account Data](https://www.anchorterminal.com/compare/enable-banking-vs-gocardless-bank-account-data.md)
- [Enable Banking vs Plaid](https://www.anchorterminal.com/compare/enable-banking-vs-plaid.md)
- [Enable Banking vs Salt Edge Account Information](https://www.anchorterminal.com/compare/enable-banking-vs-salt-edge.md)
- [Enable Banking vs Teller](https://www.anchorterminal.com/compare/enable-banking-vs-teller.md)
- [Enable Banking vs Tink](https://www.anchorterminal.com/compare/enable-banking-vs-tink.md)
- [Enable Banking vs TrueLayer](https://www.anchorterminal.com/compare/enable-banking-vs-truelayer.md)
- [Enable Banking vs Yapily](https://www.anchorterminal.com/compare/enable-banking-vs-yapily.md)
- [Flinks vs MX Platform API](https://www.anchorterminal.com/compare/flinks-vs-mx.md)
- [GoCardless Bank Account Data vs MX Platform API](https://www.anchorterminal.com/compare/gocardless-bank-account-data-vs-mx.md)
- [MX Platform API vs Plaid](https://www.anchorterminal.com/compare/mx-vs-plaid.md)
- [MX Platform API vs Salt Edge Account Information](https://www.anchorterminal.com/compare/mx-vs-salt-edge.md)
- [MX Platform API vs Teller](https://www.anchorterminal.com/compare/mx-vs-teller.md)
- [MX Platform API vs Tink](https://www.anchorterminal.com/compare/mx-vs-tink.md)
- [MX Platform API vs TrueLayer](https://www.anchorterminal.com/compare/mx-vs-truelayer.md)
- [MX Platform API vs Yapily](https://www.anchorterminal.com/compare/mx-vs-yapily.md)