Mainland relay sites vs overseas platforms: payment, latency, compliance

The root difference is what they are

Overseas platforms (OpenRouter, Together, Groq and similar) are mostly legitimate multi-provider access layers - they have formal relationships with model vendors, or they are the inference provider themselves.

Mainland relay sites are mostly "proxy buying and forwarding" - buying from an upstream and reselling. The business model is the spread.

That difference in positioning explains everything that follows.

Payment

This is the most concrete value a mainland site offers. If you do not have an international credit card, this step alone decides it.

Network

Overseas platforms are not necessarily slow - it depends on whether there is a good peering point between them and your network. Some have Asia-Pacific nodes and can beat a mainland relay service on latency if that service takes a long route.

Conversely, some overseas platforms are simply unreachable from mainland China without additional network arrangements.

How to decide: measure it. Do not assume "overseas is always slow" or "mainland is always fast".

Our monitoring records each site's response latency and can serve as a reference - but note that it is measured from this site's server, which may not match your own network.

Pricing models

The two systems are not directly comparable:

Overseas platform: $X per million tokens (multiply by the exchange rate for CNY)
Mainland site:     official price x rate (usually converted to CNY as well)

The trap when converting: a mainland site's "rate" is based on the official price - but different sites may quote different official prices (some use an older list, some include a surcharge). So:

The right approach is to work backwards from your actual bill, not to estimate from an advertised rate.

Concretely: run a week of real traffic, then divide the change in your balance by the tokens consumed. That number is your real unit price, and only that number is comparable.

Compliance

This is where the difference is largest, and where it is most easily ignored.

Overseas platforms: published terms of service, privacy policy and a legal entity. Data-use rules are relatively explicit (most state that data is not used for training).

Mainland sites: mostly run by an individual or a small team, with no public commitment, and no way for you to verify how logs are handled.

There is another layer: a mainland site itself depends on an overseas upstream. That puts a cross-border link inside its chain, and compliance requirements for cross-border data transfer vary enormously by scenario.

A mixed strategy

You do not have to choose. A practical combination:

Day-to-day development and testing -> mainland site (easy payment, low cost, fast)
Production work with sensitive data or compliance requirements -> overseas platform or official
Fallback -> keep one of each

In code it is the same advice as always: make base_url a configuration value so switching costs one line.

A checklist when choosing

If you are torn between the two, work through this in order:

1. Do you have an international credit card?
   No -> mainland site (this step decides it)

2. How sensitive is your data?
   Personal information or trade secrets -> overseas platform, or self-hosted

3. Can your network reach the target platform reliably?
   No -> mainland site

4. How large is your usage?
   Very large -> worth the time to convert both sides properly
   Very small -> pick whichever has the lower barrier

On "which is more trustworthy"

On accountability, overseas platforms and official channels are ahead - they have a legal entity and public commitments.

On availability and barriers, mainland sites are more practical inside China.

The two are not in conflict: the barrier decides whether you can start, and accountability decides how far you can go. Starting on a mainland site to validate quickly, then introducing more accountable channels as you scale, is a reasonable path.

Related reading

• Official API vs relay service: where the difference really lies
• Who handles your request: the data boundaries inside a relay chain
• The compliance boundary for sending corporate data through a third-party API