Upstream account risk

The line in the footer — sharing subscription capacity may violate upstream terms, at your own risk — is true, but it leaves a seller's biggest question, will my account get banned, in the dark. This page answers it.

What it actually violates

Nearly every model vendor's terms carry the same clause: the subscription is issued to you, and you may not transfer, rent or otherwise make account access available to others. Sharing unused capacity, however cleanly engineered, lands on that clause.

This is not "grey, but nobody enforces it". It is a clear breach of terms whose enforcement varies by vendor — throttling, suspended API access, or a disabled account.

We are not going to describe this as compliant. The income is yours and so is the risk.

What the platform actually does

These are mechanisms, not promises — every one is in the code and visible in the client's own logs.

Concurrency is capped. Matching never sends more concurrent requests than the slots you declared, except for a single extra in the window where a slot has just freed and its lease has not landed yet.

You can set a daily cap. Selling stops for the day when it is reached and resets at UTC midnight. That number is yours; the platform does not guess one for you.

A 429 cools the whole account rather than retrying. The client parks that entire account until the reset upstream names, and every lane on it leaves the market meanwhile. A local quota estimator that stopped selling before the wall used to exist — it was deleted, because the cost of guessing wrong was pulling healthy lanes off the market.

When the vendor itself says the window is spent, selling stops. The client reads the vendor's own usage figures, not an estimate.

A failure is not hammered against the same account. A request that fails on one device goes to a different device rather than being retried on the same account.

Requests are built in the shape upstream requires. The client rewrites a buyer's request into that shape before forwarding it — that part is in the client's source.

What we cannot do

We cannot guarantee you will not be banned. Everything above lowers the odds; none of it removes them.

Cross-region matching is allowed by default. Your capacity can be spent by a buyer in another country — to upstream, one account appearing in several regions in a short window, which is itself a risk signal. Per-model and per-region routing policy is supported, but nothing is restricted out of the box.

Some vendors have already tightened. Anthropic has closed the path that let subscription capacity serve third-party applications; hitting that wall shows up as the whole account going dark across every model for a while. These boundaries keep moving and we get no advance warning.

We do not publish a ban rate. Not evasion — a precise figure hands an enforcement-effectiveness metric to the party tuning enforcement.

If it does happen

What we can do:

• The full call record. Every request your account served here — timestamp, model, token counts, buyer region — is on your account pages and exportable. If an appeal needs evidence, that is the evidence.
• Immediate removal. Switch selling off and every lane on that account leaves the market at once.
• Earnings are still paid. Settled income is not withheld because your upstream account ran into trouble.

What we cannot do: negotiate with the vendor on your behalf, or reimburse a suspended subscription. This is not an insurance product.

If your account ran into trouble because of selling here, write to support@asale.ai — we can at least put the records together for you.

One plain sentence

If this account is load-bearing for your work — you earn with it, a day without it costs you — do not sell on it. Use one you could lose, or do not sell at all. Writing that costs us supply, but the trade-off is yours to make.