Skip to main content
The app and the CLI use these routes. Base URL https://app.selfbench.dev. Send Authorization: Bearer $SELFBENCH_API_KEY (or X-API-Key). Create keys under Settings → API Keys; the secret is shown once. A read key may only GET. A key acts as its owner, with the owner’s workspace roles. Keys can be listed with a key but only minted or revoked from a signed-in browser, so a leaked key can’t issue more keys.

Conventions

  • Scope. Evaluation routes sit under {scope}: a repository or eval /api/orgs/{org}/repos/{owner}/{name} (an eval’s owner is evals), a benchmark /api/orgs/{org}/benchmarks/{dataset-org}/{dataset}, or a group /api/orgs/{org}/groups/{slug}. {repo} is the repository form only.
  • Tasks are named by batch and task ID, {runId}/{taskId}.
  • Configurations are named by a setting key, shared by results, summaries, and releases.
  • Generation. Routes that author or build tasks take generation: the models, sandbox, and credentials to use. Leave it out to use the managed models and sandbox, where the deployment offers them.
  • Bodies. Routes whose page lists no body take none.
  • Background work returns 202. Poll the matching GET.
  • Errors are { "error": "…" }: 400 invalid, 403 not allowed for this key, 404 not found, 409 wrong state.

Routes

Read released results without a key through the Public API.