> ## Documentation Index > Fetch the complete documentation index at: https://docs.mx.com/llms.txt > Use this file to discover all available pages before exploring further. # MX Data Architecture The MX platform is built on seven core resources: accessors, clients, users, members, institutions, accounts, and transactions. ## Diagram Here's how these resources relate to each other. Data Architecture ## Resources The following table describes each resource, its relationships, and who creates it. | Resource | Description | Relationship | Created By | | ------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | ------------------------------------------ | | Accessors | Top-level hierarchy representing MX clients. Each has an API key for authentication and manages IP whitelisting. | Can have multiple clients | MX only | | Clients | Individual MX clients within an accessor. Each has a `client_id` for authentication and serves as the customization point for product branding. **Example:** A banking provider serving 100 institutions has one accessor with 100 clients—one per institution. | Belongs to one accessor; can have multiple users | MX only | | [Users](/api-reference/platform-api/reference/users) | End users whose financial data is aggregated and analyzed. | Belongs to one client; can have multiple members | MX clients | | [Members](/api-reference/platform-api/reference/members) | Connection between a user and an institution. Stores credentials, handles MFA, and performs aggregation. Can have multiple accounts. Duplicates not allowed. **Example:** A user with checking and savings at Wells Fargo has one member with two accounts. | Belongs to one user; can have multiple accounts | MX clients or end users | | [Institutions](/api-reference/platform-api/reference/institutions) | Financial institutions like Chase or Wells Fargo. A real-world institution may have multiple objects if divisions use separate systems. A client may set a default institution representing the partner organization itself. **Example:** Wells Fargo may have separate objects for mortgages, banking, and credit cards. | Referenced by members | MX only | | [Accounts](/api-reference/platform-api/reference/accounts) | Individual financial accounts (checking, savings, mortgage, 401(k), and [more](../../../api-reference/platform-api/reference/accounts#account-types)). | Belongs to one member; can have multiple transactions | MX products, aggregation, or MDX On Demand | | [Transactions](/api-reference/platform-api/reference/transactions) | Money movement into or out of an account (purchases, deposits, transfers, withdrawals, and so on). | Belongs to one account | MX products, aggregation, or MDX On Demand |