AAO toolAI agent pricing checker: can an agent read your prices?
When someone asks an AI to compare tools or book a plan, the agent reads your pricing page. Paste its source to see the plans, prices and billing periods an agent can extract, whether prices exist only in JavaScript or images, and whether your structured data tells the same story. Nothing is uploaded.
Free · no signup · updated 13 October 2026
Paste your pricing page's source
Open the pricing page, press Ctrl+U (or ⌥⌘U on a Mac) to view the source, select all and paste. That raw HTML is what most AI fetchers read. Nothing is uploaded.
What an agent can extract
| Plan | Price | Billing | In structured data |
|---|
Prices in your structured data
| Item | Price | Currency | Shown on the page |
|---|
Fix first
How do I make my pricing readable to AI agents?
Put every plan name, price, currency and billing period in plain text in the page's HTML, not only in images or prices rendered by JavaScript. Give plans with "contact sales" at least a starting price, and add Offer structured data whose price and priceCurrency match what the page shows.
The method, in the open.
Paste the page source (Ctrl+U), which is what fetchers that don't run JavaScript read. The checker parses it in an inert document in your browser, then:
- Finds prices in visible text: amounts next to a currency symbol or code ($, €, £, ₹, USD, INR and others), ignoring scripts and styles.
- Detects plans: headings whose surrounding block contains a price, "free" or a sales call to action, and the billing period stated nearby.
- Reads structured data: Offer prices from JSON-LD and microdata, and checks each against the visible prices.
- Flags prices that exist only inside JavaScript, pricing images, plans with no price, missing billing periods and missing currencies.
What the numbers look like.
Using the sample page. Four plans are detected. Free and Starter pass. Pro shows $49 on the page but $59 in the structured data, so an agent could quote either. Enterprise shows only "Contact sales", and add-on prices sit in an image no agent can read. Fixing the Pro markup, adding a starting price for Enterprise and moving add-on prices into text takes the score from 67 to 100.
What this is based on
- In a vendor study, a task whose numbers appeared only inside an image without a text alternative failed in all 60 agent attempts. AudioEye (accessibility vendor)
- Product structured data describes offers with price and priceCurrency, and should match what users see on the page. Google Search Central
- Lighthouse's Agentic Browsing category checks whether agents can use a page through its accessibility tree. Chrome for Developers
What it does not tell you
- Plan detection is heuristic: it relies on headings near prices. Unusual layouts may need a manual read of the "prices found" list.
- It reads the source you paste. If prices are rendered by JavaScript, the source shows none; that is the point, because many fetchers don't run scripts. Browser agents that do run JavaScript may still see them.
- Monthly/annual toggles are read as written in the HTML; whichever prices are present in the source are listed.
- It doesn't judge whether your prices are competitive, only whether they are readable and consistent.
Questions people ask.
Why does it matter if AI agents can read my pricing?
Buyers ask assistants to compare options and shortlist by price. If an agent can't find your price, it skips you or quotes an outdated number from a third-party site.
Should I hide enterprise pricing?
Give at least a starting price or range. "Contact sales" alone means an agent has nothing to compare.
Do I need structured data for pricing?
It helps make facts unambiguous, but it must match the visible page. Conflicting markup is worse than none.
Why paste the page source instead of a URL?
The source is exactly what fetchers that don't run JavaScript receive, and checking it in your browser means no server fetch and nothing uploaded.
Is the HTML uploaded?
No. It is parsed in your browser and never sent to our servers. Its scripts are not executed.
Keep checking.
AI agent form checker
Paste a form's HTML and see whether an AI agent can understand and fill it: field names, autocomplete, buttons, honeypots and CAPTCHAs. Runs in your browser.
AI bot & agent log analyzer
Upload a server log and see which AI crawlers, fetchers and agents read your site, which pages they want, and where your firewall turns them away. Runs in your browser.
AI crawler checker
Is GPTBot, OAI-SearchBot, ClaudeBot or PerplexityBot blocked on your site? Checks robots.txt and tests your CDN, bot by bot.
Make your prices impossible to misread.
We fix pricing pages, structured data and feeds so AI agents compare you on accurate numbers and finish the purchase with you.