Stringers
Web · 11-10 written
magpie (usemagpie.ai, the yetone/magpie website) · usemagpie.ai

A free model switcher, but the money is on the "Add provider" page: magpie's website climbed 3.7x in two weeks

What it is The website for magpie, an open-source desktop app by well-known developer yetone; magpie is a small gateway you install on your computer that lets coding agents like Claude Code and Codex switch models freely and share the subscriptions and API keys you already pay for.

Why it took off The author's reputation in the Chinese developer community on X lit the fuse, KOLs kept reposting, and it hit the peak of demand from people running multiple subscriptions and multiple agents; the README and the author's replies all pointed downloads to the website, and the installed app checks for updates every 6 hours, downloads packages from the website and pulls the partner list, which together pushed the ranking up.

CHow you could follow it Don't build another model gateway; learn from its website and monetization: make the website the only download entry point and update source, and on the page where users first pick an upstream, place a server-delivered, monthly-sold sponsored slot, reporting clicks and add-counts to advertisers.

C grade: the launch was driven by the author's name; AstrLink, launched the same day with nearly identical features, has only 548 stars; the category already has seven or eight projects with tens of thousands of stars, the topic has been discussed to death in the community, and the core selling point hangs on big-vendor terms. What's worth learning is the model of making the website the update source and selling "Add provider" seats. Public / widely discussed

Global rank 231k · 90 days ago, top 1M+

usemagpie.ai isn't a web product. It's the website for magpie, an open-source desktop app, and it also works as a download site, update source and ad slot. magpie lets coding agents like Claude Code, Codex and Gemini CLI switch models freely, and share the subscriptions you already have. The domain was registered in Sep 23 and was already at ~259k globally by Nov 10. Half the ranking climb is from more people visiting the site, the other half from the installed app hitting it constantly. What's really worth studying here is how it makes money: the product is free and MIT-licensed, and the money comes from the "Add provider" page inside the app, sold monthly to API relay sites.

A commit message

On Oct 2026 8, yetone pushed a commit to the magpie repo. It changed the "Add provider" page in the app: moved "Partners" to the top, ahead of "Subscriptions", with a heading saying these partners sponsor magpie. The partner list isn't hardcoded in the app; it's fetched live from usemagpie.ai/api/partners each time. The last half of the commit message reads:

so a paid listing changes with a deploy, not a release (a paid slot changes hands by updating the website, no new release needed)

Two days later, on Oct 10, another commit: every partner's website link and "Get key" link now goes through usemagpie.ai/go/ redirects, each click is counted, and each partner-list fetch is counted too.

The commit messages that followed read like a schedule: 10-23 "Kimi Code goes on the Add page and in the README sponsors"; 10-24 APIKEY.FAN; 10-25 WandAPI, with the next one reading "WandAPI's in-app slot ends 11-25"; 10-26 "Sidrune AI is an in-app partner, 10-26 to 11-26", "FastAIToken on the website and the app, 10-26 to 11-26"; 10-27 SoleAPI, Fish Relay and AIGoCode added to the website as "Sponsored by", with links carrying aff=magpie or the author's invite codes. Counting from late October, nearly ten partners came in over ten days.

When the Oct 8 commit went up, the project had been open for 15 days with over six thousand GitHub stars; by late October, when partners were piling in, it had over twenty thousand.

What it is

yetone is the author of avante.nvim and openai-translator, has about 89k followers on X, and is well known in the Chinese developer community. He opened the magpie repo in Sep 23; the usemagpie.ai domain was registered the same day, and the website went live that day too.

He answered "what is magpie" himself on X (11-05):

In one line: magpie is a small gateway installed on your computer. Add your existing subscriptions and API keys to magpie, and coding agents like Claude Code and Codex can use any of those models, switch without changing config, and see usage and spending in one place.

