Why 30% of Businesses Fail Agent Readiness Over Pricing Transparency
148 of 500 businesses we scanned have no visible pricing. Agents cannot negotiate "contact sales" — they need structured tiers, schema markup, and published numbers. D4 Pricing Transparency has the lowest weight in our scoring model (0.05), but the highest universal failure rate.
The 30% That Cannot Be Quoted
When AgentHermes scans a business for pricing transparency, we look for five signals: a /pricing page, visible prices in text (not images), schema.org Product or Offer markup, a machine-readable pricing endpoint, and a get_pricing skill in the agent-card.json. Businesses that hit at least three of the five score above 60 (Silver). Those that hit zero or one score under 20 (far below Bronze).
In our 500-business dataset, 148 businesses (30%) hit zero or one signal. Another 22% hit two. That means 52% of businesses are effectively opaque on pricing to AI agents — and this is the cause of roughly 40% of Bronze-tier scores.
The weighting paradox: D4 Pricing is weighted at only 0.05 because many businesses successfully sell without public pricing (luxury brands, enterprise SaaS, custom services). But in the agent economy, pricing silence becomes a hard filter — an agent comparing 5 options drops the 3 without quotable prices, regardless of how great those 3 options actually are.
The Five Pricing Failure Patterns
The 148 businesses with failing pricing all fall into five distinct patterns. Share of failures is noted for each.
"Contact us for pricing"
The most common pattern — and the most damaging. The business expects a human to fill out a form, wait for a sales email, and schedule a call before seeing a number. Agents bounce before the form loads.
"Custom quote based on needs"
A softer "contact us" that usually lives inside enterprise SaaS pricing pages. The middle two tiers have prices; the top tier says "Let us talk." Agents shortlist the competitors who quote the top tier openly.
Pricing behind auth
You have to sign up or log in to see prices. This is technically visible but functionally invisible to agents — they cannot complete the auth handshake on behalf of a user without credentials.
PDF price sheets
Downloadable pricing docs. Agents cannot parse PDFs reliably, cannot extract structured numbers, and cannot cite the source confidently in recommendations.
Sticker price but no structure
A /pricing page with three colored cards and prices printed as images or plain text. Slightly better than hidden pricing — agents can OCR the text — but scores poorly because there is no schema.org/Offer markup or API endpoint.
Why Agents Care About Structured Pricing (And Humans Do Not Notice)
A human visiting your pricing page can make sense of almost anything — a table of prices, three colored cards, a "talk to sales" CTA on the top tier. Humans bring context, patience, and tolerance for ambiguity. They can wait 48 hours for a quote email and still convert.
An AI agent has none of that. When a user asks "find me a CRM under $200/month that works with HubSpot", the agent evaluates candidates in seconds. It needs structured signals it can compare: number, currency, billing period, plan name, features included. If one of your three "competitors" has that structured data and you do not, you are eliminated before the user ever sees a shortlist.
This is not hypothetical — it is how Claude, ChatGPT, and Perplexity already handle product research queries today. The agent does not hate your business; it simply cannot include you in a structured comparison without structured data.
Who Is Doing It Right (And Who Is Doing It Wrong)
Agent-ready pricing — the leaders
Stripe
Score: 68Clear published rates (2.9% + 30¢ for standard cards, volume discounts above $80k/mo), schema.org/PriceSpecification markup, and a /api/v1/prices endpoint for programmatic access. Agents quote Stripe pricing with confidence.
Vercel
Score: 70Three published tiers (Hobby, Pro, Enterprise) with line-item breakdowns for bandwidth, builds, and function invocations. Structured JSON-LD Offer markup. The Enterprise tier is "Contact Sales" — not ideal — but the Pro tier has enough detail that agents do not need to ask.
Resend
Score: 75The only Gold-tier business in our 500-business dataset. Every tier has a price, a monthly email limit, a domain limit, and schema.org markup. An agent can quote Resend to a user in under 200 milliseconds without scraping.
Pricing opacity — the vertical laggards
Enterprise SaaS (avg)
Avg: 23The bulk of enterprise B2B software. "Contact us" on the top tier, and frequently on all tiers. The marketing team argues it enables price discrimination; the agent readiness data says it forfeits every agent-mediated deal.
Marketing agencies
Avg: 14Worst-performing vertical for pricing. 93% of agencies in our dataset have no public pricing. The average pricing dimension score for advertising is 9/100 — essentially zero.
Legal / Professional services
Avg: 18Cultural reflex is billable hours and custom engagements. A few forward-looking firms ship flat-fee menus, but the category average is in the teens. First firm to publish a structured rate card wins agent-mediated referrals.
What Agent-Ready Pricing Looks Like in Code
Here is the minimum JSON-LD Offer markup you can paste into the head of your /pricing page today. It takes 20 minutes to write, and it will move your D4 score by 25+ points on its own.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Acme CRM",
"description": "AI-powered CRM for modern sales teams.",
"brand": { "@type": "Brand", "name": "Acme" },
"offers": [
{
"@type": "Offer",
"name": "Starter",
"price": "49.00",
"priceCurrency": "USD",
"priceSpecification": {
"@type": "UnitPriceSpecification",
"price": "49.00",
"priceCurrency": "USD",
"unitCode": "MON",
"billingIncrement": 1
},
"eligibleQuantity": { "@type": "QuantitativeValue", "value": 5, "unitCode": "C62" },
"availability": "https://schema.org/InStock"
},
{
"@type": "Offer",
"name": "Growth",
"price": "149.00",
"priceCurrency": "USD",
"priceSpecification": { "@type": "UnitPriceSpecification", "price": "149.00", "priceCurrency": "USD", "unitCode": "MON" },
"eligibleQuantity": { "@type": "QuantitativeValue", "value": 25, "unitCode": "C62" }
},
{
"@type": "Offer",
"name": "Enterprise",
"priceSpecification": { "@type": "PriceSpecification", "priceCurrency": "USD", "minPrice": "1000", "maxPrice": "5000" }
}
]
}
</script>Note the Enterprise tier uses minPrice and maxPrice — a structured range — instead of "contact us." Agents can still shortlist you for users whose budget fits the range, instead of eliminating you outright.
Five Steps From Opaque to Agent-Ready
Every step here is independent. Even step 1 on its own moves your pricing dimension from "near-zero" to "Bronze floor." All five combined put you in Silver+ territory.
Publish at least three tiers with real numbers
Even "from $X/mo" beats "contact us." If your top tier is custom, show a range (from $5,000/mo). Agents can work with ranges — they cannot work with silence.
Add schema.org/Product + Offer markup
Wrap each tier in structured data. JSON-LD is easiest — paste a <script type="application/ld+json"> tag in the head. Google, Claude, and Perplexity all parse it.
Use semantic HTML on your /pricing page
<dl> for definition lists, <table> for rate comparisons, <meta itemprop="price"> where appropriate. Agents OCR images badly but parse semantic HTML flawlessly.
Ship a /api/pricing endpoint
A simple JSON endpoint returning your tiers as a structured document. Cacheable, versioned, agent-friendly. Even if no agent ever hits it, it signals you take programmatic access seriously.
Declare get_pricing in your agent-card.json
Add a "get_pricing" skill to your agent-card.json. This is a direct invitation for agents to quote you — the easiest possible integration point for agent-mediated sales.
Frequently Asked Questions
How many businesses fail agent readiness over pricing transparency?
148 of the 500 businesses we scanned (30%) have no visible pricing at all — no published tiers, no "from $X/mo" indicators, no price-adjacent structured data. An additional 22% have partial pricing that requires authentication or PDF download. Combined, 52% of businesses are effectively opaque to AI agents on pricing.
Why is the D4 Pricing dimension weighted so low (0.05) if it matters so much?
Pricing is weighted 0.05 in the standard AgentHermes scoring model because it is rarely a hard blocker — an agent can still discover, understand, and sometimes even buy from a business without structured pricing, as long as other dimensions are strong. But the dimension has the highest failure rate of any scored area (30% near-zero). Businesses in verticals where pricing is culturally hidden (enterprise SaaS, agencies, legal, healthcare) should expect pricing to be their lowest dimension score by a wide margin.
What does good agent-readable pricing look like technically?
Three things: (1) a /pricing page using semantic HTML with prices as text not images, (2) JSON-LD Offer / PriceSpecification markup describing each tier, and (3) a machine-readable endpoint — either a GET /api/pricing JSON route or a get_pricing skill declared in your agent-card.json. Stripe, Vercel, and Resend all do this. Their pricing dimension scores are in the 70-85 range versus the dataset average of 32.
We sell enterprise software where pricing really is custom. What should we do?
Ship a starting-point price and a range for volume. "From $2,000/mo, custom pricing available above $50k ACV" beats "Contact sales" every time. Include the range in schema.org/Offer as priceRange. If you absolutely cannot publish numbers, at least publish the structure: a get_pricing skill that returns your deal size brackets (SMB, mid-market, enterprise) and next steps. Agents can then route users correctly instead of assuming you are out of scope.
Will publishing pricing hurt my sales?
The empirical data from SaaS comparison sites (ProfitWell, OpenView, Price Intelligently) consistently shows the opposite — companies that publish pricing reduce sales cycle length by 30-50% and capture more self-serve conversion. The fear of "price anchoring" or "competitor visibility" is almost always outweighed by qualified-lead gains. In the agent economy, the gap widens: agents route toward transparent pricing because they cannot complete a quote without it.
See exactly where your pricing fails
Run a free Agent Readiness Scan. We grade your D4 Pricing dimension against every signal — schema markup, structured tiers, machine-readable endpoint, agent-card skill — and show you the 3-5 specific fixes that move you fastest.