MX Technologies
MX Technologies is a financial data connectivity platform that provides REST APIs for account aggregation, data cleansing, transaction categorization, and open banking connectivity across more than 16,000 financial institutions. The platform powers money experiences for over 2,000 banks, credit unions, and fintechs by turning raw, unstructured financial data into actionable intelligence. MX offers a suite of APIs including the Platform API for core aggregation and data services, the Atrium legacy API, SSO and authentication APIs, and a Data Access API built to FDX standards for permissioned open banking data sharing. Developers have access to OpenAPI specifications, SDKs in Node.js, Python, Java, Ruby, and Go, plus a hosted Connect Widget for rapid integration.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles MX Technologies the way a machine reads it — 44 machine-readable artifacts across 31 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — MX Technologies scores 59.3/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile MX Technologies
Each block below is one kind of artifact we hold for MX Technologies. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 31
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
MX Atrium API
The legacy MX financial data connectivity API supporting over 48,000 data connections to thousands of financial institutions. Provides secure access to user accounts and transac...
MX SSO API
A RESTful authentication API used to authenticate users on the MX Platform and generate widget URLs for Personal Finance Management and Financial Insights widgets. Supports both...
MX Data Access API
An open finance API built to FDX standards enabling permissioned data sharing with consumer consent management. Supports Account Owner Identity, statements, transaction history,...
MX Batch API
Enables processing of bulk operations and batch requests on the MX platform, supporting large-scale data operations for financial institutions and fintech partners.
MX Reporting API
Supports reporting functionality and analytics for financial institutions and fintech partners integrating with the MX platform.
MX Technologies accounts API
The accounts API from MX Technologies — 13 operation(s) for accounts.
MX Technologies ach return API
The ach return API from MX Technologies — 2 operation(s) for ach return.
MX Technologies budgets API
The budgets API from MX Technologies — 3 operation(s) for budgets.
MX Technologies categories API
The categories API from MX Technologies — 5 operation(s) for categories.
MX Technologies goals API
The goals API from MX Technologies — 3 operation(s) for goals.
MX Technologies insights API
The insights API from MX Technologies — 9 operation(s) for insights.
MX Technologies institutions API
The institutions API from MX Technologies — 5 operation(s) for institutions.
MX Technologies investment holdings API
The investment holdings API from MX Technologies — 5 operation(s) for investment holdings.
MX Technologies managed data API
The managed data API from MX Technologies — 7 operation(s) for managed data.
MX Technologies managed data [deprecated] API
The managed data [deprecated] API from MX Technologies — 7 operation(s) for managed data [deprecated].
MX Technologies members API
The members API from MX Technologies — 20 operation(s) for members.
MX Technologies merchants API
The merchants API from MX Technologies — 3 operation(s) for merchants.
MX Technologies microdeposits API
The microdeposits API from MX Technologies — 4 operation(s) for microdeposits.
MX Technologies monthly cash flow profile API
The monthly cash flow profile API from MX Technologies — 2 operation(s) for monthly cash flow profile.
MX Technologies notifications API
The notifications API from MX Technologies — 2 operation(s) for notifications.
MX Technologies processor token API
The processor token API from MX Technologies — 7 operation(s) for processor token.
MX Technologies rewards API
The rewards API from MX Technologies — 5 operation(s) for rewards.
MX Technologies spending plan API
The spending plan API from MX Technologies — 9 operation(s) for spending plan.
MX Technologies statements API
The statements API from MX Technologies — 5 operation(s) for statements.
MX Technologies taggings API
The taggings API from MX Technologies — 2 operation(s) for taggings.
MX Technologies tags API
The tags API from MX Technologies — 2 operation(s) for tags.
MX Technologies transaction rules API
The transaction rules API from MX Technologies — 2 operation(s) for transaction rules.
MX Technologies transactions API
The transactions API from MX Technologies — 19 operation(s) for transactions.
MX Technologies users API
The users API from MX Technologies — 3 operation(s) for users.
MX Technologies verifiable credentials API
The verifiable credentials API from MX Technologies — 3 operation(s) for verifiable credentials.
MX Technologies widgets API
The widgets API from MX Technologies — 4 operation(s) for widgets.
Scroll within the panel for all 31 ·
GraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
MX Technologies — Conceptual GraphQL Schema
MX Technologies does not publish a native GraphQL API. This schema is a conceptual
GRAPHQLPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Mx Technologies Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Mx Technologies Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Mx Technologies Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
MX Technologies API Rules
SPECTRALJSON Schema 1
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
MX Platform API Schemas
JSON SCHEMAExamples 1
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Security Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for MX Technologies — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/mx-technologies · machine-readable index on apis.io