MySQL
MySQL scores 6/100 on xpay's Agent-Ready Index v2: partial pricing visibility.
MySQL pricing
Sales-led pricing
MySQL displays a feature comparison table across three commercial editions (Standard, Enterprise, Cluster CGE) but provides no public pricing. The page explicitly states 'For pricing for 5+ Socket Servers, contact the MySQL Sales Team' and directs all licensing inquiries to sales. Community Server is free/open-source. Classified as sales_only due to complete absence of public pricing and mandatory sales contact requirement.
How MySQL scores on the agent-ready dimensions
Public pricing visibility
2 / 15
Self-serve checkout
0 / 15
Public API + docs
0 / 20
Usage-based / metered pricing
0 / 20
Free entry path
4 / 7
No sales call required
0 / 7
Card / wallet / x402 payment
0 / 6
Machine-readable bonus (MCP / OpenAPI)
0 / 10
Total
6 / 100
Six-step check: can an agent actually buy from MySQL?
Discover price
Select a plan
Pay per task
Avoid a sales call
API docs without auth
Estimate cost upfront
Pros and cons for AI agents
Observational summary written by xpay from the signals captured on 2026-05-06. Not a review of the product — only of its current pricing posture for agent buyers.- Pricing is publicly visible on an indexable page — agents can read tiers without scraping past auth.
- Every advertised tier is self-serve; no tier requires scheduling a call.
- No per-unit price was advertised, so an agent has no way to estimate the cost of a single task.
- API documentation is gated or absent; an agent cannot inspect the integration surface without authentication.
- No /.well-known/ai-pricing.json or equivalent machine-readable pricing manifest is published — agents must rely on HTML scraping.
How MySQL could lift its score
Add a per-unit price (e.g. $X / 1K calls) to the pricing page so an agent can compute its own cost before committing.
| pricing_visible | true |
| headline_phrasing | Compare Editions — Commercial customers have the flexibility of choosing from multiple editions to meet specific business and technical requirements: |
| tier_count | 1 |
| lowest_paid_entry_usd | null |
| free_tier | false |
| free_tier_terms | null |
| per_unit_price | null |
| annual_required | false |
| self_serve_paid_tiers | 0 |
| sales_only_tiers | 1 |
| public_api_docs_url | null |
| api_docs_auth_walled | null |
| ai_pricing_json_present | false |
| agents_txt_present | false |
| anonymous_purchase_path | false |
| per_unit_classification | null |
| usage_headline_present | false |
| custom_tier_present | true |
| agent_friendly | {"ai_pricing_json":false,"agents_txt":false,"llms_txt":false,"sitemap_xml":false,"mcp_server_card":false,"agent_skills_index":false,"x402_supported":false} |
View raw extracted page text →
Claim this scorecard & lift your score.
Get the breakdown of every signal we measured, the one-line fix, and how your peers in Database Management stack up.
Compare the agent-ready picks in Database Management.
If you're building or running an AI agent that needs to buy from this category, see who's scoring highest right now.
See agent-ready picksMySQL
6
/ 100 (rubric v2.0)Database Management
Not advertised
1
No
Sales-led
0 / 1
Auth-walled
No
Not published
2026-05-08
Sales-led pricing
Discovery files and protocols
Side-channel signals — informational, not part of the score. Each protocol is independent; adoption signals the publisher is thinking about agent buyers.ai-pricing.json
agents.txt
llms.txt
sitemap.xml
MCP Server Card
Agent Skills
x402 / MPP
Compare MySQL with peers
Highest-scoring companies in the same category that an AI agent might evaluate as an alternative.Pinecone
85
SingleStore
85
MongoDB
81
Neon
78
restdb.io
78
CrateDB
74
FaunaDB
73
QuintaDB
71
Explore the Agent-Ready SaaS Index
25,480+ SaaS scored on agent-buyability — browse by readiness band, category, or jump straight to a pay-per-run tool on xpay.tools.