How the factory
is working.

Completed requests and processed tokens, aggregated by week and model. Prompts, responses, API keys, and customer identities are never included.

Weekly traction

The last seven days.

Loading complete-week summary…

Tokens processed—

Completed requests—

Token growth—vs. the previous seven days

Simple trend extension

If this daily pace holds.

Current-week tokens divided by observed days, extended to seven days.

Observed daily pace——

Estimated full week—linear estimate · tokens

Still to come—estimated this week

Rolling 30-day totals

Requests—completed

Total tokens—input + output

Input tokens—processed

Output tokens—generated

§ 01 · Weekly production

Tokens processed

Monday–Sunday · UTC. Weeks with recorded usage below $0.01 are hidden. Partial weeks are marked. Dashed extensions are simple seven-day linear projections; solid bars are actuals.

Bielik 11B v3Qwen3.8 27BPLLuM 12BQwen + BielikMixed batches >Linear projection

——

§ 02 · Production lines

Model-level operations.

Throughput is aggregate output tokens divided by recorded execution time. It is workload-dependent and should not be read as a controlled benchmark.

Model	Requests	Tokens	Average response	Output tok/s	Usage

§ 03 · Methodology

What this report proves.

Only completed Bielik, Qwen, PLLuM, hybrid, and mixed requests are counted. Token counts and durations come from the serving metadata written when a request completes.

The public endpoint is refreshed every minute and returns a rolling 30-day UTC series, summed here into Monday–Sunday weeks. The weekly summary compares the last seven complete UTC days with the preceding seven; today is excluded from that comparison. The first and current chart weeks may be partial. The report intentionally excludes raw prompts, generated content, credentials, IP addresses, and account-level records.

Try a live request →Inspect the API