VTChat
Browser chat with Plain and VT on one page.
Without account: No account: try chat (Free tier — queue and ads).
After sign-in: With account: your tier limits; Pro/Max without ads.
Settings: mode and model on the chat page.
Ready-made assistants for medicine, law, marketing, and more. Try free in the browser — subscribe when you need full access. No coding required.
Browse the marketplace · quick chat · step-by-step builder
Structured plans, verification against the diff, and a learning loop over MCP or HTTP. One ReasonService for every project in your editor.
VT plans and verifies — you decide and write the code.
reason_plan → code → reason_verify → feedback — same taskId per batch
Honest split: local developer setup vs public production. No promised launch date.
Browser chat and marketplace live on the product host. Billing, API keys, and this landing page live on the account host. Cursor MCP is not the site chat.
| Host | Open for |
|---|---|
| Product · ReasonService | VTChat, marketplace, assistants, PromptHub, help |
| Account · AccountServer | Sign-in, pricing, cabinet, MCP onboarding |
Fast chat in the browser ≠ reason_plan in Cursor. Developers: use MCP tools with the same taskId per batch.
Each product has its own page and settings inside it. Sign in for API key, billing, and subscriptions — not required to try VTChat or browse prompts.
Browser chat with Plain and VT on one page.
Without account: No account: try chat (Free tier — queue and ads).
After sign-in: With account: your tier limits; Pro/Max without ads.
Settings: mode and model on the chat page.
Domain playbooks — medicine, law, marketing.
Without account: No account: browse marketplace and try demos.
After sign-in: With account: subscriptions, saved builder, your assistants.
Settings: inside each assistant; subscriptions in cabinet.
Describe a task — get a ready prompt. Public catalog.
Without account: No account: generator and catalog.
After sign-in: With account: save drafts and publish (when enabled).
Settings: language and filters on PromptHub pages.
reason_plan → code → reason_verify in Cursor.
Without account: No account: docs and one-click local install.
After sign-in: With account: API key for hosted MCP and HTTP /v1/reason.
Settings: API key, BYOK, model — in Account cabinet.
Explore most products without registering. An account ties billing, API access, and assistant subscriptions.
| Area | Without account | After sign-in |
|---|---|---|
| VTChat | Try in browser | Tier limits; higher tiers — no ads or queue |
| Marketplace & assistants | Browse catalog and demos | Subscribe, manage assistants, builder progress |
| PromptHub | Generate and copy prompts | Save drafts; publish when enabled |
| MCP & HTTP API | Local install + documentation | API key, hosted MCP, usage quota |
| Account cabinet | — | Billing, tier, keys, assistant subscriptions |
The higher the tier, the higher the limits and the deeper the reasoning.
With a wait in the queue and built-in ads · basic reasoning depth
≈ $20 / 1500 ₽ per month · higher limits, deeper reasoning, no ads or waiting
Maximum limits and the deepest verification with a judge ensemble
The same reasoning core powers domain assistants, a marketplace, and privacy-first data handling.
Build an assistant with its own scenario set: it runs analysis by your rules and keeps records.
Publish and connect ready-made assistants — by subscription or one-off.
We store the minimum: email, password hash, and request metadata. Export and deletion on request.
Describe the task in plain words — get a well-built prompt. Ready-made prompts are searchable by category and copyable.
The product does not jump to an answer. It follows a short loop you can read.
First it turns your request into a plan: what done looks like, and what could go wrong.
Only then is the work written — to that plan, not to a guess.
Then the result is checked against the plan. Gaps go back to fix.
If something is unclear, it asks you. It does not invent your choice.
Limits are written in plain language: what works today and what is still in progress.
The same loop repeats: plan → work → check, so the next pass is not a lottery.
Same request, different result. A comparison with no reference to any specific product.
| What happens | Assistant without structured reasoning | With our structured reasoning |
|---|---|---|
| Understanding the task | Takes the request literally and codes right away | Clarifies the goal and expands it into a plan with a DoD |
| Edge cases | Often forgotten — surface in production | Listed up front: errors, empty data, limits |
| Verification | None — “looks right” | Diff is checked against the plan; gaps go back to fix |
| Tests | Optional, if it remembers | A test matrix is proposed with the plan |
| Reproducibility | Different every time | One loop: plan → code → verify |
| Improving over time | Doesn’t learn from your tasks | Builds experience and strengthens weak categories from feedback |
| Honest limits | Hidden caps and surprise gaps | Published LIMITATIONS — what works today and what does not |
Read honest product limits (LIMITATIONS) → · See static before/after examples →
Pre-recorded pairs: flat model answer vs the same request with plan→verify. No live generation on this page.
We compare product versions on a hidden task set. Numbers appear here only after an honest run — not marketing guesses.
Figures will appear after we finish an honest measurement on a release tag.
Hidden product quality check — not GSM8K or a public model leaderboard.
Verifiable reasoning for AI agents in your editor: structured plans, verification, and learning loop over MCP or HTTP.
Do not use mcp-sampling in Cursor — use hosted MCP or local with your OpenAI API key in Cursor.
npx -y verithink-mcp
ReasonService on 127.0.0.1:8787 — one instance for all Cursor projects.
Multi-step plans with coverage checks, risks, and edge cases — before the first line of code.
Connect once — the agent calls planning and verification right in its coding loop.
Service mode with pay-as-you-go, your own key, or a local model — switch it in the cabinet.
One worked example of how a vague request becomes a verified result.
“Add file upload to the profile.”
The system expands the task into steps with a DoD: type and size limits, content checks, link privacy, edge cases, and tests.
The agent writes code to the plan — covering every point, not just the happy path.
The finished diff is checked against the plan. A missing size limit? Verification catches it and sends it back to fix.
Request: "add file upload" Plan (DoD): 1. Validation: allowed types, 10 MB limit 2. Security: content check, private links 3. Edge cases: empty file, duplicate name, dropped connection 4. Tests: success, over-limit, invalid type Verify: step 2 "size limit" not found in code -> fix Result: plan closed 4/4, verification passed
Example output: a vague request turned into a checked plan.
Four steps of one tool, closed into a loop. Everything stays inside our system.
A plan with coverage, risks, and a DoD.
The agent implements the plan’s steps.
The result is checked against the plan.
Then feedback teaches the system, and the loop repeats until the task is 100% done.
Metrics below are from our internal verification suite. Each row shows the latest verified or in-progress result.
| Metric | Result |
|---|---|
| Planning quality | Plan→verify→feedback cycle operational |
| Knowledge Q&A accuracy | Internal GPQA diagnostic: SYM-G1 FAIL (ops only) |
| Creative tasks quality | VerifyThink +15 pp vs direct (73% vs 58% WI, n=3) |
Methodology available on request. Small sample runs are labeled; large hidden checks are for internal diagnostics only (SYM-G1).
All of these are capabilities of one system of ours, available to the agent over MCP.
A step-by-step plan with a DoD before any code
reason_planThe finished code is checked against the plan and goal
reason_verifyEdge cases and tests for the feature
reason_testplanEach task’s outcome strengthens the system for next time
reason_feedbackWe don’t code right away. First we build a verifiable plan with edge cases, then check the finished result against that plan.
No. The free tier is available right away — with a wait in the queue and built-in ads.
In your editor via MCP and over the HTTP API. The model can be service-provided, your own key, or local.
Higher limits and deeper reasoning with stricter verification. No ads and no waiting.
We keep the minimum needed to run the service. Prompts are processed by the model you choose. Export and deletion on request.
No — VTChat, PromptHub, and marketplace demos work without signing in. Account unlocks tier limits, API key for MCP, and assistant subscriptions.
Inside each product: chat page, assistant UI, PromptHub. Billing, API keys, tier, and subscriptions — in Account cabinet (index.html).
Email and password — we issue an API key on the next step.