Typesense Cloud
Typesense Cloud uses a configurator-style pricing page where the visitor selects RAM, vCPU, HA, regions and version; the page returns an hourly rate with no contact-sales gate. xpay verified that the configurator produces real prices anonymously, that docs are public, and that signup is self-serve, though the resource-based model lacks a true PAYG-per-search rate and there is no machine-readable manifest.
Transparent Pricing to Meet your Precise Needs — dedicated cluster, no limits on records or operations
Hourly resource-based: RAM × vCPU × HA × SDN selection
Self-serve
How Typesense Cloud scores on the 7 agent-ready dimensions
Public pricing
10 / 15
Usage-based / metered
8 / 25
Self-serve checkout
15 / 15
Public API
15 / 15
Low / no minimum
0 / 10
Unauth automated payment
3 / 10
Bonus (machine-readable pricing)On top of /100 base
0 / 5
Total
51 / 100
Six-step check: can an agent actually buy from Typesense Cloud?
Discover price
https://cloud.typesense.org/pricing — interactive configurator outputs hourly + monthly priceSelect a plan
Single product line; configurator dimensions substitute for tiersPay per task
Resource-hour billing rather than per-search; storage/RAM scale with usageAvoid a sales call
Cluster provisioning is self-serve; only premium support plans require contactAPI docs without auth
https://typesense.org/docs/ — publicEstimate cost upfront
Configurator returns exact hourly cost for the selected configurationPros 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.- Every advertised tier is self-serve; no tier requires scheduling a call.
- API documentation is reachable without a login — discovery and integration can happen in one session.
- No per-unit price was advertised, so an agent has no way to estimate the cost of a single task.
- PPU requires account creation and an issued API key; a fully unauthenticated agent purchase is not yet supported.
- No /.well-known/ai-pricing.json or equivalent machine-readable pricing manifest is published — agents must rely on HTML scraping.
- A unit price is published but consumption per task is not declared upfront — cost predictability is partial.
How Typesense Cloud could lift its score
Typesense already lands in Verified. Three missing points: (1) introduce a per-search-request pricing option for low-volume agent workloads; (2) publish /.well-known/ai-pricing.json mirroring the configurator's rate card; (3) add an anonymous PPU endpoint so a no-account agent can issue a single query.
| pricing_visible | true |
| headline_phrasing | Transparent Pricing to Meet your Precise Needs — dedicated cluster, no limits on records or operations |
| tier_count | 0 |
| lowest_paid_entry_usd | null |
| free_tier | false |
| free_tier_terms | Self-host open source is free; Cloud has no free tier but smallest cluster ~$0.06/hr (~$43/mo) per configurator |
| per_unit_price | Hourly resource-based: RAM × vCPU × HA × SDN selection |
| annual_required | false |
| self_serve_paid_tiers | 1 |
| sales_only_tiers | 0 |
| public_api_docs_url | https://typesense.org/docs/ |
| api_docs_auth_walled | false |
| ai_pricing_json_present | false |
| agents_txt_present | false |
| anonymous_purchase_path | false |
Typesense Cloud
51
/ 100 (rubric v1.1)Search APIs
Transparent Pricing to Meet your Precise Needs — dedicated cluster, no limits on records or operations
0
No
Self-host open source is free; Cloud has no free tier but smallest cluster ~$0.06/hr (~$43/mo) per configurator
Sales-led
Hourly resource-based: RAM × vCPU × HA × SDN selection
1 / 0
Public
No
Not published
2026-05-03