Qwairy Pricing 2026: €79, 1,300 Credits, Then a Pause
Official Qwairy plans from the 2026-08-16 pricing page. Credits, API vs UI engines, and why Business is the real crawler-log SKU.
Qwairy publishes prices. That is the one adult thing on the page. Everything else is a credit formula that turns €79 into a very short month. Publishing the price is worth more than it sounds, because most of this category hides behind a "book a demo" wall, and a buyer who can read the card can do math before the call. The math is the part that catches people, and the credit formula is where the math stops being friendly.
Fetched from the Qwairy pricing page on 2026-08-16. Prices exclude tax. Annual billing is advertised as two months free (~17%). Full review: Qwairy. The date matters for a credit-based product, because the plan structure and the credit burn rate are the kind of thing a vendor can change between billing cycles, and a reader should treat the card as a snapshot, not a permanent fact.
Official plans
| Plan | Monthly | Annual effective | Prompts | Credits | Workspaces | Locked behind this tier |
|---|---|---|---|---|---|---|
| Free | €0 | €0 | n/a | 120 (homepage) / 100 (FAQ) | n/a | Nothing. It runs out. |
| Starter | €79 | €65/mo (€790/yr) | 100 | 1,300 | 1 | MCP, 10+ engine list |
| Growth | €199 | €165/mo (€1,990/yr) | 300 | 3,900 | 5 | REST API, Fact Check (beta) |
| Business | €449 | €374/mo (€4,490/yr) | 800 | 10,400 | 20 | Crawler analytics, Looker, alerts |
| Enterprise | Custom | Custom | Unlimited (page) | Custom | Unlimited | SSO, white-label, custom domain |
All paid plans list unlimited team members, 240+ countries, 45+ languages, CSV/PDF, shareable links. The unlimited team members line is the generous part of the card, and it is the part that makes Qwairy attractive to an agency that wants to seat everyone without a per-seat negotiation. The credits are the part that decides whether that team can actually work for the month.
How credits actually burn
From Qwairy's own pricing FAQ:
- 1 monitoring query = 1 credit per model
- 1 content brief = 50 credits
- At zero, new analyses pause. Config stays. You upgrade or buy more credits.
- Renewals add the plan allocation on top of leftover credits (rollover)
A 100-prompt Starter list run once across 10 engines is 1,000 credits. That is most of the month on day one. Daily cadence is not a Starter use case unless you cut engines hard. The credit math is simple once you see it written down, and it is brutal once you do: a monitoring query costs one credit per model, so a prompt watched across ten engines costs ten credits per check, and a daily check across ten engines costs three hundred credits per prompt per month. A hundred prompts at that cadence is thirty thousand credits, and Starter carries thirteen hundred.
Twenty-six content briefs (26 × 50) also empty the bucket with almost no monitoring left. A content brief is a one-time spend of fifty credits, and it is the kind of thing a team burns through early in the month without noticing, because a brief feels like a small action and costs like a large one. The rollover softens this a little, because leftover credits carry into the next cycle, but rollover does not help a plan that runs out in week one.
Engines vs the 10+ headline
Listed on every paid plan: ChatGPT (UI+API), Perplexity (UI+API), Copilot (UI), Gemini (UI+API), AI Overview (UI), Grok (UI+API), Claude (API), Mistral (API), AI Mode (UI), DeepSeek (API).
"All plans include access to every major AI engine" is the hero line. Three of those engines are API samples. If your buying reason was "what a logged-in ChatGPT/Claude user sees," Claude is the wrong box to tick. The UI versus API split is the part of the card that decides whether the engine count is real for your use case. A logged-in user sees one thing, and an API sample sees another, and the two can diverge enough to change the mention count. A buyer who assumed Claude was a live UI answer gets an API answer instead, and the answer to "are we mentioned" can be different.
What €79 does not include
- Crawler analytics (Business)
- Looker Studio connector (Business)
- Alerts and webhooks (Business, marked beta)
- REST API (Growth)
- Fact Check (Growth, beta)
- A free-forever seat after credits die
- A published G2 score we can cite
The list is the part of the review that saves a buyer from the demo. The demo shows Business features, the €79 card does not include them, and the gap between the two is where the surprise invoice lives. Crawler analytics in particular sit two tiers above Starter, and a buyer who came in for crawl visibility has to spend €449 to get it.
What the same money buys elsewhere
| Spend | Product |
|---|---|
| €0 | Promptwatch Explore (10 prompts, ChatGPT, stays free) |
| ~$95 | Promptwatch Essential: 10+ live UIs, 5 articles, no pause |
| €79 | Qwairy Starter: 1,300 credits |
| $89 | Temso Starter: 3 models, 10K bot visits |
| $29 | Otterly Lite: 15 prompts, 4 engines |
| $245 | Promptwatch Professional: 25M crawler logs |
| €449 | Qwairy Business: crawler analytics finally on |
The table is not a ranking, it is a price-equivalence read. The same euro buys different objects at different vendors, and the object that matters is the one that answers the brief. A credit bucket that pauses mid-month and a plan that does not pause are not the same product even at the same price.
Is Qwairy worth it and Promptwatch vs Qwairy walk through the buy. Alternatives: Qwairy alternatives.
FAQ
Can I buy extra credits without upgrading?
Qwairy's FAQ says you can upgrade or purchase additional credits when the balance hits zero. It does not publish a public extra-credit price on the page we fetched. The absence of a published top-up price is the part that makes budgeting hard, because the cost of running out is not knowable until you run out.
Is annual worth it?
Two months free if you already know you will stay. Do not annualize a product that pauses mid-month until you have watched a billing cycle. A product that pauses on credits is a product whose monthly cost depends on your usage, and annualizing it locks in a price before you know whether the credit allowance covers your real cadence.
Does Enterprise fix the clone problem?
It adds SSO and white-label. It does not turn API Claude into a live UI, and it does not publish a dollar price. Enterprise solves the procurement and branding questions, and it leaves the engine-format question exactly where it was, which is the question that drove the comparison in the first place.