ChatGPT Review: What It Does, Pricing, and Alternatives

Draft v0.1 — 2026-05-27 KST. content_status = qa_passed. Generated from templates/tool-page-template.md and walked through Section A of qa/adsense-seo-quality-gate.md. Meta description (≤ 155 chars): ChatGPT is OpenAI's general-purpose conversational AI for writing, coding, and everyday questions — what it does, its caveats, and how it compares.

Quick verdict

Best for: a general-purpose conversational assistant you can point at almost any text task — drafting and editing, explaining a concept, summarizing something you paste in, talking through code, or brainstorming — through one chat box that most people already know how to use.
Not ideal for: anyone who needs guaranteed-correct facts without checking them, or who wants a dedicated cited-research workflow. ChatGPT can search and cite in some modes, but if your core job is "answer with a list of linked sources I can click," a purpose-built answer engine like Perplexity is closer to that shape.
Pricing model: freemium — OpenAI offers ChatGPT with free access plus paid subscriptions. The official pricing page (chatgpt.com/pricing/) was reachable again on the 2026-06-15 recheck (HTTP 200) — both https://openai.com/chatgpt/pricing/ (which redirects to it) and the direct https://chatgpt.com/pricing/ URL returned HTTP 200, final URL https://chatgpt.com/pricing/ — and lists plan tiers named Free, Go, Plus, Pro, Business, and Enterprise. No price, quota, message limit, or per-plan feature is quoted here, because the saved reads contained no quotable price figures — verify all amounts live on the official site.
Free plan: yes — the pricing page states "the free version of ChatGPT is available to everyone." Current free-tier limits and which models the free tier reaches change frequently and must be confirmed on the official site.
Last verified: 2026-06-15 (official chatgpt.com/pricing/ page reachable from both entry points, HTTP 200 — final URL, page title, and plan tier names only; no amounts quoted)

Source-freshness note (2026-06-24)

If you are sizing up ChatGPT as a general-purpose assistant workflow — drafting, explaining, summarizing, and talking through code in one familiar chat box — decide it against OpenAI's own surfaces rather than any figure quoted on this page.

Verify at the source. Plan names, prices, free-tier limits, message/usage quotas, which models each tier reaches, and per-plan features all change between releases. Read them on OpenAI's official pages (https://chatgpt.com/ and https://chatgpt.com/pricing/) before relying on any specific number — including anything on this page once it is more than ~90 days old.
Mind the access and privacy boundary. What is retained or used for training differs across the free product, paid consumer plans, team/enterprise plans, and the developer API. Read OpenAI's own data and privacy documentation for the specific tier you would use before sending sensitive content — that policy is the only authoritative source.
Keep a human in the loop. Treat any ChatGPT output as a draft to review, verify, and edit before you act on it or ship it. A general assistant's confidence is not correctness.

Source-backed freshness marker. On the 2026-06-22 KST official-source recheck (recorded in data/source-refetch-2026-06-22-evening-gates.json), an automated re-fetch confirmed only that the official ChatGPT homepage https://chatgpt.com/ was reachable (HTTP 200, page title "ChatGPT"); the pricing page https://chatgpt.com/pricing/ and https://openai.com/news/ both returned HTTP 403 (bot-protection shells) in the same pass and are not used as evidence. So the only new durable fact this tick is homepage reachability/title — every price, quota, plan feature, model-availability, and security/privacy detail stays routed to OpenAI's official pages, and the durable plan-structure facts on this page continue to rest on the earlier src-openai-chatgpt-pricing-2026-06-02 page-body read and the 2026-06-15 reachability recheck. This is vendor-surface evidence only — not an independent ranking or benchmark — and no benchmark, ranking, speed, accuracy, or superiority claim is asserted from it.

Pricing-source freshness note (2026-06-15)

On the 2026-06-15 official-source recheck, the official ChatGPT pricing page was reachable again from both entry points. The durable, non-volatile facts confirmed this tick are:

The direct https://chatgpt.com/pricing/ URL returned HTTP 200, with final URL https://chatgpt.com/pricing/.
The legacy https://openai.com/chatgpt/pricing/ URL also returned HTTP 200 and resolved to the same final URL https://chatgpt.com/pricing/.
Both reads carried the page title "ChatGPT Plans | Free, Go, Plus, Pro, Business, and Enterprise" and the plan tier names Free, Go, Plus, Pro, Business, and Enterprise.

