What Is Sub2API? (And Claude Relay Service)

If you shop around AI API relay sites, you will run into the names Sub2API and Claude Relay Service. They are not relay sites. They are open-source programs that a site's operator installs to run one. This guide covers three things: what the projects say they are, which public signs show that a site runs one, and what that means for you as a user. It does not cover installing or configuring either project, and it does not recommend any site.

Facts checked against the projects' GitHub pages and Anthropic's policy pages on November 9, 2026.

1. What they are, per the READMEs

Sub2API

The README describes Sub2API as “an AI API gateway platform designed to distribute and manage API quotas from AI product subscriptions”: users reach upstream AI services through platform-generated API keys, while the platform handles authentication, billing, load balancing and request forwarding. It is published as Wei-Shaw/sub2api on GitHub under the LGPL-3.0 license, written in Go with a Vue front end on PostgreSQL and Redis, and had more than 45,000 GitHub stars when we checked. Features the README lists:

  • Multiple upstream account types (OAuth and API key)
  • API keys generated and managed per user
  • Token-level usage tracking and cost calculation
  • Account scheduling with sticky sessions, plus per-user and per-account concurrency limits
  • Configurable request and token rate limits
  • Built-in top-up payments (EasyPay, Alipay, WeChat Pay, Stripe)
  • An admin dashboard for monitoring and management

Sources: Sub2API README

Claude Relay Service (CRS)

CRS (Wei-Shaw/claude-relay-service, MIT license, Node.js and Redis) is the earlier project from the same GitHub account. Its README describes a “self-hosted Claude API relay service with multi-account management”. A banner at the top of the README now points users to the “next-generation project CRS 2.0 (sub2api)”, so in practice Sub2API is CRS's successor. CRS features the README lists:

  • Multiple upstream Claude accounts, rotated automatically
  • A separate API key for each person
  • Per-person usage statistics
  • Automatic switching to the next account when one has a problem
  • A web dashboard, plus HTTP and SOCKS5 proxy support

Sources: Claude Relay Service README

Software versus service.Neither project sells API access. A relay site is one operator's installation, usually restyled and often modified, with the operator choosing the upstream accounts, the prices and the rules. The Sub2API README says its developers have never authorized anyone to run a commercial operation on it.

2. How to tell from outside that a site runs one

These are signs anyone can see without an account, taken from the projects' open-source code and from our own crawling of relay sites. Use them to read a site, not to probe it: make a single request at most, never try to log in, and keep in mind that forks, white-labeling and reverse proxies can change or hide any of them.

Sub2API

An inline window.__APP_CONFIG__ script in the page HTML

The Sub2API server injects its public settings into the page it serves as window.__APP_CONFIG__. If you view the source of the site's front page and see it, the front end is Sub2API's (or a fork of it).

Sources: backend/internal/web/embed_on.go

An anonymous public-settings endpoint at /api/v1/settings/public

It returns the site's public configuration as JSON without logging in, and the default site name in that configuration is “Sub2API” unless the operator renamed it. It is rate-limited per IP address, so one request is plenty.

Sources: routes/auth.go and service/setting_public.go

An anonymous price list at /api/v1/model-plaza

Upstream, this public endpoint lists groups, the models in each group with prices, and the official reference price next to them. It is open to anonymous visitors unless the operator switches on login-required. Forks often rename it: in our own crawls, one fork serves the same kind of data under a marketplace-style path, so the front end's JavaScript bundle is where the real route name shows up.

Sources: routes/model_plaza.go

A key-less call to the gateway answers 401 with the code API_KEY_REQUIRED

Sub2API's API-key middleware answers a request with no key with an error whose code is API_KEY_REQUIRED. Seeing that code on a path like /v1/models is a strong hint.

Sources: middleware/api_key_auth.go

Browser storage keys that start with sub2api_

The front end keeps some state under keys such as sub2api_login_agreement_consent. They show up in your browser's developer tools under local storage on the login or register page.

Sources: frontend/src/views/auth/LoginView.vue

/api/status returns 404

Many relay sites run New API, a different open-source gateway, which answers /api/status with JSON. A 404 there while the signs above are present is a good reason not to assume “no public data”: Sub2API has no such route in its code, and the public data lives at the endpoints above instead. In our crawl notes, checking only for New API wrongly ruled out several sites that publish prices this way.

Source: our own crawl notes, not a project document.

Claude Relay Service

An admin front end under /admin-next/

CRS serves its newer admin single-page app under /admin-next/ (a request to /admin-next redirects to /admin-next/). The README's demo link uses the same /admin-next/login path. You can recognize it from the redirect and the page it loads; there is no reason to try to log in.

Sources: src/app.js

Several alias prefixes on one host: /api, /claude, /openai, /gemini

The same server mounts its Claude-compatible routes under both /api and /claude, and adds /openai and /gemini prefixes for the other providers it supports. A relay whose documentation lists those prefixes side by side is a likely CRS.

Sources: src/app.js

What a match does and doesn't tell you

It identifies the software, which helps you read the rest of the site: the price list's group names often hint at what kind of upstream sits behind them (we have seen names that point to Kiro or to subscription plans), and one more thing to check when you compare prices is whether a listed price already includes the group multiplier. We have seen sites on the same software do it both ways. A match tells you nothing about whether the site is honest, whether it will still be running next month, or whether the model behind it is genuine.

3. Risks for users, with sources

Each risk below cites the project or the provider it comes from. We have left out anything we couldn't source.

1

Many of these sites sit on pooled subscription accounts, and Anthropic's rules forbid that

