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. Reason-Constraint-Access-Token-Expiry
blxbench

Test fixture

Reason-Constraint-Access-Token-Expiry

Reasoningv2 — Resilienceeasyscorer: rubric_json_metrics

Arithmetic, symbolic steps, and structured problem solving.

How it is scored

The model receives the prompt (and optional system message). The run uses scorer rubric_json_metrics 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
Return JSON only with keys answer, evidence, constraints. A token expires exactly 1 hour after issuance. A 5-minute grace window is applied after expiry. A request arrives 59 minutes after the token was issued. Is the token valid at the time of the request?
Scorer config
{
  "metrics": {
    "accuracy": {
      "checks": [
        {
          "contains": [
            "valid"
          ]
        },
        {
          "contains": [
            "yes"
          ]
        },
        {
          "contains": [
            "grace"
          ]
        }
      ]
    },
    "evidence": {
      "checks": [
        {
          "contains": [
            "59 minutes"
          ]
        },
        {
          "contains": [
            "5-minute"
          ]
        },
        {
          "contains": [
            "1 hour"
          ]
        }
      ]
    },
    "constraint": {
      "checks": [
        {
          "contains": [
            "grace window"
          ]
        },
        {
          "contains": [
            "before expiry"
          ]
        },
        {
          "contains": [
            "not yet expired"
          ]
        }
      ]
    }
  }
}
Run parameters

temperature

0

max_tokens

500

timeout (s)

120

type

scored

file

reason-constraint-access-token-expiry.json

← PreviousReason-Ce-Even-Number
|
Next →Reason-Constraint-Api-Version-Compat

BLXBench

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

© 2026 BLXBench by bitslix.com

ProvenanceAggregated from user runs
Scope40 / 11 / 490
Latestrun_f78b01 / 459 / $18.57
TermsPrivacy