BLXBenchBLXBench UI
blxbench

Benchmark

Misc

DocsOur TestsPassSponsor / Partnership
DocsOur TestsPassSponsor / Partnership
BLXBenchBLXBench UI
blxbench

Benchmark

Suite

Misc

DocsOur TestsPassSponsor / Partnership
DocsOur TestsPassSponsor / Partnership
  1. Home
  2. Our Tests
  3. Summary Incident Response
blxbench

Test fixture

Summary Incident Response

Speedv1 — Nutritioneasyscorer: contains_any

Throughput and TTFT-focused generation tasks.

How it is scored

The model receives the prompt (and optional system message). The run uses scorer contains_any with the JSON configuration below. Pass/fail and partial credit are determined entirely by that scorer against the model output; no human grading.

User prompt
Summarize in 2 short bullet points:
Effective incident response needs clear ownership, fast mitigation, and postmortems with concrete actions.
Scorer config
{
  "expected_contains": [
    "ownership",
    "mitigation",
    "postmortems"
  ]
}
Run parameters

temperature

0

max_tokens

80

timeout (s)

120

type

scored

file

speed_easy_09.json

← PreviousSummary Api Design
|
Next →Summary Testing

BLXBench

Community driven leaderboardPublic benchmark runner — run in your environment, share results with the community.

© 2026 BLXBench by bitslix.com

ProvenanceAggregated from user runs
Scope43 / 11 / 490
Latestrun_7730ad / 459 / $0.00
TermsPrivacy