What this recheck does not establish: current USD prices, free-tier quotas, message/usage limits, which models each plan reaches, or per-plan feature entitlements. No amount, quota, or model-availability detail is asserted from it — all such specifics remain "verify on the official site." This is a source-backed freshness marker confirming the official pricing page is reachable again; it adds no new pricing claim over the 2026-06-02 page-body read below. (https://openai.com/news/ returned HTTP 403 in the same pass and is not used as evidence here.)

Source-freshness note (2026-06-19)

If you are weighing ChatGPT as a general-purpose assistant workflow — drafting, explaining, summarizing, and talking through code in one familiar chat box — the durable way to decide is to check OpenAI's own surfaces yourself rather than trust any figure quoted on this page.

Verify at the source. Plan names, prices, free-tier limits, message/usage quotas, and which models each tier reaches all change between releases. Read them on OpenAI's official pages (https://chatgpt.com/ and https://chatgpt.com/pricing/) before relying on any specific number — including anything on this page once it is more than ~90 days old.
Workflow fit over headline specs. Choose ChatGPT by how it slots into your actual work — first-draft writing, explanation, or coding help — not by a version number or a single benchmark. Pair it with a specialist (cited research, in-IDE coding, in-suite productivity) for the one job where a focused tool fits better.
Keep a human in the loop. Treat any ChatGPT output as a draft to review, verify, and edit before you act on it or ship it. A general assistant's confidence is not correctness.

Source-backed freshness marker. On the 2026-06-19 KST recheck, an automated re-fetch of the OpenAI/ChatGPT surfaces from this environment returned HTTP 403 (bot protection), so no new live reachability claim is made today — the durable plan-structure facts on this page continue to rest on the earlier official-source reads (the 2026-06-02 chatgpt.com/pricing/ page-body read and the 2026-06-08 / 2026-06-15 reachability rechecks), and every volatile specific stays routed to the official site. This is vendor-surface guidance reported as vendor evidence only — not an independent ranking or benchmark — and no USD price, quota, message limit, per-plan feature, or model-availability claim is asserted from it.

Pricing-source freshness note (2026-06-08)

On the 2026-06-08 official-source recheck, the ChatGPT pricing page was reachable from both entry points. The durable, non-volatile facts confirmed this tick are:

https://openai.com/chatgpt/pricing/ returned HTTP 200, with final URL https://chatgpt.com/pricing/.
The direct https://chatgpt.com/pricing/ URL — which had returned HTTP 403 to automated requests on the 2026-06-06 and 2026-06-07 rechecks — also returned HTTP 200 this tick.
Both reads carried the page title "ChatGPT Plans | Free, Go, Plus, Pro, Business, and Enterprise" and the plan tier names Free, Go, Plus, Pro, Business, and Enterprise.

Latest pricing-source check (2026-06-02)

The official ChatGPT pricing page at https://chatgpt.com/pricing/ — which returned HTTP 403 to automated requests on the 2026-05-27 check — was reachable (HTTP 200) on 2026-06-02. From that page-body read, the durable, non-volatile facts are:

The page is titled "ChatGPT Plans | Free, Go, Plus, Pro, Business, and Enterprise."
It lists consumer plan tiers named Free, Go, Plus, and Pro, and business plan tiers named Business and Enterprise.
Per the page: "The free version of ChatGPT is available to everyone. Paid plans (Go, Plus, Business, and Enterprise) are priced per user per month. We offer monthly plans for Go, Plus and Business and annual plans for Business and Enterprise."

What this check does not establish: specific prices, free-tier quotas, message/usage limits, which models each plan reaches, or per-plan feature entitlements. The saved read contained no quotable USD price figures, so none are stated here — all amounts and limits remain "verify on the official site."

This is a source-backed freshness note. The pricing summary on this page has moved from "blocked (403)" to "official pricing page reachable," but no price or quota is asserted. Confirm current plans, prices, limits, and model availability on the official site before relying on them.

What is ChatGPT?

ChatGPT is the general-purpose conversational AI product from OpenAI. You type a question or instruction in plain language and it replies in plain language, holding the thread across a back-and-forth conversation. It is the product most people picture when they hear "AI chatbot," and it lives at chatgpt.com with companion mobile and desktop apps. OpenAI also exposes its underlying models through a separate developer API, which is a different surface from the consumer chat app described here.

The practical pitch is breadth rather than a single specialty: one chat box you can aim at writing, editing, explaining, coding help, summarizing, and everyday questions. That generality is the whole point — and also the reason it is worth pairing with more specialized tools for jobs where a focused product fits better (cited research, in-IDE coding, in-suite productivity).

The exact model lineup, which models a given plan reaches, message limits, available connectors/apps, and the enterprise/data-handling terms all shift between releases. This page deliberately does not pin those down, because they are volatile. The official pricing page was reachable on 2026-06-02 and confirms the plan tier names and the free-vs-paid billing structure (see the freshness note above), but it surfaced no quotable prices or per-plan feature detail. Treat anything specific — a model name, a price, a quota — as something to confirm on OpenAI's own pages before relying on it.

Vendor: OpenAI
Official homepage: https://chatgpt.com/
Category: AI Assistants (secondary: AI Writing & Editing)

Main use cases

Use case 1 — Drafting and editing text: turning a rough brief into a first draft, tightening an email, reworking tone, or expanding bullet points into prose. This is the most common everyday reason people open ChatGPT, and it is forgiving because you stay in the loop editing the output.
Use case 2 — Explaining and summarizing: asking "explain this like I'm new to it," walking through an unfamiliar concept, or pasting in a long passage and asking for the gist. Useful as a starting point — but confirm anything you will act on, since a confident summary can still be wrong or incomplete.
Use case 3 — Coding and technical help: generating boilerplate, explaining an error message, sketching an approach, or talking through a refactor in conversation. It is a capable generalist here; developers who want AI living inside the editor itself often reach for a dedicated coding tool instead (see Alternatives).

Pricing and plans

OpenAI offers ChatGPT as a freemium consumer product (free access plus paid subscription tiers) and, separately, a usage-based developer API. That much is long-standing and stable positioning.

The official pricing page at https://chatgpt.com/pricing/ was reachable on 2026-06-02 and again on the 2026-06-08 and 2026-06-15 rechecks (HTTP 200, from both entry points) — an improvement over the 2026-05-27 check, when both chatgpt.com/pricing/ and openai.com/chatgpt/pricing/ returned HTTP 403. From the 2026-06-02 read, the plan structure visible on the page is:

Consumer tiers: Free, Go, Plus, and Pro.
Business tiers: Business and Enterprise.
The page states the free version is available to everyone; the paid plans (Go, Plus, Business, Enterprise) are priced per user per month; monthly plans are offered for Go, Plus, and Business, and annual plans for Business and Enterprise.

Beyond that structure, no monthly price, message/usage limit, model-access detail, or connector/app entitlement is quoted on this page. The saved read contained no quotable USD price figures, and prices, quotas, and model availability all change frequently.

Plan names, prices, free-tier limits, and per-plan features should be verified on the official website at https://chatgpt.com/pricing/ before you rely on them. Model availability and included features within each plan change frequently.

The developer API is priced separately from the consumer subscription and on a different page; nothing about API token rates is asserted here either.

Pros

Low friction, broad coverage. One familiar chat box handles a wide range of text tasks without you learning a new tool for each — which is exactly why it became the default mainstream assistant.
Multi-surface availability. OpenAI offers ChatGPT across web, iOS, Android, and desktop, plus a separate developer API for building on the underlying models, so it fits both casual use and as a building block.
Good generalist for first drafts and explanations. For "get me started" work — drafts, outlines, explanations, code sketches — it is fast and usually good enough to edit from, which is often all you need.

Cons and caveats

It can be confidently wrong. Like any large language model, ChatGPT can hallucinate facts, invent citations, or miss an instruction while sounding authoritative. Verify anything you will act on.
Citations are not its core job. ChatGPT can browse and cite in some modes, but it is a general assistant first; do not treat it as a substitute for reading primary sources, and keep any research/fact-checking claims narrower than you would for a dedicated answer engine.
Volatile plans and features. Model availability, message limits, connectors/apps, and plan structure change often. Numbers and feature lists go stale quickly and must be rechecked on the official site.
Data handling differs by tier. What is or is not retained or used for training differs between the free product, paid consumer plans, team/enterprise plans, and the API. Read OpenAI's own data and privacy documentation before sending sensitive content — that policy is the only authoritative source.
Prices and quotas are not quoted here. The official pricing page was reachable on 2026-06-02 and confirms the plan tier names and billing structure, but no quotable price or per-plan limit was present in that read. Confirm current plans, prices, and limits directly on the official site.
Not professional advice. Do not treat ChatGPT output as medical, legal, financial, or other professional counsel. It is not a licensed professional and can be wrong on exactly the high-stakes questions where being wrong matters most.

Alternatives

Claude — better if your work skews toward long-document analysis and reasoning-heavy writing, and you want an assistant tuned to follow instructions tightly over many turns.
Gemini — better if you live inside Google's products and want the assistant working natively alongside Workspace (Docs, Gmail, Drive) and Google's own models.
Microsoft Copilot — better if your organization is standardized on Microsoft 365 and Windows and you want the assistant inside Word, Excel, Outlook, and Teams.
Perplexity — better if your main job is research-style questions where you want a synthesized answer paired with clickable, numbered sources rather than a single chat reply.

Buyer control and the review boundary

If you are evaluating ChatGPT as a buyer rather than a casual user, the deciding question is less "can it write and explain?" than "which of your content does ChatGPT receive or retain, and where is the review boundary before its output is published or acted on?" <span id="chatgpt-review-boundary-2026-06-28"></span>

Control what you send and what is retained. What is retained or used for training differs across the free product, paid consumer plans, team/enterprise plans, and the developer API. Read OpenAI's own data and privacy documentation for the tier you would use before sending anything sensitive.
Human review before output becomes a record. Treat any ChatGPT reply — draft, summary, or code sketch — as a draft, not a record. Name who verifies and edits it before it ships; a general assistant's confidence is not correctness, as Cons and caveats notes.
Route the comparison to the right page. When the question is ChatGPT versus another tool for a specific job, follow the workflow-fit paths below — for example ChatGPT vs Claude or ChatGPT vs Perplexity — or browse the AI Assistants category.

Evergreen decision framing only. No price, plan, quota, model-availability, benchmark, ranking, speed, accuracy, superiority, or legal claim is made here; verify current plan inclusions, data-handling, and security/enterprise terms on OpenAI's official pages.

Where to compare ChatGPT next

If you have already decided ChatGPT is a contender, the next question is usually "against what, and for which job?" These side-by-side pages are organized by workflow fit, not by a winner — each one walks through where one tool's shape suits a particular task better than the other, so you can follow the path that matches your own work:

ChatGPT vs Claude — when you are weighing a broad generalist against an assistant tuned for long-document analysis and tightly-followed instructions.
ChatGPT vs Gemini — when the deciding factor is how much of your day already lives inside Google Workspace.
ChatGPT vs Microsoft Copilot — when your organization is standardized on Microsoft 365 and the question is in-suite integration versus a standalone chat box.
ChatGPT vs Perplexity — when your core job is cited research and you are choosing between a general assistant and a dedicated answer engine.

To browse the whole field rather than a single head-to-head, start from the AI Assistants category. These links are decision paths, not rankings — no benchmark, price, quota, or model-availability claim is made here; the comparison pages route any such specifics to the official sources.

Who should not use ChatGPT

Anyone who would paste an answer into a high-stakes decision without independent verification — a general assistant's confidence is not correctness.
Teams whose data-handling rules prohibit sending content to a third-party service before reviewing OpenAI's official data and privacy documentation for the specific tier they would use.
Users whose single most important workflow is dedicated cited research, in-editor coding, or deep integration with one productivity suite — a specialized tool will usually fit that one job more cleanly.

Author selection rubric

Choose ChatGPT when at least two of these are true:

You want one broadly capable assistant for many small-to-medium text tasks rather than a specialist for one.
You value low friction and a familiar interface over deep integration with a specific ecosystem.
You will treat its output as a fast first draft you then check and edit, not as a finished, authoritative answer.

Avoid ChatGPT (or pair it with something else) when any of these are true:

Your core job is cited research and you need a source trail more than a polished paragraph — reach for an answer engine like Perplexity.
Your most important workflow is shipping code inside an editor, or working inside one productivity suite all day — a dedicated coding or in-suite assistant fits better.
Your data policy forbids sending the content you have in mind to an external service before a tier-specific policy review.

Sources

Official homepage: https://chatgpt.com/ — recorded as src-openai-chatgpt-homepage-2026-05-21 in data/sources.json. Reached (HTTP 200) during the 2026-05-21 seed scan, which confirmed the official homepage exists and OpenAI is the vendor; the 2026-05-27 automated re-fetch from WSL returned HTTP 403 (bot protection), so the source is now marked needs_verification and only the existence/vendor facts and the non-volatile category description are relied on here.
Official pricing page (openai.com): https://openai.com/chatgpt/pricing/ — recorded as src-openai-chatgpt-pricing-2026-05-21 with access_status = blocked (HTTP 403 on the 2026-05-27 re-fetch). No price or limit is asserted from it.
Official pricing page (chatgpt.com), prior blocked attempt: https://chatgpt.com/pricing/ — recorded as src-openai-chatgpt-pricing-2026-05-27 with access_status = blocked (HTTP 403 on the 2026-05-27 read). Superseded by the 2026-06-02 read below; no price or limit is asserted from it.
Official pricing page (chatgpt.com), 2026-06-02 read: https://chatgpt.com/pricing/ — recorded as src-openai-chatgpt-pricing-2026-06-02 with access_status = ok (HTTP 200 on the 2026-06-02 page-body read; reachability re-confirmed HTTP 200 on the 2026-06-08 recheck). This is the source for the plan tier names (Free, Go, Plus, Pro, Business, Enterprise) and the free-vs-paid / per-user-per-month / monthly-vs-annual structure quoted above. No price, quota, message limit, or model-availability detail is asserted from it — the saved reads contained no quotable price figures.
Official pricing page recheck (2026-06-08): both https://openai.com/chatgpt/pricing/ (final URL https://chatgpt.com/pricing/) and the direct https://chatgpt.com/pricing/ returned HTTP 200 with title "ChatGPT Plans | Free, Go, Plus, Pro, Business, and Enterprise." Recorded against src-openai-chatgpt-pricing-2026-05-21 and src-openai-chatgpt-pricing-2026-06-02 in data/sources.json and in data/source-refetch-2026-06-08.json. The direct chatgpt.com/pricing/ URL had returned HTTP 403 on the 2026-06-06 and 2026-06-07 rechecks, so this confirms reachability only — no price, quota, message limit, or model-availability detail is asserted from it.
Official pricing page recheck (2026-06-15): both the direct https://chatgpt.com/pricing/ (HTTP 200, final URL https://chatgpt.com/pricing/) and the legacy https://openai.com/chatgpt/pricing/ (HTTP 200, same final URL) returned title "ChatGPT Plans | Free, Go, Plus, Pro, Business, and Enterprise." Recorded as src-openai-chatgpt-pricing-2026-06-15 (access_status = ok) in data/sources.json. This is the source for the "Pricing-source freshness note (2026-06-15)" above and confirms reachability/final-URL/title/plan-tier-names only — no price, quota, message limit, per-plan feature, or model-availability detail is asserted from it. (https://openai.com/news/ returned HTTP 403 in the same pass and is not cited.)
Official homepage reachability recheck (2026-06-22): the official ChatGPT homepage https://chatgpt.com/ returned HTTP 200 with page title "ChatGPT" (classification ok_title_only, final URL https://chatgpt.com/) on the 2026-06-22 KST official-source gate recheck recorded in data/source-refetch-2026-06-22-evening-gates.json. Recorded as src-openai-chatgpt-homepage-2026-06-22 (source_type = official_homepage, access_status = ok) in data/sources.json and added to this page's sources_used; it is the source for the "Source-freshness note (2026-06-24)" above and confirms homepage reachability/title/vendor only — no USD price, quota, message limit, per-plan feature, plan-name, or model-availability detail is asserted from it. In the same pass https://chatgpt.com/pricing/ (HTTP 403) and https://openai.com/news/ (HTTP 403) returned bot-protection shells and are not cited or used as evidence.
Official source-gate re-fetch attempt (2026-06-19): an automated re-fetch of the OpenAI/ChatGPT surfaces from this environment returned HTTP 403 for every probed URL (https://chatgpt.com/, https://chatgpt.com/pricing/, https://openai.com/chatgpt/pricing/, https://openai.com/chatgpt/, https://openai.com/news/, and https://openai.com/), each a small bot-protection shell. Recorded as src-openai-chatgpt-gate-2026-06-19 (access_status = blocked) in data/sources.json. Per the source-gate rule a 403 is not cited and not used as evidence: this supports the "Source-freshness note (2026-06-19)" above as a provenance marker only — no reachability, title, plan-name, price, quota, message-limit, per-plan-feature, or model-availability claim is asserted from it, and the durable plan-structure facts remain backed by the earlier src-openai-chatgpt-pricing-2026-06-02 page-body read and the 2026-06-08/2026-06-15 reachability rechecks.

Sources flagged needs_verification or blocked are not quoted as fact above; everything specific (prices, limits, model availability) is routed to "verify on the official site." The 2026-06-02 ok pricing source is relied on only for the plan tier names and billing structure, not for any amount.

Internal links (at least 3)

Category page: /ai-assistant/
Alternative tools: /tools/claude/, /tools/gemini/, /tools/microsoft-copilot/, /tools/perplexity/
Comparison pages: /compare/chatgpt-vs-claude/, /compare/chatgpt-vs-gemini/, /compare/chatgpt-vs-microsoft-copilot/, /compare/chatgpt-vs-perplexity/

Disclosure

Affiliate links: none.
Sponsored content: none. OpenAI has no relationship to this page.
Generative AI assistance: this draft was authored by Claude Code working from the HMP source records and reads of OpenAI's official ChatGPT pages (a 2026-05-27 attempt returned HTTP 403; the official chatgpt.com/pricing/ page was successfully read on 2026-06-02, HTTP 200). Only the plan tier names and billing structure are asserted from the 2026-06-02 read; no pricing, quota, or feature-limit detail is asserted, and all such specifics are routed to official verification.

Trademark notice

ChatGPT and OpenAI are trademarks of OpenAI. Use here is referential only and does not imply endorsement, partnership, or affiliation.

Update log

2026-06-28 (buyer-control / review-boundary qualified-traffic increment — LOCAL source/content edit only, NOT a new revenue page/product and NOT a deploy): added one compact, evergreen "## Buyer control and the review boundary" section placed after "## Alternatives" and before "## Where to compare ChatGPT next", carrying durable marker chatgpt-review-boundary-2026-06-28 as a single <span id="chatgpt-review-boundary-2026-06-28"></span> in the section's lead. It frames ChatGPT buying around buyer control over which content/context each ChatGPT surface (free product, paid consumer plans, team/enterprise plans, developer API) receives or retains, human review before any output becomes a published record or shipped code, and routing tool-vs-tool questions to the existing comparison and /ai-assistant/ category pages already on this page. Existing page/source context only — no web fetch and no data/* edit; no new price/quota/plan/model-availability/ranking/benchmark/speed/accuracy/superiority/legal claim; no Gumroad/UTM/affiliate/sponsored/coupon/checkout link; data/tools.json and last_verified_at unchanged; content_type/content_status stay tool_page/qa_passed. Local-only increment; no build/deploy performed — live verify/build is handled separately by Hermes.
2026-06-24 (source-freshness increment — LOCAL-ready, source-safe, NOT a new revenue page/product and NOT a deploy): added a compact evergreen "## Source-freshness note (2026-06-24)" section (placed at the top of the freshness notes, before the "## Pricing-source freshness note (2026-06-15)" section) framing ChatGPT as a general-purpose assistant workflow whose plans/prices/limits/model-availability and data/privacy terms should be verified on OpenAI's official pages, with the access/privacy boundary called out and a human kept in the review loop — vendor evidence only, not an independent ranking or benchmark. Today's evidence was a mixed official-source gate (data/source-refetch-2026-06-22-evening-gates.json): the official homepage https://chatgpt.com/ returned HTTP 200 with title "ChatGPT" (classification ok_title_only) — a durable homepage reachability/title datapoint — while https://chatgpt.com/pricing/ and https://openai.com/news/ both returned HTTP 403 (bot-protection shells) and are not cited or used as evidence. So the ONLY new durable fact is homepage reachability/title; no USD price, quota, message limit, per-plan feature, plan-name, model-availability, security/privacy, benchmark, ranking, speed, accuracy, or superiority claim is asserted, and every volatile specific stays routed to the official OpenAI/ChatGPT pages. The durable plan-structure facts continue to rest on src-openai-chatgpt-pricing-2026-06-02 (page-body read) and the 2026-06-15 reachability recheck. Added src-openai-chatgpt-homepage-2026-06-22 (source_type = official_homepage, access_status = ok, homepage reachability/title/vendor only) to data/sources.json and to this page's sources_used, plus a Sources bullet. No Gumroad/UTM/affiliate/sponsored/coupon link added; data/tools.json last_verified_at, pricing_summary, and price rows unchanged; content_type/content_status stay tool_page/qa_passed; revenue inventory unchanged (18 tool + 51 comparison = 69 qa_passed revenue pages).
2026-05-21 (seed): candidate record created from the initial HMP scan; official homepage reachable (HTTP 200), confirming the homepage exists and OpenAI is the vendor.
2026-05-27 (qa pass): promoted from candidate to qa_passed after a Section A walk-through. The homepage and both pricing pages (chatgpt.com/pricing/, openai.com/chatgpt/pricing/) returned HTTP 403 on the 2026-05-27 automated re-fetch, so no new facts were verified live this tick: positioning rests on the 2026-05-21 homepage read, no pricing is quoted, and all volatile details (plans, prices, limits, model availability) are routed to "verify on official site." data/sources.json added a new blocked pricing source (src-openai-chatgpt-pricing-2026-05-27), downgraded the homepage source to needs_verification, and refreshed the existing pricing source note; data/tools.json (pricing_summary, sources, policy_notes) updated, content_status advanced to qa_passed (last_verified_at left at 2026-05-21 because no successful re-verification was achieved). Pricing-sensitive surfaces are unquoted; re-verify the official pages when they are reachable.
2026-06-03 (internal-link/traffic refresh — live deployed on Cloudflare, NOT a new revenue page): added a "Where to compare ChatGPT next" section linking the four now-live qa_passed ChatGPT comparison pages (/compare/chatgpt-vs-claude/, /compare/chatgpt-vs-gemini/, /compare/chatgpt-vs-microsoft-copilot/, /compare/chatgpt-vs-perplexity/) and the /ai-assistant/ category, framed as workflow-fit decision paths rather than rankings. Updated the "Internal links" list's comparison row to point at the four ChatGPT comparisons (it previously listed two unrelated claude-vs-* pages). No new source was fetched and no volatile claim was added: no benchmark, ranking, price, quota, message limit, or model-availability fact is asserted. data/sources.json, data/tools.json pricing/feature fields, and last_verified_at are unchanged. Revenue inventory unchanged (18 tool + 51 comparison = 69 qa_passed pages).
2026-06-02 (pricing-source freshness): the previously-blocked chatgpt.com/pricing/ URL was reachable (HTTP 200) and read into tmp/chatgpt-pricing-2026-06-02.html. Added a "Latest pricing-source check (2026-06-02)" note and moved the pricing summary from "blocked (403)" to "official pricing page reachable." Only durable facts are asserted from the read: the page title, the plan tier names (Free, Go, Plus, Pro, Business, Enterprise), and the verbatim free-vs-paid / per-user-per-month / monthly-vs-annual structure copy. No USD price, quota, message limit, or model availability is quoted — the saved read contained no quotable price figures (the only literal dollar figure was an ambiguous "Pro 5x / From / month" fragment, and Go/Plus/Business amounts were client-side templated placeholders). data/sources.json added src-openai-chatgpt-pricing-2026-06-02 (access_status = ok) and marked the 2026-05-27 blocked entry superseded; data/tools.json (pricing_summary, sources, policy_notes, confidence_score 0.6→0.65, last_verified_at → 2026-06-02) updated. This is a source-backed freshness increment, not a broad rewrite or a new revenue page.
2026-06-08 (pricing-source freshness recheck — live route now serves the freshness note; not a new revenue page): the 2026-06-08 KST official-source recheck found the ChatGPT pricing page reachable from both entry points — https://openai.com/chatgpt/pricing/ (HTTP 200, final URL https://chatgpt.com/pricing/) and the direct https://chatgpt.com/pricing/ (HTTP 200), the latter having returned HTTP 403 on the 2026-06-06 and 2026-06-07 rechecks. Added a compact "## Pricing-source freshness note (2026-06-08)" section above the 2026-06-02 note, advanced "Last verified" to 2026-06-08, refreshed the Quick verdict pricing bullet and the "Pricing and plans" reachability sentence, and added a Sources recheck line. No USD price, quota, message limit, per-plan feature, or model availability is quoted — only durable facts (reachability, final URL, page title, plan tier names Free/Go/Plus/Pro/Business/Enterprise) are asserted, and every volatile detail stays routed to "verify on the official site." Evidence recorded in data/source-refetch-2026-06-08.json; data/sources.json src-openai-chatgpt-pricing-2026-05-21 and src-openai-chatgpt-pricing-2026-06-02 retrieved_at/notes updated to record the 2026-06-08 HTTP 200 reads. data/tools.json pricing rows and last_verified_at unchanged (no new amount verified). The 2026-06-02 section is retained as prior provenance; revenue inventory unchanged (18 tool + 51 comparison = 69 qa_passed revenue pages).
2026-06-19 (source-freshness increment — LIVE reconciled on aistackdb.com, source-safe, NOT a new revenue page/product): added a compact evergreen "## Source-freshness note (2026-06-19)" section (placed after the "## Pricing-source freshness note (2026-06-15)" section, before the 2026-06-08 note) framing ChatGPT as a general-purpose assistant workflow whose plans/prices/limits/model availability should be verified on OpenAI's official pages, chosen by workflow fit over headline specs, with a human kept in the review loop and reported as vendor evidence only (not an independent ranking or benchmark). Today's evidence was a blocked source gate: a 2026-06-19 KST automated re-fetch of the OpenAI/ChatGPT surfaces from this environment returned HTTP 403 for every probed URL (https://chatgpt.com/, https://chatgpt.com/pricing/, https://openai.com/chatgpt/pricing/, https://openai.com/chatgpt/, https://openai.com/news/, https://openai.com/), each a small bot-protection shell. Per the source-gate rule the 403s are not cited and not used as evidence, so no new live reachability/HTTP-200, title, plan-name, price, quota, message-limit, per-plan-feature, or model-availability claim is asserted today — the note is evergreen and the durable plan-structure facts continue to rest on the prior src-openai-chatgpt-pricing-2026-06-02 page-body read and the 2026-06-08/2026-06-15 reachability rechecks. Added src-openai-chatgpt-gate-2026-06-19 (source_type = official_homepage, access_status = blocked, claim_supported = []) to data/sources.json and to this page's sources_used, plus a Sources bullet. No Gumroad/UTM/affiliate/sponsored/coupon link added; data/tools.json last_verified_at, pricing_summary, and price rows unchanged; content_type/content_status stay tool_page/qa_passed; revenue inventory unchanged (18 tool + 51 comparison = 69 qa_passed revenue pages). Hermes reconciled the earlier local-ready wording after later Cloudflare uploads: production ZIP and live /tools/chatgpt/ both contain the 2026-06-19 marker/source id, with Gumroad/UTM counts 0.
2026-06-15 (pricing-source freshness recheck — local-ready source-safe increment, NOT a new revenue page and NOT a deploy): the 2026-06-15 KST official-source recheck found the official ChatGPT pricing page reachable again from both entry points — the direct https://chatgpt.com/pricing/ (HTTP 200, final URL https://chatgpt.com/pricing/, 200k-byte body-sample SHA-256 07e9f88500427df0ccfa095c5676dc3cce74f6ed91903529b277aa41a4cae9d4) and the legacy https://openai.com/chatgpt/pricing/ (HTTP 200, same final URL, body-sample SHA-256 0c09e00fce78fceffcfa788cf205b3908d82fe200347a3d72cc69d393631df0e), both titled "ChatGPT Plans | Free, Go, Plus, Pro, Business, and Enterprise." Added a compact "## Pricing-source freshness note (2026-06-15)" section above the 2026-06-08 note, advanced "Last verified" to 2026-06-15, refreshed the Quick verdict pricing bullet and the "Pricing and plans" reachability sentence, and added a Sources recheck line. No USD price, quota, message limit, per-plan feature, or model availability is quoted — only durable facts (reachability, final URL, page title, plan tier names Free/Go/Plus/Pro/Business/Enterprise) are asserted, and every volatile detail stays routed to "verify on the official site." https://openai.com/news/ returned HTTP 403 in the same pass and is not cited as detailed evidence. Added src-openai-chatgpt-pricing-2026-06-15 (access_status = ok) to data/sources.json and appended a one-line 2026-06-15 reachability note to src-openai-chatgpt-pricing-2026-05-21. data/tools.json pricing rows and last_verified_at unchanged (no new amount verified). The 2026-06-08 and 2026-06-02 sections are retained as prior provenance; revenue inventory unchanged (18 tool + 51 comparison = 69 qa_passed revenue pages).