> ## Documentation Index
> Fetch the complete documentation index at: https://agent-compass.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Run A Service Benchmark

> Run an evaluation whose harness delegates the agent loop to an external service.

Some evaluations delegate the agent loop to an external service. In the current runtime this is a harness-level pattern: the `terminus2` harness can talk to a remote agent service through an `endpoint` parameter, while AgentCompass still owns task preparation, result normalization, summaries, and analysis.

## Prerequisites

* The external agent service is running and reachable.
* The harness accepts a service endpoint. For `terminus2`, pass it through `--harness-params` or set `harnesses.terminus2.endpoint` in the config.
* Model endpoint variables are exported.

## Command Pattern

```bash theme={null}
agentcompass run \
  terminal_bench_2 \
  terminus2 \
  your-model \
  --env <env-provider> \
  --harness-params '{"endpoint":"http://127.0.0.1:8000"}' \
  --benchmark-params '{"sample_ids":["<task-id>"]}' \
  --model-base-url "$MODEL_BASE_URL" \
  --model-api-key "$MODEL_API_KEY"
```

The endpoint can also be set once in `config/defaults.yaml` under `harnesses.terminus2.endpoint`; `service_url` and `url` are accepted as aliases.

## What To Verify

| Check            | Why                                                    |
| ---------------- | ------------------------------------------------------ |
| Service health   | Avoid confusing service failures with model failures.  |
| Timeout settings | Service benchmarks can run longer than local datasets. |
| Task ids         | Use `sample_ids` for reproducible debugging.           |
| Result schema    | Confirm service responses map into `details/*.json`.   |

## Related Pages

* [Runtime](/key_modules/runtime)
* [Results](/key_modules/results)
* [Post-analysis](/cookbooks/operations/post_analysis)