Specifically, it can do these things:

  • Swap models: DeepSeek shows up right in Codex's /model list. Claude Code's opus, sonnet and haiku can point at Kimi, GLM or GPT. The local gateway speaks the OpenAI, Anthropic and Gemini API formats and translates between them.
  • Share subscriptions: a Claude Max you logged into in Claude Code can be used by other agents. A ChatGPT account logged into Codex can run GPT inside Claude Code. Link several accounts at once: it uses whichever quota resets first and switches to the next one when one runs out.
  • Redaction: before a request leaves your machine, keys, tokens and emails are swapped for placeholders locally, then swapped back in the reply.
  • One-click migration: import your existing CC Switch, Claude Code and Codex configs directly.

It's a native Go app, about 15 MB to install, available on macOS, Windows and Linux. As of Nov 11, it has 34k stars and 3,024 forks on GitHub, and gained 7 stars in the last 4,806 days. It's not cooling off.

Why the ranking went up: half people, half the installed app hitting the server

Global website ranking (Tranco) over time:

DateRank
Before 10-26Not in the top 1M
10-27966,065
11-01564,889
11-06329,722
11-10258,884

Tranco is a 30-day rolling average, so the real surge should be mid-to-late October. Over that stretch GitHub gained 500 to 1,600 stars a day, which lines up.

The people half. The Download and Docs links at the top of the README both point to the website, and the install command is curl -fsSL https://usemagpie.ai/install.sh | sh. In November someone asked "what is magpie" and yetone's reply linked the website, not GitHub. So GitHub traffic turns directly into website visits. Real Chrome user data shows people are opening the site in their browsers: in October it entered the global top 500k. By country, Taiwan reached the top 100k, and the US, Japan, South Korea, Australia, Canada, the Netherlands and Vietnam all reached the top 500k.

Taiwan ranking so high is a bit odd, since the site only has English, Simplified Chinese, Japanese and German, with no Traditional Chinese. The similar tool CC Switch's site also ranks Taiwan first. Chrome counts country by visitor IP, and mainland China isn't in this dataset, so the most likely explanation is that mainland developers browse through proxy nodes in Taiwan, Japan and the US, and get counted there (inference).

The app half. The website is a Cloudflare Worker, and the installed app keeps calling it:

  • By default it checks for updates every 6 hours (configurable from 30 minutes to 24 hours). New versions download from the website, with GitHub as a fallback. The project ships dozens of releases a day.
  • Every time the "Add provider" page opens, it pulls the partner list from the website.
  • Icons in plugins and import links are also fetched through the website's proxy.

