MX Technologies
for LuumenAI
Read MX accounts, members, and budgets, then make changes as approved steps
Connect MX Technologies and Luumen can read the state of your financial data platform directly from the terminal: users, members, accounts, account owners, institutions and their credential fields, categories, budgets, goals, and open MFA challenges. Changes — creating a member, fixing a transaction description, disabling a user — run as previewed steps you approve first. Luumen authenticates with basic auth.
The MX Technologies toolbox
36 tools: 27 read, 9 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadRetrieve Audience API CredentialsRetrieve Audience API credentials.
- ReadList Account Numbers by MemberList account numbers for a specific member.
- ReadList account ownersList account owners for a specific member.
- ReadList accountsList all accounts for a user.
- ReadList budgetsList all budgets for a specific MX user.
- ReadList categoriesList all categories for a user.
- ReadList challengesList MFA challenges for a member.
- ReadList favorite institutionsList the partner's favorite financial institutions, sorted by popularity.
- ReadList goalsList all financial goals for a specific MX user.
- ReadList institution credentialsList credential fields required by a given institution.
- ReadList institutionsList financial institutions supported by MX.
- ReadList member accountsList accounts for a specific member.
- ReadList membersList all members (financial institution connections) for a specific user.
- ReadList rewardsLists rewards and loyalty program data for a specific member.
- ReadList statements by memberRetrieve a paginated list of monthly account statements (PDF) for a specific member.
- ReadList taggingsList all taggings for a specific MX user.
- ReadList tagsList all custom tags associated with a specific MX user.
- ReadList transactionsRetrieve all financial transactions for an MX user across all their connected accounts and members.
- ReadList transactions by memberList transactions for a member.
- ReadList usersList all users in the MX Platform.
- ReadRead accountRetrieve details for a specific account.
- ReadRead categoryRetrieve a default category by GUID.
- ReadRead FDX accountRetrieve details for a specific account using the FDX 4.6 standard API.
- ReadRead institutionRetrieve details for a specific institution by code.
- ReadRead transactionRetrieve details for a specific transaction by its GUID.
- ReadRead transaction by accountRetrieve details for a specific transaction by account.
- ReadRead transaction ruleRetrieve details for a specific transaction rule by its GUID.
- WriteDisable MX User AccountDisables an MX user account, preventing background updates to accounts and transactions and restricting data access. Approval by default
- WriteCreate accountCreates a manual account for a specified user in MX Platform. Approval by default
- WriteCreate memberCreate a member to connect a user to a financial institution. Approval by default
- WriteCreate Partner AccountCreate a new user (partner account) in the MX Platform. Approval by default
- WriteFetch rewardsInitiate rewards aggregation for a specific member. Approval by default
- WriteGet configurable widget URLRetrieve a configurable widget URL for embedding MX widgets (Connect, Transactions, Pulse, etc.). Approval by default
- WriteUpdate transactionUpdate a specific transaction's description. Approval by default
- WriteUpdate transaction rulesUpdate an existing transaction rule. Approval by default
- WriteUpdate user taggingUpdate a tagging for an MX user. Approval by default
One prompt, start to finish
What a governed MX Technologies run looks like inside Luumen.
Questions
Authorize once with Basic auth. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — disable mx user account, create account, create member, create partner account, and more — is shown as a plan and requires approval by default, including the 1 action classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to MX Technologies — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
GitHubRepos, actions, and runbook code as context and as actions.
GitLabMerge requests and pipelines proposed, triggered, and rolled back.
BitbucketRead commits, diffs, and branches in Bitbucket, then open the fix as a held write.
Azure DevOpsAzure DevOps repos and pipelines as context — and as approved actions.Put MX Technologies to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.