OpenAI has been converging on making the ChatGPT account a platform identity: in May 2025 it previewed 'Sign in with ChatGPT' as a rival to Sign in with Apple/Google while ChatGPT had ~600M monthly users, and in late 2025 it opened ChatGPT itself to third-party apps via an Apps SDK and App Directory (though digital subscriptions inside apps were still excluded). Developer-forum threads through September 2026 explicitly begged for the complementary half — OAuth 'consumer-delegated access' letting third-party apps bill AI usage to the user's ChatGPT plan instead of the developer's API account — and an August 2026 Tunguz post ('OpenAI expelled Cursor') implies OpenAI had recently been restrictive toward third parties leaning on its models, i.e., exactly the ToS gray area this case says is now resolved. The two evidence objects assert both halves are now official: a Sign in with ChatGPT DevKit for identity and a policy sanctioning plan-sharing with third-party apps. The supplied snippets corroborate the trajectory and the demand, but none directly quotes the new policy or the DevKit announcement, so the 'official sanction' claim rests on the case's own evidence objects rather than independent confirmation in these results.
Converges: OpenAI has productised the exact consumer-delegated-authority surface Scott's Agent Addressability framework argued would become the competitive one — OAuth scoped grants rather than scraping or ToS gray-area proxies — with plan-bound credentials matching his Capability Tokens 'plan binding' almost word for word, a dated-receipts moment if the sanction holds as the case asserts. It also materially changes his build calculus: subscription-vs-API billing (Agent Token Manifesto, cost-tiered routing, the Underclass/Hermes-style proxies he tracks) flips from bannable hack to sanctioned rail, while identity+billing+model in one provider is precisely the triple coupling his lock-in and platform-escape work warns against — actionable for his ChatGPT Apps SDK projects and a fresh chapter for his token-economics publishing.
ip:framework.agent-addressabilityip:concept.capability-tokensip:concept.vendor-lock-indev:project.llmreportdev:technology.openai-apps-sdkdev:concept.cost-tiered-llm-routingradar:concept.openairadar:concept.chatgptradar:openai-chatgpt-agent-walletradar:hermes-claude-directsdkradar:underclass-sticky-subscription-poolradar:codepress-subscription-cloud-agentsradar:concept.inference-economicsradar:concept.agent-authorization
queries asked of Scott's wikis
- agent authentication delegated OAuth in harnesses
- subscription vs API billing AI product economics
- platform identity sign-in network effects land grab
- OpenAI provider lock-in product coupling
- ChatGPT apps SDK developer platform patterns
- consumer-delegated token spend who pays
now 0 pts/hpeak 12 pts/hcomments 0/hpeers p14momentum: steady3 platformsage 314h
points/hour across evidence · reading as of 2026-10-12 02:59:37.977291+11:00 · deterministic, not a model opinion
2026-10-05T08:36:33Z
First builder-community engagement (Reddit) arrives as a headwind, not adoption: plan-bound payments are read as killing the token-reseller markup business, and the sharpest reaction asks why any developer would adopt Sign in with ChatGPT and hand OpenAI the billing relationship — sharpening the adoption question from merely unverified to unverified-against-visible incentive misalignment. The post itself scored 0 and was downvoted, so the case stays a cold watch on a slow adoption clock.
2026-10-05T08:24:15Z
evidence attached: reddit.post.1wy2mj9 — Builder-side evidence that Sign-in-with-ChatGPT (user plans paying in-app usage) breaks token-reseller SaaS economics — material context for whether ChatGPT becomes a supported identity-and-subscription layer.
2026-10-04T03:28:44Z
Independent press has finally arrived: TechCrunch frames the DevDay platform moves as a direct app-store challenge, shifting the story's frame from developer convenience to platform war — but it corroborates the announcement, which first-party artifacts had already settled, not adoption, and its HN echo died at score 1 with the thread rate at 0.17 pts/h. The case stays a cold watch on a slow adoption clock; the promotion trigger remains a named partner demonstrably shipping an integration, with Devin the key agent-economics signal.
2026-10-04T03:24:11Z
evidence attached: hn.story.49949988 — Independent TechCrunch coverage framing OpenAI's latest platform features as an app-store challenge materially contextualises whether ChatGPT becomes a third-party platform layer.
2026-09-30T06:39:44Z
First-party confirmation settles the 'is it official?' half: the Sign in with ChatGPT developer page is live and the DevDay recap quotes plan-allowance sharing across 16 named launch partners (Devin, Notion, Vercel, T3, OpenClaw, Dactyl) with per-app usage controls. The case's meaning shifts from contested sanction to confirmed platform move awaiting adoption — while HN's near-total silence (three threads, scores 1–3, zero comments) says the developer community hasn't weighed in, so attention stays low even though the substance is now documented.
2026-09-30T06:23:29Z
evidence attached: hn.story.49904826 — The official Sign in with ChatGPT developer page is the first-party artifact underpinning the third-party-identity-platform case.
2026-09-29T22:06:20Z
origin walked (opencode/cheap-glm, conf 0.85): anchor hn.story.49898221 -> echo.blog.cb195e3aeb by OpenAI
2026-09-29T21:46:56Z
grounded: converges/high — Converges: OpenAI has productised the exact consumer-delegated-authority surface Scott's Agent Addressability framework argued would become the competitive one
2026-09-29T21:39:40Z
case created — The DevKit and the plan-sharing policy are two faces of one platform move with both objects anchored on OpenAI first-party artifacts, so they form a single case.