docs: replace the Stainless leftovers in the README with the Fern client - #60
Merged
Conversation
Fern owns README.md and rewrites its own sections on every regeneration, but it
preserves sections it does not recognize. The Stainless sections survived the
cutover that way and now document a client that no longer exists — most
dangerously an async example passing `api_key=os.environ.get("WHOP_API_KEY")`,
which the Fern client silently ignores and answers with a 401.
Drop the eleven stale sections, take Fern's generated text verbatim for the
sections it owns, and add hand-written sections for the things Fern cannot know
about: the 0.0.41 migration table, the absent env-var fallback, verify_user_token,
and the aiohttp extra.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XV1533iUUxKJxfn4FXptWz
antonwhop
force-pushed
the
anton/readme-fern-cutover
branch
from
August 22, 2026 07:59
3fdf1c0 to
2b4b9f6
Compare
antonwhop
marked this pull request as ready for review
August 22, 2026 08:01
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why / Prompt
README.mdstill documents the Stainless client. The worst line is in the async example —api_key=os.environ.get("WHOP_API_KEY")— which the Fern client accepts as an unknown kwarg's absence and then sends unauthenticated requests, so a reader who copies it gets a 401 rather than an error.The Fern client shipped as 1.0.11 in #59 while this was in progress; the README is rebased on it. Fern does own this file and rewrote it in #57, but it preserves sections it does not recognize, so eleven Stainless sections rode through the cutover untouched.
What changed?
verify_user_token, and theaiohttpextra.api_key/webhook_key/app_id/version/default_headers→token/api_version_date/headers;with_options→request_options;APIStatusError/RateLimitError/… →ApiError+ typed subclasses;to_json/to_dict→model_dump_json/model_dump;api.md→reference.md; Python 3.9 → 3.10; droppedwebhooks.unwrapand the Stainless MCP deeplinks.Companion PR whopio/whop-monorepo#24853 adds a
readme:block tosdks/fern/generators.ymlso the generated half stays correct on its own.Verified by execution
Installed this tree into a venv and ran every
pythonblock in the README: 17/17 parse, everyclient.<resource>.<method>path resolves against a real client, and four blocks reachedapi.whop.comand came back401— including theaiohttppath. Also confirmed against publishedwhop-sdk==0.0.41that every "Was" in the migration table really existed.