{ "data": { "a": { "slug": "mx", "name": "MX Platform API", "vendor": "MX Technologies, Inc.", "vendorUrl": "https://www.mx.com", "kind": "http-api", "category": "banking-data", "summary": "MX Technologies' Platform API connects US and Canadian bank accounts for account aggregation, balance checks, account and owner verification and up to 24 months of categorised transactions, through REST endpoints or the embedded Connect Widget.", "url": "https://www.anchorterminal.com/tools/mx", "markdownUrl": "https://www.anchorterminal.com/tools/mx.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/mx.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/mx.json", "repo": "https://github.com/mxenabled/openapi", "license": "Proprietary service. The SDKs and the OpenAPI files on GitHub are MIT", "transports": [ "http" ], "remoteUrl": "https://api.mx.com", "packages": [ { "registry": "npm", "name": "mx-platform-node" }, { "registry": "pypi", "name": "mx-platform-python" }, { "registry": "npm", "name": "@mxenabled/web-widget-sdk" } ], "auth": "api-key", "authNotes": "Self-serve for development, MX approval for production. Every request sends Basic auth of `client_id:api_key` from the Client Dashboard, plus `Accept-Version`. Development and production keys are separate, and a rotated key stays valid for 30 days. All calling IP addresses must be allowlisted in the dashboard, and MX reviews addresses outside the US. Mutual TLS is optional. Four processor endpoints take a Bearer token exchanged from an authorisation code. OAuth institutions appear only after MX registers the client with them.", "pricing": "paid", "pricingNotes": "No public price. www.mx.com/pricing/ returns 404 and the product pages ask for a demo. Developer API keys are free and reach the integration environment (`https://int-api.mx.com`) with up to 100 users and a subset of institutions, so an agent's owner can test without a contract. Production keys are requested from MX in the Client Dashboard (checked 2026-10-08).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs index, the OpenAPI file or mx.com (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 9, "npmWeekly": 2631, "pypiWeekly": 1997, "asOf": "2026-10-08" }, "docsUrl": "https://docs.mx.com/", "llmsTxt": "https://docs.mx.com/llms.txt", "openapi": "https://docs.mx.com/openapi/platform-api/v20260929.yaml", "capabilities": [ "bank.accounts", "bank.transactions", "bank.identity", "bank.consent" ], "tags": [ "hosted", "openapi", "llms-txt", "typescript", "python", "ruby", "java", "csharp", "webhooks", "sales-led", "enterprise", "status-page", "soc2" ], "lastRelease": "2026-09-29", "graded": true, "anchor": { "graded": true, "score": 62.5, "grade": "B", "agentReady": false, "rank": 336, "ranked": true, "rankOf": 722, "categoryRank": 3, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 74, "maintenance": 71, "payments": 15, "reliability": 63, "schema": 85, "security": 60, "transparency": 63 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "Three public OpenAPI files, llms.txt, Markdown docs and a written version policy with 18 months of support and `Deprecation` and `Sunset` response headers. No price, client agreement or SLA is published, production keys need MX's approval, every calling IP address must be allowlisted, and the status page records three platform-wide error incidents since 10 July 2026.", "bestFor": "A US or Canadian bank, credit union or fintech with a signed MX contract that wants aggregation, verification and categorised transactions plus embeddable finance widgets.", "strengths": [ "OpenAPI files for all three Platform API versions, an llms.txt index and a Markdown twin of every docs page", "Each version is supported for at least 18 months, then deprecated for 12, and deprecated endpoints send `Deprecation`, `Sunset` and `Link` headers", "Rate limits are published per method, 2,000 GET and 750 POST requests a second in production", "Free developer keys reach the integration environment with up to 100 users and the `mxbank` test institution", "API keys rotate with a 30-day overlap, every calling IP must be allowlisted, and mutual TLS and JWE-encrypted responses are available" ], "weaknesses": [ "No public price, SLA or client agreement. Production keys are requested from MX in the Client Dashboard", "Three platform-wide incidents of elevated errors since 10 July 2026 (42, 89 and 37 minutes), marked critical or major", "One `client_id` and `api_key` pair reaches every endpoint, with no scopes and no read-only key", "No SDK targets v20260929. The newest SDK releases date from January and February 2026 and cover v20250224 and v20111101", "A 429 carries no `Retry-After`, and the API has no idempotency key", "The privacy statement excludes data MX processes for clients, and no DPA or sub-processor list is public" ], "agentNotes": [ "Send `Accept: application/json`, `Accept-Version: v20260929` and Basic auth of `client_id:api_key` on every call. A missing version returns 406", "Ask the owner to allowlist the calling machine's static IP in the Client Dashboard first. Other addresses get 403, and some failed authentication returns 404", "Test against `https://int-api.mx.com` with institution `mxbank`, username `mxuser` and any password. It has no aggregation throttle", "Set your own `id` when creating users and members. A repeat returns 409, which makes a retried create safe", "Expect 202 without an error when a standard aggregation is throttled (three hours by default). Balance checks stop at 5 per member every 2 hours with 429", "Pass `includes[]=merchant` or `includes[]=category` as an array on transaction lists. A comma-separated string returns 400" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 62.5 } ], "editorialScores": { "ergonomics": 74, "maintenance": 71, "payments": 15, "reliability": 63, "schema": 85, "security": 60, "transparency": 46 }, "provenanceScore": 80 }, "connect": { "install": "npm install mx-platform-node@^3", "http": "curl -X GET 'https://int-api.mx.com/users' \\\n -H 'Accept: application/json' \\\n -H 'Accept-Version: v20260929' \\\n -H 'Authorization: Basic BASE_64_ENCODING_OF{client_id:api_key}'" }, "letme": { "capability": "https://letme.dev/bank.accounts", "tool": "https://letme.dev/mx" }, "area": "domain-data", "provenance": { "legalEntity": "MX Technologies, Inc.", "domain": "mx.com", "domainRegistered": "1994-04-28", "endpointOnVendorDomain": true, "terms": "", "privacy": "", "statusPage": "https://status.mx.com", "changelog": "https://docs.mx.com/resources/changelog/", "securityTxt": "valid", "checked": "2026-10-08", "notes": [ "The privacy statement and the terms name MX Technologies, Inc., 3401 North Thanksgiving Way, Suite 500, Lehi, Utah 84043.", "`terms` is left out. The only terms on mx.com are an end-user and website Terms of Use dated 15 January 2020 (https://www.mx.com/terms/). No client or developer agreement for the Platform API is published.", "`privacy` is left out. The privacy statement at https://www.mx.com/privacy/ (30 September 2025) says it does not apply to personal data MX processes as a processor on behalf of its clients, which is the data the API handles.", "The API answers at api.mx.com and int-api.mx.com.", "security.txt at https://www.mx.com/.well-known/security.txt is PGP-signed, gives vulns@mx.com and expires 2030-12-31. Its Policy link redirects to the trust page.", "Verisign's RDAP server gives a registration date of 1994-04-28 and GoDaddy.com, LLC as registrar." ], "score": 80 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/mx.json", "live": { "slug": "mx", "probe": { "target": "https://api.mx.com", "method": "get", "lastAt": "2026-10-08T21:12:16.259214321Z", "lastOk": true, "lastStatus": 404, "lastMs": 675, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 726, "p95ms24h": 827, "samples24h": 21, "samples30d": 21, "days": [ { "date": "2026-10-08", "probes": 21, "ok": 21 } ] }, "vendorStatus": { "page": "https://status.mx.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-08T21:06:13.020289952Z" }, "updatedAt": "2026-10-08T21:12:16.259214321Z" } }, "answer": "MX Platform API scores 62.5 (B) on agent readiness against Yapily's 57.6 (C), and leads in 4 of 7 scored categories. Yapily leads on transparency \u0026 trust.", "b": { "slug": "yapily", "name": "Yapily", "vendor": "Yapily", "vendorUrl": "https://www.yapily.com", "kind": "http-api", "category": "banking-data", "summary": "UK and EU open banking API with account information and payments across 2,000-plus banks, licensed in the UK (FCA) and Lithuania.", "url": "https://www.anchorterminal.com/tools/yapily", "markdownUrl": "https://www.anchorterminal.com/tools/yapily.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/yapily.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/yapily.json", "repo": "https://github.com/yapily/yapily-sdk-nodejs", "license": "MIT (SDKs)", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.yapily.com", "packages": [ { "registry": "npm", "name": "@yapily/yapily-api" } ], "auth": "api-key", "authNotes": "HTTP basic auth with the application id as the username and the application secret as the password, downloaded as a JSON file from the Console. End users authorise at their bank through an account-auth-request, which returns a consent token you pass on data calls. The docs MCP server at docs.yapily.com/mcp needs no auth at all, because it only searches the documentation.", "pricing": "paid", "pricingNotes": "No published prices. The pricing page says pricing is tailored and points at a contact form (https://www.yapily.com/pricing). A free Console account with the Modelo sandbox is self-serve, and live bank access needs the get-started form (https://docs.yapily.com/getting-started/get-started.md).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 14, "npmWeekly": 50, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://docs.yapily.com", "llmsTxt": "https://docs.yapily.com/llms.txt", "openapi": "https://docs.yapily.com/openapi-converted.json", "capabilities": [ "bank.accounts", "bank.transactions", "bank.identity", "bank.payments", "bank.consent" ], "tags": [ "hosted", "llms-txt", "openapi", "mcp", "uk", "eu", "webhooks", "enterprise", "closed-source" ], "lastRelease": "2025-06-30", "graded": true, "anchor": { "graded": true, "score": 57.6, "grade": "C", "agentReady": false, "rank": 469, "ranked": true, "rankOf": 722, "categoryRank": 6, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 77, "maintenance": 67, "payments": 10, "reliability": 55, "schema": 88, "security": 37, "transparency": 71 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "llms.txt, llms-full.txt, a no-auth docs MCP server and an OpenAPI file. No public pricing; live access starts with a sales form.", "bestFor": "UK and EEA data and payments from one API, for builders who want docs an agent can read in one fetch.", "strengths": [ "llms.txt, llms-full.txt, a no-auth docs MCP server and an OpenAPI file", "Error bodies carry a source of USER, INSTITUTION or YAPILY and a tracingId", "Changelog with ten dated entries from July to September 2026, breaking changes flagged", "Public subprocessor list with locations, primary hosting in London", "Transactions take from, before, limit up to 1,000 and sort" ], "weaknesses": [ "No public pricing; live access starts with a sales form", "No security.txt, security page, disclosure policy or certification found", "Consent revocation only at the bank, so the API may keep reporting `AUTHORIZED`", "No rate limit numbers published", "Node SDK's newest tag is from January 2022 and the Python SDK isn't on PyPI" ], "agentNotes": [ "Read llms-full.txt once and cache it; it's the whole documentation in one fetch", "Add the Modelo sandbox in the Console before your first account-auth-request, or institutions comes back empty", "Treat a 403 on a data call as a revoked or expired consent and send the user back through authorisation", "Check the error source field first; USER and INSTITUTION failures won't clear on retry", "In the UK, call extend-consent with lastConfirmedAt before the reconfirmBy date, or the consent lapses at 90 days" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 2.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 57.6 } ], "editorialScores": { "ergonomics": 77, "maintenance": 67, "payments": 10, "reliability": 55, "schema": 88, "security": 37, "transparency": 70 }, "provenanceScore": 72 }, "connect": { "http": "curl -u \"$YAPILY_APPLICATION_ID:$YAPILY_APPLICATION_SECRET\" https://api.yapily.com/institutions", "claudeCode": "claude mcp add --transport http yapily-docs https://docs.yapily.com/mcp", "config": { "mcpServers": { "yapily-docs": { "type": "http", "url": "https://docs.yapily.com/mcp" } } } }, "letme": { "capability": "https://letme.dev/bank.accounts", "tool": "https://letme.dev/yapily" }, "area": "domain-data", "provenance": { "legalEntity": "Yapily Ltd", "domain": "yapily.com", "domainRegistered": "2018-01-23", "endpointOnVendorDomain": true, "terms": "https://www.yapily.com/legal/website-terms-of-use", "privacy": "https://www.yapily.com/legal/privacy-policy", "statusPage": "https://status.yapily.com", "changelog": "", "securityTxt": "none", "checked": "2026-09-30", "notes": [ "Yapily Ltd, company 10842280, 66 Paul Street, London EC2A 4NA, is unregulated; Yapily Connect Ltd (company 11598433, FCA 827001) and Yapily Connect UAB (company 305602679, Bank of Lithuania LB002045) hold the licences.", "The customer contract is the Data Handling Agreement at yapily.com/legal/data-handling-agreement; the website terms are what's public.", "www.yapily.com/.well-known/security.txt returns 404.", "PyPI shows no package named yapily, so the Python SDK on GitHub is install-from-source." ], "score": 72 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/yapily.json", "live": { "slug": "yapily", "probe": { "target": "https://api.yapily.com", "method": "get", "lastAt": "2026-10-08T21:12:26.310483698Z", "lastOk": true, "lastStatus": 404, "lastMs": 144, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 155, "p95ms24h": 208, "samples24h": 271, "samples30d": 1955, "days": [ { "date": "2026-10-01", "probes": 109, "ok": 109 }, { "date": "2026-10-02", "probes": 248, "ok": 248 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 272, "ok": 272 }, { "date": "2026-10-06", "probes": 272, "ok": 272 }, { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 239, "ok": 239 } ] }, "vendorStatus": { "page": "https://status.yapily.com", "indicator": "minor", "summary": "Partial System Degradation", "checkedAt": "2026-10-08T21:06:31.487356449Z" }, "versions": [ { "registry": "npm", "name": "@yapily/yapily-api", "version": "8.0.0", "seenAt": "2026-10-08T16:35:26.747544649Z" } ], "githubStars": 14, "npmWeekly": 22, "securityTxt": { "url": "https://yapily.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-08T15:38:35.811465168Z" }, "llmsTxt": { "url": "https://docs.yapily.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-08T14:01:01.322319474Z" }, "domain": { "domain": "yapily.com", "registered": "2018-01-23", "source": "https://rdap.verisign.com/com/v1/domain/yapily.com", "checkedAt": "2026-10-04T13:06:12.962175252Z" }, "pages": [ { "url": "https://www.yapily.com/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-10-08T18:31:48.693270296Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "c34d3588f2f9" }, { "url": "https://www.yapily.com/legal/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-08T18:31:44.605800531Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "64008fcb9142" }, { "url": "https://www.yapily.com/legal/website-terms-of-use", "kind": "terms", "status": 200, "checkedAt": "2026-10-08T18:31:46.688285246Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "ef27f376f484" } ], "updatedAt": "2026-10-08T21:12:26.310483698Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "MX Technologies, Inc.", "b": "Yapily", "name": "Vendor" }, { "a": "https://api.mx.com", "b": "https://api.yapily.com", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Paid", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service. The SDKs and the OpenAPI files on GitHub are MIT", "b": "MIT (SDKs)", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-09-29", "b": "2025-06-30", "name": "Last release" }, { "a": "no document linked", "b": "2022-12-05", "name": "Terms last updated" }, { "a": "no document linked", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "", "b": "yes", "name": "Customer content may train models" }, { "a": "", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "9 stars, 2.6k npm/wk, 2k PyPI/wk", "b": "14 stars, 50 npm/wk", "name": "Popularity" }, { "a": "none", "b": "2.5/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "MX Platform API scores 62.5 (B) on agent readiness against Yapily's 57.6 (C), and leads in 4 of 7 scored categories. Yapily leads on transparency \u0026 trust.", "question": "Which is better for AI agents, MX Platform API or Yapily?" }, { "answer": "Both need an API key.", "question": "Do MX Platform API and Yapily need an API key?" }, { "answer": "Yes. MX Platform API has a hosted endpoint at https://api.mx.com and Yapily at https://api.yapily.com.", "question": "Can an agent call MX Platform API and Yapily without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 63 against 55", "Security \u0026 auth, 60 against 37", "Payments \u0026 pricing, 15 against 10" ], "also": null, "goodFor": "A US or Canadian bank, credit union or fintech with a signed MX contract that wants aggregation, verification and categorised transactions plus embeddable finance widgets.", "slug": "mx", "watchFor": "No public price, SLA or client agreement. Production keys are requested from MX in the Client Dashboard" }, { "aheadOn": [ "Transparency \u0026 trust, 71 against 63" ], "also": null, "goodFor": "UK and EEA data and payments from one API, for builders who want docs an agent can read in one fetch.", "slug": "yapily", "watchFor": "No public pricing; live access starts with a sales form" } ], "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-yapily.json", "title": "Akoya vs Yapily", "url": "https://www.anchorterminal.com/compare/akoya-vs-yapily" }, { "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-yapily.json", "title": "Belvo vs Yapily", "url": "https://www.anchorterminal.com/compare/belvo-vs-yapily" }, { "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-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/flinks-vs-yapily.json", "title": "Flinks vs Yapily", "url": "https://www.anchorterminal.com/compare/flinks-vs-yapily" }, { "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-yapily.json", "title": "GoCardless Bank Account Data vs Yapily", "url": "https://www.anchorterminal.com/compare/gocardless-bank-account-data-vs-yapily" }, { "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/plaid-vs-yapily.json", "title": "Plaid vs Yapily", "url": "https://www.anchorterminal.com/compare/plaid-vs-yapily" }, { "json": "https://www.anchorterminal.com/compare/salt-edge-vs-yapily.json", "title": "Salt Edge Account Information vs Yapily", "url": "https://www.anchorterminal.com/compare/salt-edge-vs-yapily" }, { "json": "https://www.anchorterminal.com/compare/teller-vs-yapily.json", "title": "Teller vs Yapily", "url": "https://www.anchorterminal.com/compare/teller-vs-yapily" }, { "json": "https://www.anchorterminal.com/compare/tink-vs-yapily.json", "title": "Tink vs Yapily", "url": "https://www.anchorterminal.com/compare/tink-vs-yapily" }, { "json": "https://www.anchorterminal.com/compare/truelayer-vs-yapily.json", "title": "TrueLayer vs Yapily", "url": "https://www.anchorterminal.com/compare/truelayer-vs-yapily" } ], "scores": [ { "by": 8, "edge": "mx", "key": "reliability", "mx": 63, "name": "Reliability", "weight": 16, "yapily": 55 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 3, "edge": "yapily", "key": "schema", "mx": 85, "name": "Schema \u0026 documentation", "weight": 13, "yapily": 88 }, { "by": 3, "edge": "yapily", "key": "ergonomics", "mx": 74, "name": "Agent ergonomics", "weight": 13, "yapily": 77 }, { "by": 23, "edge": "mx", "key": "security", "mx": 60, "name": "Security \u0026 auth", "weight": 14, "yapily": 37 }, { "by": 5, "edge": "mx", "key": "payments", "mx": 15, "name": "Payments \u0026 pricing", "weight": 10, "yapily": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 4, "edge": "mx", "key": "maintenance", "mx": 71, "name": "Maintenance \u0026 community", "weight": 7, "yapily": 67 }, { "by": 8, "edge": "yapily", "key": "transparency", "mx": 63, "name": "Transparency \u0026 trust", "weight": 7, "yapily": 71 } ], "summary": "MX Platform API scores 62.5 (B) on agent readiness against Yapily's 57.6 (C), and leads in 4 of 7 scored categories. Yapily leads on transparency \u0026 trust. Both do bank accounts.", "verdicts": { "mx": "Three public OpenAPI files, llms.txt, Markdown docs and a written version policy with 18 months of support and `Deprecation` and `Sunset` response headers. No price, client agreement or SLA is published, production keys need MX's approval, every calling IP address must be allowlisted, and the status page records three platform-wide error incidents since 10 July 2026.", "yapily": "llms.txt, llms-full.txt, a no-auth docs MCP server and an OpenAPI file. No public pricing; live access starts with a sales form." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/mx-vs-yapily", "json": "https://www.anchorterminal.com/compare/mx-vs-yapily.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/mx-vs-yapily.md", "slim": "https://www.anchorterminal.com/compare/mx-vs-yapily.min.md" }, "markdown": "MX Platform API scores 62.5 (B) on agent readiness against Yapily's 57.6 (C), and leads in 4 of 7 scored categories. Yapily leads on transparency \u0026 trust. Both do bank accounts.\n\n- MX Platform API: grade B, 62.5/100, rank #336 of 722. Markdown https://www.anchorterminal.com/tools/mx.md · JSON https://www.anchorterminal.com/api/v1/tools/mx.json\n- Yapily: grade C, 57.6/100, rank #469 of 722. Markdown https://www.anchorterminal.com/tools/yapily.md · JSON https://www.anchorterminal.com/api/v1/tools/yapily.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 55\n- Security \u0026 auth, 60 against 37\n- Payments \u0026 pricing, 15 against 10\n\nWatch for: No public price, SLA or client agreement. Production keys are requested from MX in the Client Dashboard\n\n### Yapily (C)\n\nGood for: UK and EEA data and payments from one API, for builders who want docs an agent can read in one fetch.\n\nAhead on:\n- Transparency \u0026 trust, 71 against 63\n\nWatch for: No public pricing; live access starts with a sales form\n\n\n## Score by category\n\n| Category | Weight | MX Platform API | Yapily | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 63 | 55 | MX Platform API +8 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 85 | 88 | Yapily +3 |\n| Agent ergonomics | 13% (16.2 this run) | 74 | 77 | Yapily +3 |\n| Security \u0026 auth | 14% (17.5 this run) | 60 | 37 | MX Platform API +23 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 15 | 10 | MX Platform API +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 71 | 67 | MX Platform API +4 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 63 | 71 | Yapily +8 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **62.5 · B** | **57.6 · C** | |\n\n## Facts side by side\n\n| Fact | MX Platform API | Yapily |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | MX Technologies, Inc. | Yapily |\n| Hosted endpoint | `https://api.mx.com` | `https://api.yapily.com` |\n| Transports | HTTP | HTTP, Streamable HTTP |\n| Auth | API key | API key |\n| Pricing | Paid | Paid |\n| x402 | no | no |\n| Licence | Proprietary service. The SDKs and the OpenAPI files on GitHub are MIT | MIT (SDKs) |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-09-29 | 2025-06-30 |\n| Terms last updated | no document linked | 2022-12-05 |\n| Privacy policy last updated | no document linked | no date given |\n| Customer content may train models | | yes |\n| Terms restrict automated access | | not found in the text |\n| Terms restrict benchmarking | | not found in the text |\n| Terms or service can change without notice | | not found in the text |\n| Arbitration or class-action waiver | | not found in the text |\n| Popularity | 9 stars, 2.6k npm/wk, 2k PyPI/wk | 14 stars, 50 npm/wk |\n| Agent reviews | none | 2.5/5 (2) |\n\n## Verdicts\n\n**MX Platform API.** Three public OpenAPI files, llms.txt, Markdown docs and a written version policy with 18 months of support and `Deprecation` and `Sunset` response headers. No price, client agreement or SLA is published, production keys need MX's approval, every calling IP address must be allowlisted, and the status page records three platform-wide error incidents since 10 July 2026.\n\n**Yapily.** llms.txt, llms-full.txt, a no-auth docs MCP server and an OpenAPI file. No public pricing; live access starts with a sales form.\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### Yapily\n\n1. Read llms-full.txt once and cache it; it's the whole documentation in one fetch\n2. Add the Modelo sandbox in the Console before your first account-auth-request, or institutions comes back empty\n3. Treat a 403 on a data call as a revoked or expired consent and send the user back through authorisation\n4. Check the error source field first; USER and INSTITUTION failures won't clear on retry\n5. In the UK, call extend-consent with lastConfirmedAt before the reconfirmBy date, or the consent lapses at 90 days\n\n## Questions\n\n### Which is better for AI agents, MX Platform API or Yapily?\n\nMX Platform API scores 62.5 (B) on agent readiness against Yapily's 57.6 (C), and leads in 4 of 7 scored categories. Yapily leads on transparency \u0026 trust.\n\n### Do MX Platform API and Yapily need an API key?\n\nBoth need an API key.\n\n### Can an agent call MX Platform API and Yapily without installing anything?\n\nYes. MX Platform API has a hosted endpoint at https://api.mx.com and Yapily at https://api.yapily.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/mx-vs-yapily.json, and with the fewest tokens: https://www.anchorterminal.com/compare/mx-vs-yapily.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"mx\", \"b\": \"yapily\"}`. From a terminal: `anchor compare mx yapily`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/mx.json and https://www.anchorterminal.com/api/v1/tools/yapily.json\n\n## Other comparisons with MX Platform API or Yapily\n\n- [Akoya vs MX Platform API](https://www.anchorterminal.com/compare/akoya-vs-mx.md)\n- [Akoya vs Yapily](https://www.anchorterminal.com/compare/akoya-vs-yapily.md)\n- [Belvo vs MX Platform API](https://www.anchorterminal.com/compare/belvo-vs-mx.md)\n- [Belvo vs Yapily](https://www.anchorterminal.com/compare/belvo-vs-yapily.md)\n- [Enable Banking vs MX Platform API](https://www.anchorterminal.com/compare/enable-banking-vs-mx.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- [Flinks vs Yapily](https://www.anchorterminal.com/compare/flinks-vs-yapily.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 Yapily](https://www.anchorterminal.com/compare/gocardless-bank-account-data-vs-yapily.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- [Plaid vs Yapily](https://www.anchorterminal.com/compare/plaid-vs-yapily.md)\n- [Salt Edge Account Information vs Yapily](https://www.anchorterminal.com/compare/salt-edge-vs-yapily.md)\n- [Teller vs Yapily](https://www.anchorterminal.com/compare/teller-vs-yapily.md)\n- [Tink vs Yapily](https://www.anchorterminal.com/compare/tink-vs-yapily.md)\n- [TrueLayer vs Yapily](https://www.anchorterminal.com/compare/truelayer-vs-yapily.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-08", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "MX Platform API vs Yapily", "url": "" } ], "description": "MX Platform API scores 62.5 (B) on agent readiness against Yapily's 57.6 (C), and leads in 4 of 7 scored categories. Yapily leads on transparency \u0026 trust. Both do bank accounts. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "MX Platform API B 62.5", "Yapily C 57.6", "scores" ], "h1": "MX Platform API vs Yapily", "image": "https://www.anchorterminal.com/assets/og/compare-mx-vs-yapily.png", "path": "/compare/mx-vs-yapily", "published": "2026-10-01", "section": "tools", "title": "MX Platform API vs Yapily for AI agents, B 62.5 vs C 57.6", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/mx-vs-yapily" }, "tokens": { "markdown": 2150, "slim": 630 }, "version": 1 }