Sub2API's own README describes the product as a platform that distributes “API quotas from AI product subscriptions”, and its Important Notice says that using it “may violate the terms of service of Anthropic and other upstream providers”. Anthropic's Claude Code legal page says OAuth sign-in is for ordinary use of Claude Code and other native Anthropic apps, and that Anthropic does not permit developers “to route requests through Free, Pro, Max, or Ultra plan credentials on behalf of their users”. Its Usage Policy, with an effective date of Nov 12, 2026, adds a ban on reselling or proxying Claude “including services that route requests through consumer subscriptions”. One nuance: the software also supports plain API-key upstreams, so running Sub2API does not by itself tell you which kind of supply sits behind a site. The price list and group names often hint at it; see our channel types guide.

Sources: Sub2API README · Claude Code: Legal and compliance · Anthropic Usage Policy

2

Bans and interruptions land on the shared pool, and your key stops with it

Both READMEs say the authors take no responsibility: Sub2API's states they “assume no liability for account bans, service interruptions, data loss, or any other direct or indirect damages”, and CRS says the same about “account bans, service interruptions, or other losses”. Anthropic says it may enforce its restrictions “without prior notice” and that, if it suspects a violation, it may “warn you or throttle, limit, suspend, or terminate” access. If the accounts behind a relay are banned or throttled, the requests you send through that relay fail or slow down. The sharper risk is for anyone who hands their own Claude login or subscription to a pool: Anthropic's Consumer Terms say you may not share your account login information or make your account available to anyone else.

Sources: Sub2API README · Claude Relay Service README · Claude Code: Legal and compliance · Anthropic Consumer Terms of Service (PDF)

3

The operator is in the path of everything you send

The Claude Relay Service README makes this point about other people's relay sites: “Your conversation content is completely visible to others, forget about business secrets”. That is true of any middleman, including one built on open-source software that the operator controls end to end. Don't send secrets, customer data or private code through a relay you can't vet.

Sources: Claude Relay Service README

4

The software has had serious security bugs, and you can't see a site's version from outside

The CRS README carries a warning that v1.1.248 and below have “a critical admin authentication bypass vulnerability allowing unauthorized access to the admin panel”, and points users to v1.1.249+ or to “CRS 2.0 (sub2api)”. Sub2API has published two high-severity advisories: CVE-2026-27812 (password reset poisoning leading to account takeover, patched in 0.1.85) and CVE-2026-73079 (a path-traversal bug in the Responses routes that let an authenticated tenant relay requests to arbitrary upstream endpoints using pooled account credentials, patched in 0.1.169). Whether a given site has applied the fixes depends entirely on its operator.

Sources: Claude Relay Service README · GHSA-vc2q-289v-74g3 · GHSA-vrxq-qm4h-6hgg

5

Nobody upstream stands behind a site that runs it

The Sub2API README says its developers “have never authorized any individual or organization to conduct any form of commercial operation based on this project”, and that disputes, losses and legal liability from such activity fall on the party running it. Sites that use the software are independent operators; there is no project-level support, SLA or complaint channel to go to if something goes wrong.

Sources: Sub2API README

What to take from this

  • Treat “runs Sub2API” (or CRS) as a fact about the software, not a verdict on the site. It says nothing about where the upstream supply comes from or whether the model is the one you paid for.
  • Start with a small deposit, as with any relay, and check the model you're getting with our verification tool.
  • Never give a relay your own Claude login, session token or subscription credentials.
  • Keep secrets, customer data and private code out of requests sent through a relay you haven't vetted.

FAQ

What is Sub2API?

Sub2API is an open-source AI API gateway. Its README calls it an “AI API Gateway Platform for Subscription Quota Distribution”: software that distributes and manages API quotas from AI product subscriptions, handling authentication, billing, load balancing and request forwarding. It is software that someone installs, not a relay service you sign up to; a relay site is one operator's installation of it, often with changes.

What is Claude Relay Service (CRS)?

Claude Relay Service is the earlier open-source project by the same GitHub author, described as a self-hosted Claude API relay service with multi-account management (Node.js and Redis, MIT license). Its README now tells users to update to v1.1.249+ or to migrate to “CRS 2.0 (sub2api)”, which is the Sub2API project.

Is Sub2API the same thing as New API?

No. New API is a different open-source gateway, and many relay sites run it. The two look different from outside: New API answers /api/status with JSON and exposes a public /api/pricing, while Sub2API has no /api/status and publishes prices through its own endpoints such as /api/v1/model-plaza.

Can I tell from outside whether a relay site runs Sub2API?

Often, yes. The inline window.__APP_CONFIG__ script, the /api/v1/settings/public endpoint, the API_KEY_REQUIRED error code and sub2api_-prefixed browser storage keys are all visible without logging in. Forks and white-labeled front ends can hide or rename these, so a miss isn't proof, and a match only identifies the software. Make one gentle request at most; the public endpoints are rate-limited per IP.

Does a relay built on Sub2API pool Claude subscriptions?

The software can be pointed at subscription accounts (OAuth) or at plain API keys, and its README presents subscription quota distribution as the purpose. So some sites do pool subscriptions and some don't; the software alone can't tell you. If a relay prices Claude far below the official API, ask where the supply comes from and read our channel types guide.

Is it safe to use a relay that runs Sub2API?

The software being open source doesn't make a specific site safe. The risks above come from the operator (who sees your traffic and chose the upstream supply), from Anthropic's rules about subscription pooling, and from whether the operator keeps the software patched. This page isn't legal advice; check the terms that apply to you.

What is an AI API relayChannel types explainedPitfalls to avoidRelay verification tool