> For the complete documentation index, see [llms.txt](https://docs.layerlens.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.layerlens.ai/more-in-this-section-9/scorers-2.md).

# Scorers

In Stratix, custom scorers are **LLM-backed**: a scorer wraps a model + prompt. Use scorers when you need a custom scoring rule that doesn't fit the built-in benchmark metrics or judge surfaces.

## Create

```python
scorer = client.scorers.create(
 name="response-rubric",
 description="Rate response on factual accuracy",
 model_id=model.id,
 prompt="Rate the response on a 1-5 scale based on factual accuracy...",
)
```

## Get

```python
scorer = client.scorers.get(scorer_id)
# Returns Scorer with: id, organization_id, project_id, name, description,
# model_id, model_name, model_key, model_company, prompt, created_at, updated_at
```

## List

```python
response = client.scorers.get_many(page=1, page_size=20)
```

## Update

```python
client.scorers.update(
 scorer_id,
 name="...", # any subset of fields
 description="...",
 model_id="...",
 prompt="...",
)
```

## Delete

```python
client.scorers.delete(scorer_id)
```

## Where scorers fit

* **Custom benchmark** evaluation — pass `custom_scorer_ids=[...]` to `client.benchmarks.create_custom(...)` to apply scorers to that benchmark.
* **Trace evaluation** — judges are typically the path; scorers are used when the rubric is reusable across many benchmarks.

## Async

All methods have `AsyncStratix` equivalents.

## See also

* [Concept: Scorers](/more-in-this-section-9/scorers-2.md)
* [Stratix Premium — Scorers](/more-in-this-section-9/scorers-2.md)
* [Judges](/more-in-this-section-9/judges-2.md) — LLM-as-a-judge for trace evaluations


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.layerlens.ai/more-in-this-section-9/scorers-2.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.