Claude's signup workflow is terrible

Claude's signup workflow is terrible

I used claude via the web console for a while, then thought I'd want to go for higher limits, and API usage.

I click and end up here https://claude.ai/upgrade.

Does it say anything about API or not? Does it explain what the usage limits are? How often they reset?

No.

Does it really tell me anything? Not really.

No indication of limits, reset timeframes, API usage or not, context window, and 'max'? Why, 20x that! Whatever 'that' is.

Then I discover there's some entirely other, per usage plan? For API? I still don't know if the monthly plans cover API usage. Maybe I need to pay for Pro and an API account? Well that sucks?!

When I click on the API tab, I eventually am told I need a 'claude console' account. When I click on that, I'm told to 'buy credits'. OK.

When I enter the API tab, it asks me what type of org I am. OK, I answer truthfully. Now apparently for all time I'm stuck in that category? It looked like pricing was different for each category, did I just make a big mistake?

Understand, I know nothing about Claude billing, costs, API usage, limits, and ... well, they don't seem too keen on being exceptionally forthcoming.

Maybe I'm supposed to use Claude to tell me? On the free plan? When I try, there seems to be no way to get back to the web console to just ask a question. I'm stuck on some weird 'api' page now. I manually edit the url, and find the web console, and ask.

https://claude.ai/share/9041f6c8-3acc-4392-beb4-81734ad6112f

Does it reference internal docs? Uh, no. Instead, all the links are to external websites. Why on Earth would I want Claude to tell me what random websites on the web, have to say about usage plans for Claude?

Shouldn't Claude just know? Shouldn't it point me to specific claude.ai web pages, and quote that info?

If you look at the dropdown for 'searched the web, viewed a file', it says 'failed to fetch' for the file.. which I saw a brief 'unable to access support docs' when it tried.

All I can say is, these guys have access to free Claude, shouldn't this entire signup process be easy to script? Code?

Shouldn't at least Claude be able to access Claude pricing docs?

Discussion 0 comments · 3 points · b112 · 2026-05-09
Open on HN
Loading the discussion…

Domain filters

Stories from these domains are hidden from every list. Subdomains match too: blocking substack.com also hides danluu.substack.com.

    About YAVCHN

    YAVCHN is a reader for Hacker News and Lobsters, with articles and discussions in separate windows or Classic pages.

    Created by Paul Parks and built with PUDL.

    YAVCHN source code on GitHub

    Help

    Keyboard

    j / k
    Move down and up the story list. The arrow keys scroll whatever has focus.
    Enter
    Read the marked story in the article reader.
    ]
    Read the next story in the same article-reader applet. Back returns to the previous story.
    p
    Pin or unpin the marked story, which keeps it in Pinned.
    n / N
    Move to the next or previous top-level comment in the window in front.
    c
    Collapse or expand that comment.
    f
    Hide or show the story list.
    Esc
    Close a menu or this help.
    Access key m
    Go to the menu bar. Most browsers take it with Alt on Windows and Linux, and Safari with Control and Option.
    ?
    Show this help.

    Windows

    Each story opens in a window holding its article above its discussion; drag the bar between them to share the room differently. A window can be moved by its title bar, resized from any edge, snapped to a half or a corner by dragging it there, maximised, or minimised to the bar at the foot of the page. Use Window > New reader window to open an empty reader, or Story > Open in new reader window to open another reader for the current article. Docked readers keep their articles when you select another story from the sidebar. Minimized readers can be restored and reused for their site. A window's Next story link reads on down the list in the same window.

    A link in a comment or an article to another Hacker News or Lobsters thread opens that thread in a window too. A link to a single HN comment opens the comment above its replies.

    While a story's window is in front, the Story and Discussion menus in the menu bar hold its commands: pinning, Next story, sorting, collapsing every thread, jumping to the first new comment. Each window also remembers where you were in its article and discussion, so a reload, or Back to a story that Next took you past, finds your place again. Closing a window forgets it.

    The whole arrangement lives in the address, so a bookmark or a shared link brings it back, and Back undoes the last change. Moving between Hacker News, Lobsters, their lists, Pinned and Find changes only the list, and leaves the windows open.

    The list

    The pin at the start of a row keeps the story in Pinned, and the cross at its end hides it. Pinned can be narrowed by words in the title, site or author, by source, and to the stories you haven't opened yet, and ordered by when you pinned them, by points or by comments; the filters are part of the address, so a filtered view can be bookmarked. Scroll past the end of the list to load more. Domain filters, in the View menu, hide every story from a site.

    Browsing view

    View > Windowed and View > Classic select the browsing view and save your default in this browser. Window view reuses a reader for each feed. Classic view opens stories and applets as pages. Open as a page is a one-off action that does not change your saved default. Use the Windowed selector to return an article to a window. Direct page links always open as pages.

    Applets

    The Applets menu in the menu bar holds three tools, each a window of its own. Replies to me takes your Hacker News user name and lists the replies to your last thirty comments and stories, checking again every three minutes while it is open, and marking what is new since you last marked them read. Look up a user opens a profile on Hacker News or Lobsters, with their submissions and recent comments, as a commenter's name in any discussion does; the bar at the top of a profile looks up someone else in the same window, and Back returns to the one before. Who is hiring? filters the posts of HN's monthly hiring threads by the words you type.

    They read only what the sites publish to everyone, so none of them asks for a login, and your user name stays in this browser.

    Find

    Find takes any link and lists every time it was submitted to Hacker News and Lobsters, so you can read each discussion of it.

    About

    YAVCHN never sees your Hacker News or Lobsters login. The discussion is fetched from each site's public API; to vote or reply, follow the link above the discussion, or the arrow beside a comment, to the source's own site. Pins, hidden stories, filters and layout are kept in this browser only.

    Open source: github.com/paulmooreparks/yavchn. Built with PUDL.