This release has been yanked by its maintainers, and will be ignored by installers, except when explicitly specified.
Consider using release 0.1.2 instead.
llama-index-evaluation-nace
Replace your LLM judge. LlamaIndex evaluators backed by Drex decision models from Nace: Drex returns probabilities, not text that has to be parsed.
Install
pip install llama-index-evaluation-nace
Set NACE_API_KEY. Optional: NACE_BASE_URL, NACE_DEFAULT_DECISION_MODEL. For OpenRouter pass base_url="https://openrouter.ai/api/v1".
The default model is drex-max-v1.1. An explicit model= is sent exactly as given; without one, NACE_DEFAULT_DECISION_MODEL is used when set, else drex-max-v1.1. If that default is a text-only model (drex-v1.5, drex-v2.0) and the request has images, drex-max-v1.1 is used for that request. OpenRouter doesn't list v1.1 yet, so there the default is the original Drex Max, nace-ai/drex-max.
Usage
from llama_index.evaluation.nace import NaceFaithfulnessEvaluator
result = NaceFaithfulnessEvaluator().evaluate(
query="When was the Eiffel Tower completed?",
response="It was completed in 1889.",
contexts=["The Eiffel Tower was completed in March 1889."],
)
print(result.passing, result.score, result.feedback) # True 0.95 P(faithful)=0.95
evaluate() is sync and works in Jupyter; aevaluate() is async. evaluate_response() reads source nodes, so the evaluators work with BatchEvalRunner.
| Evaluator | Question | score / passing |
|---|---|---|
NaceFaithfulnessEvaluator |
Is every claim supported by the context? (strict) | P(yes); passing = P >= threshold (0.5) |
NaceRelevancyEvaluator |
Does the response answer the query, in line with the context? | P(yes); same threshold |
NaceCorrectnessEvaluator |
5-level score, against reference= when given |
1 to 5; passing = score >= score_threshold (4.0) |
raise_error=True (faithfulness, relevancy) raises ValueError on a failing result, as LlamaIndex's evaluators do. The question text is editable through update_prompts({"instructions": ...}).
Results are NaceEvaluationResult: probability, probabilities (score levels), model, request_id, usage.
Images
Evaluators read ImageNode sources (image_path, base64 image, or a data: URL) and send them to Drex. The default model, drex-max-v1.1, reads images; when NACE_DEFAULT_DECISION_MODEL names a text-only model, requests with images still go to drex-max-v1.1, and an explicit text-only model= with images raises NaceImageModelError. http(s) image URLs are refused, because Drex never fetches URLs. max_images=N keeps the N highest-scored image nodes, whatever their count; without it, more than 8 images (Drex's per-request limit) raise NaceImageLimitError rather than being trimmed silently. Strict faithfulness on image-only sources tends to score lower than on text; compare probabilities rather than trusting the default cut-off.
See examples/ for runnable scripts and notebooks.
Metadata
Release files for llama-index-evaluation-nace 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| llama_index_evaluation_nace-0.1.1.tar.gz | 15.3 kB | With provenance | Details for llama_index_evaluation_nace-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| llama_index_evaluation_nace-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for llama_index_evaluation_nace-0.1.1-py3-none-any.whl |
Total release size: 37.1 kB
Release files / llama_index_evaluation_nace-0.1.1.tar.gz
| Download URL | llama_index_evaluation_nace-0.1.1.tar.gz |
|---|---|
| Size | 15.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
09b1a92778ff2be64f83dd3fe1a64eae3d95abaf90f0c0095d22c0d7a39e9fe7
|
|
BLAKE2b-256 checksum How to use checksums |
83bf5bb0aa63eee20d634f6497ad31830b809287952f7c0e63e570731d126d7e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 29, 2026.
Transparency logRelease files / llama_index_evaluation_nace-0.1.1-py3-none-any.whl
| Download URL | llama_index_evaluation_nace-0.1.1-py3-none-any.whl |
|---|---|
| Size | 21.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8dd902b6395b00e955bf6fea7877daab2baf51438811076fd13d02d3dbe6b41f
|
|
BLAKE2b-256 checksum How to use checksums |
4fa35f12926744952c20d357a66321054a7c340fdb65c209289c86472ecadfa8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 29, 2026.
Transparency logSecurity for llama-index-evaluation-nace 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for llama_index_evaluation_nace-0.1.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 29, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.