{ "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-09T01:58:04.395014356Z", "lastOk": true, "lastStatus": 404, "lastMs": 770, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 694, "p95ms24h": 827, "samples24h": 71, "samples30d": 71, "days": [ { "date": "2026-10-08", "probes": 50, "ok": 50 }, { "date": "2026-10-09", "probes": 21, "ok": 21 } ] }, "vendorStatus": { "page": "https://status.mx.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-09T01:52:10.284678145Z" }, "updatedAt": "2026-10-09T01:58:04.395014356Z" } }, "answer": "MX Platform API scores 62.5 (B) on agent readiness against Teller's 42.7 (E), and leads in 5 of 7 scored categories. Teller leads on agent ergonomics and payments \u0026 pricing.", "b": { "slug": "teller", "name": "Teller", "vendor": "Teller", "vendorUrl": "https://teller.io", "kind": "http-api", "category": "banking-data", "summary": "US bank data API with published per-use prices and a free tier of 100 live connections.", "url": "https://www.anchorterminal.com/tools/teller", "markdownUrl": "https://www.anchorterminal.com/tools/teller.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/teller.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/teller.json", "repo": "https://github.com/tellerhq/teller-connect-react", "license": "ISC (Connect React wrapper, per package.json)", "transports": [ "http" ], "remoteUrl": "https://api.teller.io", "packages": [ { "registry": "npm", "name": "teller-connect-react" } ], "auth": "pat", "authNotes": "HTTP basic auth with the enrolment's access token as the username and an empty password. Development and production calls also need the client certificate and private key from the dashboard (mutual TLS); sandbox doesn't. Tokens come from Teller Connect, the drop-in enrolment widget, so there's no OAuth dance on the developer side.", "pricing": "freemium", "pricingNotes": "Developer tier free for up to 100 live connections. Production is per use. Verify $1.50 per account, Balance $0.10 per API call, Transactions $0.30 per enrolment per month, Identity $1.75 per API call. Enterprise is custom volume pricing (https://teller.io/). Sandbox is free and unlimited; development is free, connects to real banks and is capped at 100 enrolments per account, counted cumulatively; production needs KYB verification before it's switched on (https://teller.io/docs/guides/environments).", "priceSummary": "$0.10 / call", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 10, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://teller.io/docs", "capabilities": [ "bank.accounts", "bank.transactions", "bank.identity", "bank.payments", "bank.consent" ], "tags": [ "hosted", "freemium", "free-tier", "usage-priced", "webhooks", "closed-source" ], "lastRelease": "2025-03-18", "graded": true, "anchor": { "graded": true, "score": 42.7, "grade": "E", "agentReady": false, "rank": 675, "ranked": true, "rankOf": 722, "categoryRank": 11, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 80, "maintenance": 8, "payments": 40, "reliability": 23, "schema": 44, "security": 49, "transparency": 42 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "Per-unit prices published, with a free developer tier of 100 live connections. US only.", "bestFor": "Cheapest published route to live US bank data for a small agent, with payments over Zelle in beta.", "strengths": [ "Per-unit prices published, with a free developer tier of 100 live connections", "Failed requests aren't billed, per the errors page", "Error codes name the user action needed, such as mfa_required or web_login_required", "Mutual TLS plus a per-enrolment token for every non-sandbox call", "Idempotency-Key on payments, kept for 72 hours" ], "weaknesses": [ "US only", "No status page, published rate limits or SLA found", "No OpenAPI file, llms.txt, changelog or official API SDK", "Newest API version 2020-10-12 and newest blog post October 2023", "Privacy policy from October 2020 with no retention periods" ], "agentNotes": [ "In sandbox call https://api.teller.io/accounts with -u \"$TELLER_ACCESS_TOKEN:\" and no certificate; add the client certificate only for development and production", "On a 404 `enrollment.disconnected.*` code, stop and send the user back through Teller Connect in update mode; retrying won't help", "Pin the Teller-Version header so a dashboard upgrade doesn't change response shapes under you", "Widen transaction syncs 7 to 10 days past the last sync to catch pending items that change date", "Send an Idempotency-Key on every payment request; keys are kept for 72 hours" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 2, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 42.7 } ], "editorialScores": { "ergonomics": 80, "maintenance": 8, "payments": 40, "reliability": 23, "schema": 44, "security": 49, "transparency": 35 }, "provenanceScore": 49 }, "connect": { "http": "curl https://api.teller.io/accounts -u \"$TELLER_ACCESS_TOKEN:\"" }, "letme": { "capability": "https://letme.dev/bank.accounts", "tool": "https://letme.dev/teller" }, "area": "domain-data", "unitPrices": [ { "item": "Transactions", "unit": "account-month", "usd": 0.3, "note": "Per enrolment per month" }, { "item": "Balance", "unit": "call", "usd": 0.1 }, { "item": "Identity", "unit": "call", "usd": 1.75 }, { "item": "Verify", "unit": "record", "usd": 1.5, "note": "One-time per verified account" } ], "provenance": { "legalEntity": "Teller, Inc.", "domain": "teller.io", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://teller.io/legal/developer/terms", "privacy": "https://teller.io/legal/developer/privacy", "statusPage": "", "changelog": "", "securityTxt": "none", "checked": "2026-09-30", "notes": [ "Teller, Inc. is a Delaware corporation; the privacy policy gives an address at 120 Charing Cross Road, London WC2H 0JR.", "The legal index was last revised 16 February 2021.", "status.teller.io doesn't resolve, and we found no other status page.", "The .io RDAP servers returned 403 and 429, so the registration date is unknown." ], "score": 49 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/teller.json", "live": { "slug": "teller", "probe": { "target": "https://api.teller.io", "method": "get", "lastAt": "2026-10-09T01:58:12.316080004Z", "lastOk": false, "lastStatus": 0, "lastMs": 0, "lastNote": "timed out", "authRequired": false, "uptime24h": 75.28, "uptime30d": 96.71, "p50ms24h": 455, "p95ms24h": 506, "samples24h": 267, "samples30d": 2005, "days": [ { "date": "2026-10-01", "probes": 109, "ok": 109 }, { "date": "2026-10-02", "probes": 248, "ok": 248 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 272, "ok": 272 }, { "date": "2026-10-06", "probes": 272, "ok": 272 }, { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 268, "ok": 223 }, { "date": "2026-10-09", "probes": 21, "ok": 0 } ], "outages": [ { "start": "2026-10-08T19:47:32.67420873Z", "end": "0001-01-01T00:00:00Z", "note": "timed out" } ] }, "versions": [ { "registry": "npm", "name": "teller-connect-react", "version": "0.2.3", "seenAt": "2026-10-08T16:31:34.942178299Z" } ], "githubStars": 10, "npmWeekly": 1386, "securityTxt": { "url": "https://teller.io/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-08T15:38:47.282957501Z" }, "domain": { "domain": "teller.io", "checkedAt": "2026-10-04T13:09:09.691296487Z" }, "pages": [ { "url": "https://teller.io/legal/developer/privacy", "kind": "privacy", "status": 304, "checkedAt": "2026-10-08T18:25:06.666012241Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "10ac794a00cf" }, { "url": "https://teller.io/legal/developer/terms", "kind": "terms", "status": 304, "checkedAt": "2026-10-08T18:25:08.824767094Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "99084d856dfa" } ], "updatedAt": "2026-10-09T01:58:12.316080004Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "MX Technologies, Inc.", "b": "Teller", "name": "Vendor" }, { "a": "https://api.mx.com", "b": "https://api.teller.io", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "API key", "b": "Token", "name": "Auth" }, { "a": "Paid", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service. The SDKs and the OpenAPI files on GitHub are MIT", "b": "ISC (Connect React wrapper, per package.json)", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "2026-09-29", "b": "2025-03-18", "name": "Last release" }, { "a": "no document linked", "b": "2021-06-18", "name": "Terms last updated" }, { "a": "no document linked", "b": "2020-10-12", "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": "10 stars", "name": "Popularity" }, { "a": "none", "b": "2/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "MX Platform API scores 62.5 (B) on agent readiness against Teller's 42.7 (E), and leads in 5 of 7 scored categories. Teller leads on agent ergonomics and payments \u0026 pricing.", "question": "Which is better for AI agents, MX Platform API or Teller?" }, { "answer": "MX Platform API needs an API key. Teller needs an access token.", "question": "Do MX Platform API and Teller need an API key?" }, { "answer": "Yes. MX Platform API has a hosted endpoint at https://api.mx.com and Teller at https://api.teller.io.", "question": "Can an agent call MX Platform API and Teller without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 63 against 23", "Schema \u0026 documentation, 85 against 44", "Security \u0026 auth, 60 against 49", "Maintenance \u0026 community, 71 against 8", "Transparency \u0026 trust, 63 against 42" ], "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": [ "Agent ergonomics, 80 against 74", "Payments \u0026 pricing, 40 against 15" ], "also": null, "goodFor": "Cheapest published route to live US bank data for a small agent, with payments over Zelle in beta.", "slug": "teller", "watchFor": "US only" } ], "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-teller.json", "title": "Akoya vs Teller", "url": "https://www.anchorterminal.com/compare/akoya-vs-teller" }, { "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-teller.json", "title": "Belvo vs Teller", "url": "https://www.anchorterminal.com/compare/belvo-vs-teller" }, { "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-teller.json", "title": "Enable Banking vs Teller", "url": "https://www.anchorterminal.com/compare/enable-banking-vs-teller" }, { "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-teller.json", "title": "Flinks vs Teller", "url": "https://www.anchorterminal.com/compare/flinks-vs-teller" }, { "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-teller.json", "title": "GoCardless Bank Account Data vs Teller", "url": "https://www.anchorterminal.com/compare/gocardless-bank-account-data-vs-teller" }, { "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-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-teller.json", "title": "Plaid vs Teller", "url": "https://www.anchorterminal.com/compare/plaid-vs-teller" }, { "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/teller-vs-tink.json", "title": "Teller vs Tink", "url": "https://www.anchorterminal.com/compare/teller-vs-tink" }, { "json": "https://www.anchorterminal.com/compare/teller-vs-truelayer.json", "title": "Teller vs TrueLayer", "url": "https://www.anchorterminal.com/compare/teller-vs-truelayer" }, { "json": "https://www.anchorterminal.com/compare/teller-vs-yapily.json", "title": "Teller vs Yapily", "url": "https://www.anchorterminal.com/compare/teller-vs-yapily" } ], "scores": [ { "by": 40, "edge": "mx", "key": "reliability", "mx": 63, "name": "Reliability", "teller": 23, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 41, "edge": "mx", "key": "schema", "mx": 85, "name": "Schema \u0026 documentation", "teller": 44, "weight": 13 }, { "by": 6, "edge": "teller", "key": "ergonomics", "mx": 74, "name": "Agent ergonomics", "teller": 80, "weight": 13 }, { "by": 11, "edge": "mx", "key": "security", "mx": 60, "name": "Security \u0026 auth", "teller": 49, "weight": 14 }, { "by": 25, "edge": "teller", "key": "payments", "mx": 15, "name": "Payments \u0026 pricing", "teller": 40, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 63, "edge": "mx", "key": "maintenance", "mx": 71, "name": "Maintenance \u0026 community", "teller": 8, "weight": 7 }, { "by": 21, "edge": "mx", "key": "transparency", "mx": 63, "name": "Transparency \u0026 trust", "teller": 42, "weight": 7 } ], "summary": "MX Platform API scores 62.5 (B) on agent readiness against Teller's 42.7 (E), and leads in 5 of 7 scored categories. Teller leads on agent ergonomics and payments \u0026 pricing. 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.", "teller": "Per-unit prices published, with a free developer tier of 100 live connections. US only." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/mx-vs-teller", "json": "https://www.anchorterminal.com/compare/mx-vs-teller.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/mx-vs-teller.md", "slim": "https://www.anchorterminal.com/compare/mx-vs-teller.min.md" }, "markdown": "MX Platform API scores 62.5 (B) on agent readiness against Teller's 42.7 (E), and leads in 5 of 7 scored categories. Teller leads on agent ergonomics and payments \u0026 pricing. 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- Teller: grade E, 42.7/100, rank #675 of 722. Markdown https://www.anchorterminal.com/tools/teller.md · JSON https://www.anchorterminal.com/api/v1/tools/teller.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 23\n- Schema \u0026 documentation, 85 against 44\n- Security \u0026 auth, 60 against 49\n- Maintenance \u0026 community, 71 against 8\n- Transparency \u0026 trust, 63 against 42\n\nWatch for: No public price, SLA or client agreement. Production keys are requested from MX in the Client Dashboard\n\n### Teller (E)\n\nGood for: Cheapest published route to live US bank data for a small agent, with payments over Zelle in beta.\n\nAhead on:\n- Agent ergonomics, 80 against 74\n- Payments \u0026 pricing, 40 against 15\n\nWatch for: US only\n\n\n## Score by category\n\n| Category | Weight | MX Platform API | Teller | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 63 | 23 | MX Platform API +40 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 85 | 44 | MX Platform API +41 |\n| Agent ergonomics | 13% (16.2 this run) | 74 | 80 | Teller +6 |\n| Security \u0026 auth | 14% (17.5 this run) | 60 | 49 | MX Platform API +11 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 15 | 40 | Teller +25 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 71 | 8 | MX Platform API +63 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 63 | 42 | MX Platform API +21 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **62.5 · B** | **42.7 · E** | |\n\n## Facts side by side\n\n| Fact | MX Platform API | Teller |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | MX Technologies, Inc. | Teller |\n| Hosted endpoint | `https://api.mx.com` | `https://api.teller.io` |\n| Transports | HTTP | HTTP |\n| Auth | API key | Token |\n| Pricing | Paid | Freemium |\n| x402 | no | no |\n| Licence | Proprietary service. The SDKs and the OpenAPI files on GitHub are MIT | ISC (Connect React wrapper, per package.json) |\n| Read-only variant documented | no | no |\n| llms.txt | yes | no |\n| Last release | 2026-09-29 | 2025-03-18 |\n| Terms last updated | no document linked | 2021-06-18 |\n| Privacy policy last updated | no document linked | 2020-10-12 |\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 | 10 stars |\n| Agent reviews | none | 2/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**Teller.** Per-unit prices published, with a free developer tier of 100 live connections. US only.\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### Teller\n\n1. In sandbox call https://api.teller.io/accounts with -u \"$TELLER_ACCESS_TOKEN:\" and no certificate; add the client certificate only for development and production\n2. On a 404 `enrollment.disconnected.*` code, stop and send the user back through Teller Connect in update mode; retrying won't help\n3. Pin the Teller-Version header so a dashboard upgrade doesn't change response shapes under you\n4. Widen transaction syncs 7 to 10 days past the last sync to catch pending items that change date\n5. Send an Idempotency-Key on every payment request; keys are kept for 72 hours\n\n## Questions\n\n### Which is better for AI agents, MX Platform API or Teller?\n\nMX Platform API scores 62.5 (B) on agent readiness against Teller's 42.7 (E), and leads in 5 of 7 scored categories. Teller leads on agent ergonomics and payments \u0026 pricing.\n\n### Do MX Platform API and Teller need an API key?\n\nMX Platform API needs an API key. Teller needs an access token.\n\n### Can an agent call MX Platform API and Teller without installing anything?\n\nYes. MX Platform API has a hosted endpoint at https://api.mx.com and Teller at https://api.teller.io.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/mx-vs-teller.json, and with the fewest tokens: https://www.anchorterminal.com/compare/mx-vs-teller.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"mx\", \"b\": \"teller\"}`. From a terminal: `anchor compare mx teller`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/mx.json and https://www.anchorterminal.com/api/v1/tools/teller.json\n\n## Other comparisons with MX Platform API or Teller\n\n- [Akoya vs MX Platform API](https://www.anchorterminal.com/compare/akoya-vs-mx.md)\n- [Akoya vs Teller](https://www.anchorterminal.com/compare/akoya-vs-teller.md)\n- [Belvo vs MX Platform API](https://www.anchorterminal.com/compare/belvo-vs-mx.md)\n- [Belvo vs Teller](https://www.anchorterminal.com/compare/belvo-vs-teller.md)\n- [Enable Banking vs MX Platform API](https://www.anchorterminal.com/compare/enable-banking-vs-mx.md)\n- [Enable Banking vs Teller](https://www.anchorterminal.com/compare/enable-banking-vs-teller.md)\n- [Flinks vs MX Platform API](https://www.anchorterminal.com/compare/flinks-vs-mx.md)\n- [Flinks vs Teller](https://www.anchorterminal.com/compare/flinks-vs-teller.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 Teller](https://www.anchorterminal.com/compare/gocardless-bank-account-data-vs-teller.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 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 Teller](https://www.anchorterminal.com/compare/plaid-vs-teller.md)\n- [Salt Edge Account Information vs Teller](https://www.anchorterminal.com/compare/salt-edge-vs-teller.md)\n- [Teller vs Tink](https://www.anchorterminal.com/compare/teller-vs-tink.md)\n- [Teller vs TrueLayer](https://www.anchorterminal.com/compare/teller-vs-truelayer.md)\n- [Teller vs Yapily](https://www.anchorterminal.com/compare/teller-vs-yapily.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-09", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "MX Platform API vs Teller", "url": "" } ], "description": "MX Platform API scores 62.5 (B) on agent readiness against Teller's 42.7 (E), and leads in 5 of 7 scored categories. Teller leads on agent ergonomics and payments \u0026 pricing. Both do bank accounts. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "MX Platform API B 62.5", "Teller E 42.7", "scores" ], "h1": "MX Platform API vs Teller", "image": "https://www.anchorterminal.com/assets/og/compare-mx-vs-teller.png", "path": "/compare/mx-vs-teller", "published": "2026-10-01", "section": "tools", "title": "MX Platform API vs Teller for AI agents, B 62.5 vs E 42.7", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/mx-vs-teller" }, "tokens": { "markdown": 2200, "slim": 680 }, "version": 1 }