MX
Based on public pricing signals, xpay observed that mx.com/pricing returns a 404 and the only commercial path is the Contact Us form. Documentation at docs.mx.com is public and well-structured, which means an agent can plan technical integration but cannot estimate cost or self-procure credentials. The shape is consistent with an enterprise data-platform sales motion.
404 — page not found
No tier numbers were visible on the public pricing page. An agent has no machine-readable path to evaluate or transact.
Snapshot rendered from xpay's extracted pricing signals. Tier count capped at 5 (anti-slider). For the live page, see source link above.How MX scores on the 7 agent-ready dimensions
Public pricing
0 / 15
Usage-based / metered
0 / 25
Self-serve checkout
0 / 15
Public API
8 / 15
Low / no minimum
0 / 10
Unauth automated payment
0 / 10
Bonus (machine-readable pricing)On top of /100 base
0 / 5
Total
8 / 100
Six-step check: can an agent actually buy from MX?
Discover price
https://www.mx.com/pricing/ — 404Select a plan
No tier table on mx.comPay per task
No per-unit price visible on mx.comAvoid a sales call
Only path is https://www.mx.com/contact-usAPI docs without auth
https://docs.mx.com accessible without authEstimate cost upfront
No per-unit price exposed on mx.comPros and cons for AI agents
Observational summary written by xpay from the signals captured on 2026-05-03. Not a review of the product — only of its current pricing posture for agent buyers.- API documentation is reachable without a login — discovery and integration can happen in one session.
- No tier numbers were visible on the public pricing page during the scoring fetch — agents cannot evaluate cost without a sales conversation.
- No per-unit price was advertised, so an agent has no way to estimate the cost of a single task.
- All advertised tiers route to a sales contact form; an agent cannot complete a purchase autonomously.
- No /.well-known/ai-pricing.json or equivalent machine-readable pricing manifest is published — agents must rely on HTML scraping.
- The pricing URL did not render numeric tier data on the scoring date — possibly a router or sales-led landing page.
How MX could lift its score
- Stand up a /pricing page with at least starter/scale/enterprise tiers and per-account or per-API-call rates.
- Add a card-based self-serve signup that issues production keys for the smallest tier without sales contact.
- Publish /.well-known/ai-pricing.json mirroring the rate card so agents can negotiate plans programmatically.
| pricing_visible | false |
| headline_phrasing | 404 — page not found |
| tier_count | 0 |
| lowest_paid_entry_usd | null |
| free_tier | false |
| free_tier_terms | null |
| per_unit_price | null |
| annual_required | null |
| self_serve_paid_tiers | 0 |
| sales_only_tiers | 0 |
| public_api_docs_url | https://docs.mx.com |
| api_docs_auth_walled | false |
| ai_pricing_json_present | false |
| agents_txt_present | false |
| anonymous_purchase_path | false |
MX
8
/ 100 (rubric v1.1)Financial Data APIs
404 — page not found
0
No
Sales-led
0 / 0
Public
No
Not published
2026-05-03