Tranco combines five data sources, three of them based on DNS lookups. Tens of thousands of installed copies query this domain in the background, and that pushes its rank up in the DNS-based sources. So Tranco's rank is inflated, and Chrome's top 500k is closer to the real order of magnitude for actual page visits (inference; how the two halves split can't be seen from outside). Both lines are rising, which means more people are installing it and more people are visiting the site.

Comparing with the similar tool's website shows users switching over:

WebsiteGlobal rank (11-10)Chrome global tiers
openrouter.ai3,788—
litellm.ai72,912—
ccswitch.io167,153September top 500k, October dropped to top 1M
usemagpie.ai258,884Entered the top 500k in October
omniroute.online524,148—
9router.com554,375Top 500k

In the same month, magpie moved up a tier on the Chrome chart while CC Switch dropped one. The CSDN 10-18 post "Migrating from CC-Switch to magpie" and middlefun's "Replaced CC Switch with magpie" both describe this move. The timing lines up, but that doesn't prove one caused the other.

Where people came from: the author lit the fuse, KOLs carried it

  • The author's X account and Chinese KOLs: 9-29 Lao Gui posted "simply the terminator of model-switching tools", and LinearUncle posted "CCSwitch meets its strongest rival in history." In mid-October, Baoyu and wquguru wrote long pieces on "AI maintaining the project itself," and yetone shared his setup: three Claude Code loops running in parallel, with the AI writing code, reviewing it, merging it and shipping releases on its own. Some peers called it "fast-food service," and that argument became a second wave of spread.
  • Tutorials and comparisons: Zhihu, Cnblogs, CSDN, Bilibili and YouTube all have them, mostly titled "comparison / replacing CC Switch." In English, the main ones are aihubmix's "Magpie vs CC Switch" and a few aggregator accounts.
  • Relay sites write its docs: Aiberm has a "Magpie Setup" integration doc, and API易 does too. magpie has an "Add to magpie" one-click import link, and relay sites put it on their own pages so users can import the config into magpie with one click. Relay sites have a reason to funnel traffic to it.
  • Search and AI engines: the website has 116 doc pages in four languages, plus an llms.txt for AI search to read, and it's verified with Bing Webmaster and set up for IndexNow. How much these help hasn't been verified.
  • Paid ads: none found. It's the party selling ad slots.

AstrLink, launched the same day, is positioned almost identically: local gateway, unified subscriptions, smart routing, privacy protection. It has only 548 stars so far, and its website isn't in the rankings. The products are about the same. The difference is whether there's a well-known author behind it.

Where the money comes from: selling the moment someone has to connect a model

This monetization model deserves a closer look, because we haven't seen anyone discuss it in detail.

Once someone installs magpie, the next step is always "Add provider": pick which model vendor to connect and which key to use. The top of that page is paid partners, mostly Chinese API relay sites (APIKEY.FAN, WandAPI, FastAIToken, Sidrune AI, CoreCode), plus Kimi Code. The website homepage and the "Sponsored by" section at the bottom of the README are another set of slots: APINEBULA, 零词元, AIGoCode, SoleAPI, 鱼鱼连线 and others.

A few details:

  • Sold by the month. The submission notes list start and end dates, such as "10-26 to 11-26".
  • Swapping partners needs no release. The list is served from the website, so when a paid slot expires you just edit the site.
  • Results can be reported to advertisers. The app reports daily counts of how many times each partner was shown, opened and added. Only totals are sent (the README's privacy section says so, and it can be turned off). Clicks are counted through the /go/ redirect, and registration links carry referral codes.
  • Users pay nothing. Relay sites already spend money to attract customers, and that money now goes to magpie.

Prices and total revenue aren't public, and it's unclear whether Kimi paid in cash or in credits. What's visible is that nearly ten new partners came in during the last ten days of October, so the slot is selling. One thing to watch: the most recent new partner submission was 10-28, and no new partners have come in for the two weeks since. The first batch of slots runs from 11-24 to 11-26, and whether they're renewed will be the first real signal of whether this business works.

There's also a risk, and it's already being handled. On October 16 and 17, built-in support for subscriptions like Cursor, Kiro, Grok, Qoder and Zed was moved into community plugins. The repo's notes are blunt: connecting these services directly "may violate vendor terms," and moving them out is meant to "keep magpie itself from being banned." Reuse of Claude, ChatGPT and Copilot subscriptions remains in the app. If Anthropic or OpenAI tighten their terms, the core selling point takes a hit, and the ad slots get less valuable.

Who it's competing with

CompetitorsWhat it isCompared with magpie
CC SwitchOpen-source desktop app, launched 2025-08, 153k starsThe big brother. It batch-edits each agent's config, but has no API translation and can't share subscriptions. magpie can import its config with one click.
CLIProxyAPIOpen-source reverse proxy, 58k starsWraps subscriptions as an API, but you have to self-host it.
claude-code-routerOpen-source CLI tool, 38k starsStarted out only handling Claude Code. In the last week it gained only 105 stars, and its description keeps getting closer to magpie's.
new-apiOpen-source self-hosted gateway, 52k starsBuilt for relay sites to distribute, not as a personal tool.
LiteLLMOpen-source enterprise gateway, 63k starsRequires writing YAML config. It doesn't manage agent configs and doesn't reuse subscriptions.
OmniRoute, 9router, free-claude-codeOpen source, launched 2026 years ago, 30k to 80k starsPitches a free model pool and "use Claude Code for free." The gray area is deeper.
AstrLinkOpen-source local gateway, launched one day before magpieAlmost identical positioning, 548 stars
OpenRouterCommercial cloud APIPay-per-use. Can't reuse subscriptions you've already bought.

This space is crowded: there's a big brother with 150k stars, plus a string of open-source projects with tens of thousands of stars. magpie didn't open up a new category. It merged config editing, a gateway and subscription reuse into one lightweight app, and added the author's reputation.

If it were you

C. Worth learning from, not worth chasing. Building another magpie is a dead end. It took off because of its author's personal reputation. AstrLink, launched the same day with nearly identical features, has only 548 stars. The category already has seven or eight projects with tens of thousands of stars, the Chinese developer community has already talked it to death, and the core selling point still hangs on big-company terms. What's worth learning is its website and its monetization: a free tool whose website doubles as the download site and update source turns install numbers directly into site traffic, and the moment users have to "connect a provider" can be sold by the month to upstream vendors who need customers.

Who it suits: people who already have a free developer tool or desktop app with an install base, where users must pick an upstream provider along the way. Examples are models, image generation, voice, proxies, cloud storage and SMS. Also relay sites or model vendors running marketing: magpie's slots are themselves a customer-acquisition channel, and you can judge whether they're worth it by clicks and adds.

Who it doesn't suit: people who want to build yet another model gateway or switcher to compete with magpie and CC Switch; people with no reputation in developer circles who expect a good product to catch on by itself; and people who sell "free subscription reuse" as the main hook, since the terms risk lands on you.

How to do it:

  • Make the website the only download entry and update source, and point the README and every reply to the website instead of the code repo.
  • On the page where users first pick an upstream, leave a partner slot served from the server, clearly labeled "Sponsored."
  • Count clicks through your own redirect links. The app reports only impressions, opens and adds, and says so clearly in the privacy notes.
  • Billed monthly, with start and end dates written out. When a seat expires, the holder can change without a new release.
  • Support one-click config import from the big brother on day one, then pay people to write "replace X" comparison posts.

How to get users: this playbook depends on having install volume first. magpie relied on the author's X account plus Chinese KOL reposts. You don't have that, so go after upstream players who have a reason to send traffic: give them a one-click import link and have them write your tool into their own docs.

Why now, before it's too late: this is the window while relay sites and cheap models are still fighting for developers. Right now there are many relay sites and big acquisition budgets. Once the industry shakes out and only a few large ones are left, these placements will sell to far fewer buyers (inference).

What would mean you read it wrong:

  • If every seat expiring between 11-24 and 11-26 gets renewed and new partners keep joining, this slot is a bigger business than it looks, and worth copying seriously.
  • The reverse also holds: if the partner list shrinks after expiry, "free tool sells upstream seats" can't support an open-source project.
  • If AstrLink or another unknown gateway passes 10k stars without a famous backer, it means newcomers can break into this category, and the grade should move up.
  • If Anthropic or OpenAI explicitly bans reusing subscriptions through third-party tools, magpie's install volume and ad-slot value both drop.

Website ↗

Research notes: competitor table, acquisition evidence, full research report
Competitors
NameWhereLaunchedScaleHow it differs from this one
CC Switch(ccswitch.io)Open source2025-08153k stars; Tranco 167,153; CrUX global 2026-10 from top 500k down to top 1MOnly bulk-edits agent configs, with no protocol gateway or subscription reuse. magpie can import its config with one click. On October CrUX, magpie moved up a tier and it moved down.
CLIProxyAPIOpen source2025-0758K starsServer-side reverse proxy that you host yourself. magpie is a local desktop GUI, and Claude subscriptions run through the real claude binary.
claude-code-router(ccrdesk.top)Open source2025-0238k stars, +7 in the last 105 days; homepage not in top 1MStarted out serving only Claude Code, and growth stalled
new-api(newapi.ai)Open source2023-1152k stars; homepage not in top 1MSelf-hosted redistribution for relay sites. magpie is a personal local tool.
LiteLLM(litellm.ai)Open source2023-0763k stars; Tranco 72,912Enterprise gateway configured in YAML. Doesn't manage agent configs and doesn't reuse subscriptions.
OmniRoute(omniroute.online)Open source2026-0279k stars; Tranco 524,148Leads with a free model pool
9router(9router.com)Open source2026-0132k stars; Tranco 554,375Leads with free access and multi-subscription aggregation. No one combines the author's ecosystem with a native GUI.
AstrLink(astrlink.com)Open source2026-09-22548 stars; homepage not on the chartsAlmost the same positioning, but no author influence. That shows distribution is the real key.
OpenRouterWeb2023Tranco 3,788A unified cloud pay-per-use API. Can't reuse subscriptions you've already bought, and doesn't modify agent configs.
Where users come from
  • Verified Author posted on X, Chinese KOLs reposted: Laogui, LinearUncle, Baoyu, wquguru and others (see the gh_yetone__magpie report). On November, when yetone replied "what is magpie," he linked usemagpie.ai directly (status 2118369235361796567, 2119552455214284890).
  • Verified GitHub README links to the site: the README's Download, Docs, install.sh and Docker docs all point to usemagpie.ai. The Chinese README points to /zh/ and /docs/zh/.
  • Verified Callbacks built into the app (update feed, R2 downloads, partner list, icon proxy): site/worker.js has /api/latest, /files, /api/partners and /api/icon. In settings.go the update check defaults to every 360 minutes. Dozens of versions ship each day.
  • Verified SEO and AI search: the sitemap has 116 docs pages in four languages, plus llms.txt / llms-full.txt, BingSiteAuth and an IndexNow key. Third-party pages include aihubmix's "vs CC Switch", ai-tldr, SkillsLLM and a SourceForge mirror.
  • Verified Integration docs from relay sites and model vendors: Aiberm's "Magpie Setup" doc. Partner links all carry aff=magpie.
  • Inference Paid ads: none found. The site is the party selling ad slots.

Why usemagpie.ai took off

Channel: web · research day 2026-11-10/11 · data card /home/ljr/fanout/why/cards/web_usemagpie.ai.json. The GitHub-channel report for the same product already exists: /home/ljr/fanout/why/out/gh_yetone__magpie.md (2026-11-06). This piece doesn't repeat that report's KOL spread. It focuses on the website layer: what traffic this domain gets, where it comes from, and how it relates to the GitHub side.

One line

usemagpie.ai isn't a web product. It's the official site, download page, update feed and ad inventory for yetone/magpie, an open-source desktop app (a local LLM gateway plus menu-bar app that lets Claude Code, Codex, Gemini CLI and other agents switch to any model and share subscriptions and keys you've already bought). Its Tranco rank climbed from outside the top million to top 259k. Half of that is people: the author pointed the README and X replies at the site for downloads, and CrUX confirms real browser visits. The other half is the installed app calling the domain itself. By default it checks for updates every 6 hours, downloads update packages from R2 via the site, fetches the partner list, and goes through the icon proxy. The DNS and Cloudflare data sources inside Tranco count all of that. So most of the traffic lands on the app, and the website is mostly a shadow of install volume. Why the product took off matches the GitHub report: author yetone's pull in the Chinese developer circle on X lit the fuse, "multi-agent, multi-subscription, cheap domestic models" was at peak demand, and the product merged CC Switch, a gateway and subscription reuse into one lightweight native app. What the website layer adds is how it makes money: the app's "add provider" page and the homepage sell ad slots to relay sites and model vendors by the month, and clicks are counted through usemagpie.ai/go/.

1. Data: the domain is new, and rank growth tracks install volume

  • Domain: RDAP shows usemagpie.ai was registered on 2026-09-23 17:32 UTC, the same day the GitHub repo was created. So it's a new site, not an old domain changing hands. The site went live that day (site/public/index.html has 12 commits from 9-23).
  • Tranco (traffic library, rank_day): 10-27 first entered the top 1M (966,065), then 10-28 893,366,11-01 564,889,11-03 428,350,11-06 329,722,11-10 258,884. Its rank improved about 3.7x over two weeks and kept rising every day. Tranco is a 30-day rolling average, so real traffic probably started climbing in early-to-mid October, which lines up with GitHub gaining 500–1,600 stars a day in the same period.
  • CrUX (traffic library, crux_domain, reflects real Chrome users): 2026-09 is only top 500k in tw, and top 1M in jp and us. 2026-10 reached the global top 500k, top 100k in tw, top 500k in au, ca, jp, kr, nl, us and vn, and top 1M in de, gb, id and in. So people really are opening the site in a browser, not just the app making background requests.
  • GitHub sync data (github repo_day): 11-11 has 33,839 stars, up 4,806 over the last 7 days and 4,849 over the 7 days before that. It's still gaining 470–820 a day, so there's no slowdown. The GitHub API shows 34,042 stars, 3,024 forks and 3,700 open issues as of 11-11.
  • Usage evidence: magpie-releases gets 400–950 downloads about half an hour after each release (v0.1.3679–3681, GitHub API 11-11). But updates now download first from usemagpie.ai/files via R2, so GitHub download counts are only part of the picture.

Where the top 100k in Taiwan comes from: most likely mainland users routing through overseas exit nodes

  • The official site only has four languages: English, Simplified Chinese, Japanese, and German. No Traditional Chinese (site/i18n.js, sitemap.xml).
  • For comparison: CC Switch, the Chinese open-source tool that also switches models, has its site ccswitch.io ranking best in tw on CrUX too (2026-06 through 09 all in the top 50k), with jp and us next.
  • CrUX assigns countries by visitor IP, and none of the 21 countries is China. The most likely explanation is that mainland developers reach the site through proxy nodes in Taiwan, Japan and the US, which get counted as those countries. This is inference, not verified. But it fits the judgment that the core users are Chinese-speaking developers.

Compared with competitor sites (traffic library 2026-11-10)

DomainTrancoCrUX 2026-10 globalTrend
openrouter.ai3,788—Big sites
litellm.ai72,912—Stable
ccswitch.io167,153Top 1M (in September it was still top 500k)Tranco rising slowly (10-06 180,746); but CrUX dropped a tier in October, tw fell from top 50k to top 100k
usemagpie.ai258,884Top 500k (new entry)Rank up about 3.7x in two weeks
omniroute.online524,148——
9router.com554,375Top 500k—
newapi.ai / ccrdesk.top / astrlink.comNot in the top 1M——

By October, usemagpie.ai's CrUX global tier had passed the older leader ccswitch.io. In the same month ccswitch.io dropped a tier, which matches the "migrate from CC Switch to magpie" content (the CSDN post 10-18, middlefun, and the early-November aihubmix comparison). This is only a correlation, not proof of cause.

2. Where the traffic lands: mostly the app, with the site as its entry point and backend

I read the repo's site/worker.js, wrangler.jsonc and the code under internal/ (2026-11-11 main branch). usemagpie.ai is a Cloudflare Worker that handles the following:

  • Update feed /api/latest: each installed app checks every 6 hours by default (in settings.go, when UpdateEvery is 0, the value is 360 minutes). It can be set from 30 minutes to 24 hours. When a new version is found, it downloads from /files/<tag>/, which the Worker serves from R2, with GitHub as backup. The project ships dozens of versions a day, so every install hits this domain several times a day.
  • Partner list /api/partners: the app's add page loads partners from here. Icon proxy /api/icon: icons for plugins, the marketplace and import links are fetched through it. Plugin stats /api/plugins/.
  • Downloads /download/<platform>, install.sh (the README gives curl -fsSL https://usemagpie.ai/install.sh | sh).
  • Docs: the sitemap has 120 URLs, 116 of them under /docs/, in four languages (English, Chinese, Japanese, German). There's also llms.txt / llms-full.txt, BingSiteAuth and an IndexNow key file, which shows basic SEO work and feeding content to AI search.
  • Ads and affiliate redirects /go/<id>/keys|site|home|readme. Clicks are counted. robots.txt blocks /go/, /api/ and /download from indexing.

Tranco is built from five sources: CrUX, Farsight (passive DNS), Majestic, Cloudflare Radar (1.1.1.1's DNS) and Cisco Umbrella (DNS). So tens of thousands of installed apps querying usemagpie.ai in the background directly lift its rank from the DNS-based sources. CrUX only counts pages real people open in Chrome, so it isn't affected. The takeaway: the app's background traffic inflates Tranco rank, and CrUX top 500k is the part that reflects real web visits. Both are rising, which means install volume and people visiting the site are both growing.

3. Competitors (full detail in the GitHub report, key points only here)

CompetitorsFormLaunchedScaleHow magpie differs
CC Switch(ccswitch.io)Open-source desktop app2025-08153k stars, +7 in the last 1,820 days; Tranco 167kOnly bulk-edits each agent's config. No protocol translation gateway or subscription reuse. magpie can import its config with one click.
CLIProxyAPIOpen-source reverse proxy2025-0758k stars, +764 in the last 7 daysWrapping subscriptions as an API means self-hosting; magpie is a local GUI that runs the real claude binary on your Claude subscription
claude-code-router(ccrdesk.top)Open-source CLI / desktop2025-0238k stars, +7 in the last 105 days; homepage not in top 1MStarted out serving only Claude Code, and growth stalled
new-api(newapi.ai)Open-source self-hosted gateway2023-1152K starsFor redistribution through relay sites; magpie is a personal local tool
LiteLLM(litellm.ai)Open-source enterprise gateway2023-0763k stars; Tranco 72,912Needs YAML config, doesn't manage agent configs, and doesn't reuse subscriptions
OmniRoute(omniroute.online)Open-source gateway2026-0279k stars; Tranco 524kLeads with a free model pool
9router(9router.com)Open source2026-0132k stars; Tranco 554kSame positioning: "free, multi-subscription"
free-claude-codeOpen source2026-0168k stars, +1,930 in the last 7 daysLeads with "use Claude Code for free", a deeper gray-area play
AstrLink(astrlink.com)Open-source local gateway2026-09-22548 stars; homepage not on the chartsNearly identical positioning, but no author influence
OpenRouterCommercial cloud API2023Tranco 3,788Pay-as-you-go, can't reuse subscriptions you already bought, and doesn't change agent configs

(Stars come from the github repo_profile, 11-11; Tranco comes from the traffic database, 11-10.)

4. Growth tactics (with evidence)

  1. The author published it on X himself, and Chinese KOLs reposted it (confirmed, main channel). Details are in the GitHub report: Laoguai, LinearUncle, Baoyu, wquguru and others. When November yetone answered "what is magpie", he pasted the usemagpie.ai link directly (x.com/yetone/status/2118369235361796567,11-05; 2119552455214284890,11-08), sending traffic to the official site rather than GitHub.
  2. The README points downloads and docs to the official site (confirmed). The Download and Docs links at the top of the README, the install script, and the Docker docs all live on usemagpie.ai; the Chinese README points to /zh/ and /docs/zh/. So GitHub star traffic converts directly into visits to the official site.
  3. Return visits built into the app (confirmed, from code). Auto-update, the partner list, icon proxying, and plugin stats all keep every installed copy hitting this domain. This is one of the main drivers of its Tranco ranking.
  4. SEO and AI search (layout confirmed, results unverified). 116 doc pages in four languages, llms.txt, Bing webmaster verification, IndexNow. Third-party pages such as "Magpie vs CC Switch" (aihubmix blog), ai-tldr.dev, SkillsLLM, the SourceForge mirror, and myaiexp send search traffic to the official site.
  5. Relay-site and model-vendor integration docs (confirmed). Aiberm has a "Magpie Setup" doc (aiberm.com/docs/en/magpie/), and API易 and others have similar pages. Partners have a reason to funnel traffic to it.
  6. Paid advertising: none found. The official site is the one selling ad space, not the one buying it.

5. Where the money comes from: in-app and website ad slots sold monthly (new finding, from repo commit history)

  • 2026-10-08 commit: the listing page now puts Partners at the very top, ahead of Subscriptions, with a heading stating they sponsor magpie. The partner list comes from usemagpie.ai/api/partners, "so a paid listing changes with a deploy, not a release" (the commit message, verbatim).
  • 10-10: partner sites and key links all go through usemagpie.ai/go redirects, which count clicks, and fetches of the partner list are counted too. The app reports, daily, how often each partner is shown, opened, and added (privacy section of the README).
  • Ad slots are sold by the month, with start and end dates in the commits. In-app: APIKEY.FAN through 11-24, WandAPI through 11-25, Sidrune AI and FastAIToken both 10-26 to 11-26, plus CoreCode and Kimi Code. On the official site "Sponsored by" and the README: APINEBULA, Zero Token (from 10-16), Kimi (10-23), APIKEY.FAN (10-24), WandAPI (10-25), FastAIToken, SoleAPI, 鱼鱼连线, AIGoCode (10-26 to 27). Links carry aff=magpie, aff=YETONE, or invite codes (site/sponsors.js, site/partners.js).
  • The structure: the product is free and MIT-licensed open source; every moment where "you have to plug a model into your agent" becomes a customer-acquisition slot for relay sites inside the app. Relay sites pay either a commission on top-ups or a monthly fee; the amounts aren't public. In the last ten days of October, nearly ten more were added, suggesting the ad slots are selling.

6. Why it took off (website-level view)

  • The website's ranking is a result of install volume, not the cause. The app is what drove growth, and the ignition came from author yetone's influence in the Chinese developer circle on X (see the GitHub report for details).
  • Timing: people hold several subscriptions at once, such as Claude Max, ChatGPT, and Copilot, plus cheap models like DeepSeek V4, Kimi K3, and GLM-5.3. "A subscription only works in one agent, and it cuts off when the quota runs out" is a pain point people hit every day.
  • The product combines config switching, a four-protocol gateway, subscription reuse, automatic multi-account switching, and privacy redaction in one native app, and one-click migration from CC Switch. CrUX shows usemagpie.ai moving up a tier in October while ccswitch.io moved down, a hint that users are migrating.
  • Very frequent releases (dozens a day) plus auto-update. On one hand, users feel "you ask and it's delivered"; on the other, every installed copy hits the official site often, pushing its Tranco rank up faster.

7. Differentiation

Similar tools either only switch configs (CC Switch, claude-code-router) or only run a gateway (LiteLLM, new-api, CLIProxyAPI). magpie was the first to combine both with "reuse existing subscriptions and automatically switch between accounts" in one lightweight menu-bar app, and its subscription reuse runs the official CLI for real, which looks safer. That's half the reason it worked: AstrLink, launched the same day with nearly identical positioning, has only 548 stars and isn't on the charts, which suggests the ignition came from the author's resources. Differentiation gave relays something to talk about and got real users to move over from CC Switch. The website has no independent differentiation; it is the app's download site, update source, and ad inventory.

8. Visibility and copycat risk

  • Widely discussed in the Chinese developer community: 34k stars, top X accounts such as Baoyu and Laoguai, and it has been written up on Zhihu, CSDN, cnblogs, Bilibili, and YouTube. English aggregator accounts and the aihubmix comparison article are also circulating (see sources in the GitHub report). Revenue is not public. The model of "free open-source client, selling relay ad slots inside the app" has not been specifically discussed by anyone I found.
  • Copycats: plugins and merchandise built around it have already appeared (magpie-our-free-model and others; see the GitHub report). Similar tools from the same period, model-relay, antirion, and respan-gateway, each have only a few hundred stars. claude-code-router changed its description to move closer to its positioning. No sizable direct clone has been spotted.

9. What others can learn

  • The official site of an open-source tool doubles as download site, update source, and icon proxy, so install volume automatically turns into domain traffic and branded search volume.
  • Sell ad slots at the step where "the user is about to connect a new provider": the list is served from the backend and rotated monthly, clicks are counted through the company's own /go redirect, and the in-app shown/opened/added data is used to report results to advertisers. Users pay nothing, yet relay sites' customer-acquisition budgets become revenue.
  • Multilingual docs, llms.txt, and IndexNow make the product findable by search engines and AI engines alike.
  • Support one-click migration from the incumbent on day one, then get KOLs to write "switch away from X" comparison pieces.

10. Still unclear

  • How much of the Tranco rank comes from the app's background DNS / API requests versus real visits: there is no per-channel data. The top 500k on CrUX only proves real visits reached a certain scale.
  • Whether Taiwan's top 100k is a proxy exit for mainland users: that is only an inference, based on ccswitch.io showing the same distribution.
  • The price and total revenue of the ad slots, and whether Kimi paid in cash or credits.
  • If Anthropic or OpenAI tighten the terms on subscription reuse, both the core selling point and the value of the ad slots would be affected.
  • There are already 3,700 open issues and the number is still climbing; whether AI-driven auto-merges and high-frequency releases cause quality problems that hurt retention.

Sources

This article was written by AI from public data and the data we collect daily. Numbers are sourced, and inferences are labeled.