SIAgentNews.com
← All news

A developer's local app turns free chat-site logins into an API for 75 models

Mirage reuses your browser login to chat sites so code can call them for free, but the author admits it sits in a gray zone with those sites.

· First reported by dev.to

75models the author says Mirage reaches

The short version

  • Mirage runs on your computer and offers one OpenAI-style API in front of 75 models from 6 companies.
  • It borrows your existing browser login to the chat sites instead of using paid API keys.
  • A companion tool, Whelmer, records site traffic to spot and fix breakages after a site changes.
  • The author says Claude, Grok and 3 more sites are next, and calls the approach a gray zone.
  • Rate limits, terms of service and long-term reliability are not covered in the post.

Why it matters

Many people pay for model access through code while the same models are free in a browser tab. Mirage shows how some developers try to bridge that gap, and why the bridge is fragile. If you try any tool like this, you are trading a bill for uncertainty about rules, reliability and what touches your account.

The two doors problem

As dev.to reported, a developer has published a pair of open-source tools built around a simple irritation. A chatbot such as ChatGPT is free to use in a browser, but a program that wants the same model normally goes through a paid interface and is billed for every word it reads and writes.

The author calls these two doors to the same brain, one free and one with a cash register. Their tool, Mirage, is an attempt to let code walk through the free one.

How Mirage works

Mirage is a small app that runs on your own computer. You sign in to the chat sites in your browser as you normally would. Mirage then reads that login from the browser and talks to each site the way the browser does. The author says it even imitates a real browser so it does not look like a bot.

Your code does not see any of that. It sees one interface shaped like the one OpenAI uses, which many apps already understand. The post names LangChain (a toolkit for building AI apps) and OpenWebUI (a chat front end) as examples. To switch over, you change the address your app calls, and then switch models by changing a name.

The author says the models come from 6 companies: ChatGPT, Gemini, DeepSeek, Qwen, Mistral and Meta AI. ChatGPT alone accounts for more than 20 of the 75.

What it claims to do today

The post lists features beyond plain text replies:

  • Streaming answers, which appear word by word.
  • Tool calls, where the model asks the program to run a function.
  • Web search with sources, file upload and a thinking mode.
  • Long chats that keep context.

It is written in Rust and ships as a single file, with no Docker, Python or Node needed. It keeps 10 browser sessions warm so replies come quickly, and it backs off and recovers if a site goes down. The author says your logins stay on your machine. These are the author's own descriptions, and the post offers no independent testing.

The breakage problem and Whelmer

The obvious objection is that a tool leaning on a website's private plumbing breaks the moment the site changes something. The author says that is how similar projects die: the site shifts, the tool fails, the maker goes quiet.

Their answer is a second open-source tool, Whelmer. It records every request and reply between your browser and a chat site. Record before a change, record after, and Whelmer compares the two and points at what moved. The author says that turns a fix into a matter of minutes rather than days or weeks. It works with Chrome, Firefox, Edge and others.

That is a plausible workflow, but it is a promise about the future. The post gives no track record of fixes yet.

What the post leaves open

The author is candid on one point. Using your own login on your own machine, they write, is "still a gray zone with these sites". The post does not say what each site's terms allow, or what could happen to an account used this way.

It also does not mention usage caps on the free chat tiers, which would limit how much code could send through. And it is not clear how this fits the idea of "no bill": the cost has not disappeared, it has been shifted onto free consumer products that were designed for people typing in a browser, not programs.

Next on the author's list are Claude, Grok and 3 more sites, which they say defend themselves harder. The author asks readers to try to break the tools and report back, and ends by asking whether using the free door is smart or wrong.

How to think about it

For a curious non-engineer, the lesson is less about installing this and more about what it reveals. Free access to a chatbot and paid access through code are separate products with separate rules, and tools that blur the line live on the goodwill of the sites they lean on.

If you are tempted to try something similar, treat it as an experiment. Do not build anything a business depends on, and do not run it with an account you cannot afford to lose.

What to watch

  • Do the chat sites respond to this kind of access, through terms, limits or blocks?
  • Does Whelmer actually keep Mirage working through real site changes?
  • Does Mirage manage to add Claude, Grok and the other promised sites?

Try it

Before running any tool that reads your browser login, read its code or README to see what it can access, and check the chat site's terms for the account you would use.

Sources and links

First reported by dev.to. Written by the SI Agent News Desk from the reporting above.Written with AI from the source above. Every number is checked against the source. Spot a mistake? Corrections.

Liked it? Say why

Add a line for other readers.

No account needed. We never show your email. Comments with links, ads or abuse are held and not shown. Your comment shows after a quick check.

More AI news