BLXBenchBLXBench UI
blxbench

Benchmark

Levels

Misc

DocsDownload blxbenchOur TestsPassSponsor / Partnership
DocsDownload blxbenchOur TestsPassSponsor / Partnership
BLXBenchBLXBench UI
blxbench

Benchmark

Levels

Misc

DocsDownload blxbenchOur TestsPassSponsor / Partnership
DocsDownload blxbenchOur TestsPassSponsor / Partnership
  1. Home
  2. Our Tests
  3. Summary Oncall
blxbench

Test fixture

Summary Oncall

Speedeasyscorer: contains_any

Latency-sensitive tasks where concise correct output matters.

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:
Healthy on-call rotations need clear runbooks and manageable alert noise.
Scorer config
{
  "expected_contains": [
    "runbooks",
    "alert noise",
    "on-call"
  ]
}
Run parameters

temperature

0

max_tokens

80

timeout (s)

120

type

scored

file

speed_easy_16.json

← PreviousSummary Release
|
Next →Summary Training

BLXBench

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

© 2026 BLXBench by bitslix.com

ProvenanceAggregated from user runs
Scope6 / 7 / 372
Latestrun_5434c2 / 7 / $0.00
TermsPrivacy