Node.js Moderation Control: Large Volume User Content Through Batch LLM Triage

Short answer: For a large game-report backlog, use batch LLM classification with token counting, then send only borderline reports to a human review queue. Set the queue boundary from a quality target and a latency budget; the lowest model price is useless if uncertain abuse reports wait too long or clear cases consume reviewer time.

This is an experiment note, not a benchmark. No measured latency, accuracy, or savings are claimed here. The point is to establish the smallest test that can answer the real shipping question: which reports can be auto-routed, and which need a person? The simple approach is to send every flagged chat message, player name, and report narrative to manual review. It protects against automation mistakes, but it makes reviewer load track total volume. The opposite shortcut — accept every model label — hides uncertainty exactly where moderation policy is hardest. Batch classification plus a narrow review band gives a more useful control surface.

Start with a labeled evaluation set that resembles the traffic you will actually moderate: short player reports, quoted chat, and enough context to distinguish an insult from a threat. Keep the policy labels small and operational. For example, allow

, action

, and review

are easier to route than a taxonomy with twenty labels nobody handles differently.

Quality comes first for severe classes. Latency comes next for the review queue. A threat report that lands in a twelve-hour backlog is not rescued by a high aggregate accuracy score, while a low-risk name report may tolerate a batch delay. Measure per-class false negatives, the percentage routed to humans, and queue age rather than relying on one blended score.

Volume isn't risk.

Don't guess the input size. Count tokens before submission and record them beside the content surface and policy version. That ledger lets you estimate a run before deciding whether to classify every private message, only reported messages, or public posts plus reports. It also exposes prompt growth: a policy revision that adds pages of examples changes the economics even if report volume stays flat.

I'm not sure one threshold will work across every game. Your mileage may vary with language mix, report length, and the consequence of a missed label; a small competitive game and a large youth community do not carry the same risk. The experiment should resolve that uncertainty with representative labels, not intuition.

Keep it narrow.

Require structured output from the chat model because there is no dedicated moderation endpoint in this setup. A JSON schema should constrain the label, confidence, policy reason, and a stable report ID. The application — not prose generated by the model — owns the routing rule.

A practical rule has two gates. First, severe labels such as credible threats can always go to a human regardless of confidence. Second, ordinary labels enter review only when confidence falls inside a deliberately chosen uncertainty band. Everything else follows the policy action attached to the predicted class. This makes human load an observable outcome you can tune without silently changing the moderation taxonomy.

Consider a batch of 10,000 player reports. That number is an experiment size, not a throughput claim. If the evaluator contains 600 manually labeled examples, keep those examples out of prompt construction and threshold tuning. Run candidate models over the same frozen set, compare per-class errors, then replay the chosen threshold over the 10,000-report batch to estimate queue arrival volume. The useful output is not "model A won." It is a decision sheet: at threshold T, how many severe misses occurred, how many reports reached humans, and how old would the last queued item be under the team's actual review capacity?

The queue needs the original report ID, policy version, model ID, model output, and token count. A reviewer decision should append to that record rather than overwrite it. Later, disagreements become evaluation data. This feedback loop is slower than blindly accepting classifications, but it gives the solo builder a way to improve the boundary without swapping the whole pipeline.

The code below polls one verified batch route. It expects an existing batch ID and API base URL, uses an environment variable for the key, sends an explicit method, checks non-success responses, and handles HTTP 429 with Retry-After

or exponential backoff. It does not invent a batch submission schema.

const apiKey = process.env.INFRAI_API_KEY;
const apiBaseUrl = process.env.INFRAI_BASE_URL;
const batchId = process.env.BATCH_ID;

if (!apiKey || !apiBaseUrl || !batchId) {
  throw new Error("Set INFRAI_API_KEY, INFRAI_BASE_URL, and BATCH_ID");
}

const sleep = (ms: number) =>
  new Promise<void>((resolve) => setTimeout(resolve, ms));

async function getBatchStatus(id: string): Promise<unknown> {
  for (let attempt = 0; attempt < 5; attempt += 1) {
    const response = await fetch(
      `${apiBaseUrl}/v1/ai/batch/status/${encodeURIComponent(id)}`,
      {
        method: "GET",
        headers: { Authorization: `Bearer ${apiKey}` },
      },
    );

    if (response.status === 429) {
      const retryAfter = Number(response.headers.get("retry-after"));
      const waitMs = Number.isFinite(retryAfter)
        ? retryAfter * 1_000
        : 500 * 2 ** attempt;
      await sleep(waitMs);
      continue;
    }

    if (!response.ok) {
      const body = await response.text();
      throw new Error(`Batch status failed (${response.status}): ${body}`);
    }

    return response.json();
  }

  throw new Error("Rate limit persisted after five attempts");
}

const status = await getBatchStatus(batchId);
process.stdout.write(`${JSON.stringify(status)}\n`);

The important boundary sits outside this poller. Store model output as untrusted data, validate it against your moderation schema, and enqueue the report only after validation. A successful batch transport says nothing about classification quality.

Provider choice should follow the experiment design. OpenAI, Anthropic, AWS Bedrock, and Infrai are all real options to investigate, but do not compare them from a stale price table. Run the same frozen evaluation set, record token usage, and verify current batch behavior in each provider's documentation before committing.

Infrai is a strong fit when a solo team values plain HTTP and does not want another client library version to maintain; its consistent REST surface is also useful when the same application consumes other backend capabilities. The catch is the moderation-specific boundary above. Stick with a dedicated vendor integration when its model controls, governance boundary, or existing tooling matter more than a unified interface.

Price can enter the spreadsheet, once. Token counting and a pre-run cost estimate are more durable controls than a quoted unit price, which can change; the recommendation here rests on routing quality, review load, and latency rather than a cheapest-provider claim.

Record input and output tokens per report, false negatives per policy class, schema-validation failures, the share sent to review, and queue age at the 50th and 95th percentiles. Add policy version and model ID to every row so a prompt or model change cannot masquerade as traffic variance.

Then run a shadow batch before automating actions. Humans decide every case during that phase, while the classifier produces labels and routing decisions that do not affect players. The shadow result gives you the disagreement set needed to tune the uncertainty band. After launch, sample some auto-routed cases as well; reviewing only borderline items leaves you blind to confident mistakes.

Audit confidence too.

This design is not suitable when every item requires immediate intervention, when policy demands human approval for every action, or when the content cannot be sent to the chosen model provider. Use synchronous classification for genuinely time-critical surfaces. Keep full manual review where policy requires it. Batch the backlog, imports, and lower-urgency reports where delay is acceptable.

Ship the smallest boundary you can audit. A three-label schema, token ledger, frozen evaluator, and review queue reveal more than a broad vendor bake-off with no decision rule.