# The lab: we run the tools and the models ourselves (slim)

> One machine where open-weight models try the tools Anchor Terminal lists and answer questions about the site. What the lab does, how it's set up, and where its results go.

- Full: https://www.anchorterminal.com/benchmark/lab/index.md (~500 tokens) · this version ~380 tokens · JSON https://www.anchorterminal.com/benchmark/lab/index.json · canonical https://www.anchorterminal.com/benchmark/lab/
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-22
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

The lab is one machine we run ourselves, beside the site's server.

## What it does

- Evaluations: models asked questions that have one right answer, run the same way for every model. Open-weight models are the first. https://www.anchorterminal.com/benchmark/lab/evaluation/index.md
- Tool tests: a model is given only what a server says about its tools and writes programs to call each one, and the lab's gateway counts and times every call. What it found is on the listing, under Lab, and moves its Performance and Task success. https://www.anchorterminal.com/benchmark/index.md

## The setup

- The box: an AMD Ryzen AI Max+ 395 with 128 GB, running plain Debian, every model through llama.cpp from a build pinned by file hash.
- The cell: a program a model writes runs with no network, and what it calls goes through the lab's gateway.
- Nothing the lab reads is trusted, and the site checks the box's results one field at a time before it shows any.
- The harness is open source (Go, standard library only, MIT): https://github.com/Anchor-Terminal/anchorlab

JSON: https://www.anchorterminal.com/api/v1/lab.json and https://www.anchorterminal.com/api/v1/lab-evals.json
