PlayHT
xpay attempted to score PlayHT on 2026-05-03 and found that DNS resolution failed for play.ht, www.play.ht, and play.ai during the live pull, so no pricing content could be observed. The opportunity is to publish a stable, indexable pricing URL (and equally important, ensure DNS reachability for crawlers) so agents can discover and transact against PlayHT's TTS rates. This score reflects observability at scrape time and should be revisited if the pricing surface returns.
(domain unreachable from scraper — DNS resolution failed for play.ht, www.play.ht, and play.ai during the 2026-05-03 pull)
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 PlayHT 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 PlayHT?
Discover price
https://play.ht/pricing/ — DNS resolution failed during 2026-05-03 FirecrawlSelect a plan
https://play.ht/pricing/ — page unreachablePay per task
https://play.ht/pricing/ — page unreachableAvoid a sales call
https://play.ht/pricing/ — page unreachableAPI docs without auth
https://docs.play.ht — same root domain unresolvable from scraperEstimate cost upfront
https://play.ht/pricing/ — no content fetchedPros 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 PlayHT could lift its score
- Restore stable DNS / public reachability for the pricing URL so search engines and agent crawlers can index it.
- Publish a server-rendered per-character or per-minute TTS rate card with a free tier and Stripe self-serve checkout.
- Add /.well-known/ai-pricing.json so autonomous agents can discover the rate without HTML parsing.
| pricing_visible | false |
| headline_phrasing | (domain unreachable from scraper — DNS resolution failed for play.ht, www.play.ht, and play.ai during the 2026-05-03 pull) |
| tier_count | 0 |
| 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 | 0 |
| public_api_docs_url | https://docs.play.ht |
| api_docs_auth_walled | false |
| ai_pricing_json_present | false |
| agents_txt_present | false |
| anonymous_purchase_path | false |
PlayHT
8
/ 100 (rubric v1.1)Speech & Transcription
(domain unreachable from scraper — DNS resolution failed for play.ht, www.play.ht, and play.ai during the 2026-05-03 pull)
0
No
Sales-led
0 / 0
Public
No
Not published
2026-05-03