Softwr

APIs · head to head

MX Technologies vs Poolside

MX Technologies logo

MX Technologies

APIs

US financial data aggregation with heavy transaction cleansing and enrichment

From
On request
Free plan
No
Poolside logo

Poolside

AI

Open-weight foundation models built for agentic software engineering

From
$0.06/month
Free plan
No

The short version

  • Poolside starts at $0.06/mo; MX Technologies prices on request.
  • Only MX Technologies lists account aggregation; only Poolside lists laguna S 2.1.
  • Where Poolside falls short: no self-serve public application; access is largely through enterprise sales or third-party model gateways.
  • Prices and features on this page were last checked on 31 August 2026.

Where they differ

Only the attributes on which MX Technologies and Poolside actually diverge.

Attributes where MX Technologies and Poolside differ
AttributeMX TechnologiesPoolside
Starting priceOn request$0.06/month
Pricing modelQuoteUsage-based
PlatformsAPI, WebWeb, API, macOS, Windows, Linux
CategoryAPIsAI

Identical on both: free tier (No).

Not yet recorded: founded for MX Technologies.

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in MX Technologies

  • Account aggregation
  • Transaction cleansing
  • Categorisation
  • Merchant resolution
  • Account verification
  • Balance and funds checks
  • Data enhancement APIs
  • Consent and connection management

Only in Poolside

  • Laguna S 2.1
  • Laguna XS 2.1
  • Desktop and CLI tools
  • Open-weight models
  • Third-party gateway access

What people use each for

The jobs each tool is most often brought in to do.

MX Technologies

  • A credit union building a personal finance view in its own app that needs its own transaction descriptions made readablenot Poolside
  • A lender using cash flow underwriting that needs categorised income and expense data rather than raw transaction stringsnot Poolside
  • A bank wanting account verification and balance checks before initiating ACH debits to reduce returnsnot Poolside
  • A fintech that already aggregates data elsewhere and licenses only the enrichment layer to clean what it hasnot Poolside

Poolside

  • Enterprises deploying AI coding assistance across large developer organizationsnot MX Technologies
  • Government and defense agencies needing on-premise or sovereign coding modelsnot MX Technologies
  • Teams building custom coding agents on open-weight foundation modelsnot MX Technologies
  • Organizations wanting on-device lightweight coding modelsnot MX Technologies

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

MX Technologies

  • Coverage is United States focused, so any product with European or other international users runs a second aggregator and reconciles two data models, which removes most of the single vendor argument
  • Nothing is published on price and contracts are enterprise shaped, so a small fintech cannot estimate cost or start building without a sales process, unlike self-serve competitors
  • Data enhancement is the differentiator and is licensed separately from aggregation, so the quoted aggregation price is not the price of the product people actually buy it for
  • Categorisation and merchant resolution are statistical and get business to business and unusual transactions wrong more often than consumer retail, so lending decisions built on categorised data need their own review layer
  • As the United States moves to regulated API access, connection quality depends on what each institution exposes, and the long tail of small banks and credit unions remains the weakest part of any aggregator including this one

Poolside

  • No self-serve public application; access is largely through enterprise sales or third-party model gateways
  • Pricing for the flagship enterprise and government offering is not public and requires a sales conversation
  • Targets organizations with large (5,000+) developer headcounts, making it a poor fit for individuals or small teams
  • Documentation and product surface area are thin compared to consumer-facing coding assistants

Pricing, plan by plan

MX Technologies

On request
  • MX PlatformOn request
    • Priced by connected users, API calls and modules
    • Data enhancement licensed separately from aggregation
    • Enterprise contracts aimed at financial institutions

Poolside

$0.06/month
  • Laguna XS 2.1On request
    • $0.06 per 1M input tokens
    • $0.12 per 1M output tokens
    • Available via OpenRouter and Vercel AI Gateway
  • Laguna S 2.1On request
    • $0.10 per 1M input tokens
    • $0.20 per 1M output tokens
    • 1M token context window
  • Enterprise / GovernmentOn request
    • Custom contracts for large engineering organizations
    • Sales-quoted pricing
    • On-premise or dedicated deployment options

Which should you pick?

Choose MX Technologies if

  • You need account aggregation.
  • You work on API, Web.
  • You also want transaction cleansing.

Choose Poolside if

  • You need laguna s 2.1.
  • You work on Web, API, macOS, Windows, Linux.
  • You also want laguna xs 2.1.

Questions people ask

Is MX Technologies or Poolside better?
Neither clearly leads. MX Technologies starts at On request and Poolside at $0.06/month, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, MX Technologies or Poolside?
MX Technologies starts at On request and Poolside at $0.06/month.
Does MX Technologies or Poolside run on more platforms?
MX Technologies runs on API, Web. Poolside runs on Web, API, macOS, Windows, Linux.
What is MX Technologies best used for?
MX Technologies is most often used for a credit union building a personal finance view in its own app that needs its own transaction descriptions made readable, a lender using cash flow underwriting that needs categorised income and expense data rather than raw transaction strings, a bank wanting account verification and balance checks before initiating ach debits to reduce returns, a fintech that already aggregates data elsewhere and licenses only the enrichment layer to clean what it has. Of those, a credit union building a personal finance view in its own app that needs its own transaction descriptions made readable and a lender using cash flow underwriting that needs categorised income and expense data rather than raw transaction strings are not what Poolside is typically brought in for.
What can MX Technologies do that Poolside cannot?
MX Technologies covers Account aggregation, Transaction cleansing, Categorisation, Merchant resolution. Poolside covers Laguna S 2.1, Laguna XS 2.1, Desktop and CLI tools, Open-weight models.

Answered from the vendors’ own pages

MX Technologies: What does MX do that Plaid does not?

It sells transaction cleansing, categorisation and merchant resolution as a first class product, including on data you already hold, which is why financial institutions rather than startups are its core customers.

Poolside: How is Poolside's Laguna model usage priced?

Laguna XS 2.1 is priced at $0.06 per 1M input tokens and $0.12 per 1M output tokens; Laguna S 2.1 is $0.10 per 1M input tokens and $0.20 per 1M output tokens.

Source
MX Technologies: Does it cover Europe?

No. MX is United States focused. European coverage requires a different provider such as Tink.

Poolside: Where can I access Poolside's models?

Laguna models are available through third-party gateways OpenRouter and Vercel AI Gateway, as well as via Poolside's own desktop and CLI tools.

Source
MX Technologies: Is pricing published?

No. Contracts are quoted by connected users, call volume and modules, with enhancement licensed separately from aggregation.

Poolside: Does Poolside offer enterprise or government pricing?

Yes, Poolside offers custom, sales-quoted contracts for large enterprises and government/defense customers, including on-premise or dedicated deployment options.

Source
MX Technologies: Does it use screen scraping?

It uses direct bank APIs where institutions expose them and credential based connections elsewhere. The credential path is being deprecated across the industry, and coverage quality now tracks which banks have real APIs.

Poolside: How do I get started building with Poolside's models?

Poolside's documentation provides a quickstart guide for installing the `pool` CLI and running an agent task, alongside API documentation for custom integrations.

Source
Share

Related pages

Other head to heads