pydantic-cal
Accuracy answers "is the model right?". Calibration answers "when the model says it's 90% confident, is it right 90% of the time?". An LLM can be 91% accurate and 72% miscalibrated at the same time. Every eval library on PyPI today reports the first number; none report the second. pydantic-cal is the calibration layer for pydantic-evals.
pip install pydantic-cal
import numpy as np
from pydantic_cal import ece, mce, ace, brier, brier_decomposition, TemperatureScaler
# Pull (confidence, correct) pairs from any eval run
confidences = np.array([0.95, 0.80, 0.70, 0.60, 0.45, 0.30])
correct = np.array([1, 1, 0, 1, 0, 0])
print(f"ECE = {ece(confidences, correct):.4f}") # Expected calibration error
print(f"ACE = {ace(confidences, correct):.4f}") # Adaptive (equal-mass bins)
print(f"MCE = {mce(confidences, correct):.4f}") # Worst-case bin gap
print(f"Brier= {brier(confidences, correct):.4f}") # MSE confidence vs outcome
decomp = brier_decomposition(confidences, correct, n_bins=10)
print(f"Reliability {decomp.reliability:.4f} (the calibration component)")
print(f"Resolution {decomp.resolution:.4f} (the discrimination component)")
print(f"Uncertainty {decomp.uncertainty:.4f} (intrinsic, can't be reduced)")
Fit a temperature scaler on a calibration split and recheck:
scaler = TemperatureScaler().fit(cal_confidences, cal_labels)
ece_after = ece(scaler.transform(test_confidences), test_labels)
Why this exists
Every other eval framework reports accuracy + LLM-judge variants. Surveyed nine of them - pydantic-evals, openai-evals, lm-eval-harness, deepeval, promptfoo, ragas, langfuse, langchain.evaluation, helicone - and not one ships ECE, Brier, or a reliability diagram. The gap is not subtle.
Calibration matters most when downstream code routes on confidence: human-in-the-loop fallback, conformal prediction, eval-test-suite pruning, RAG re-ranking, gating UX disclaimers. A miscalibrated 0.85 confidence routes the same as a calibrated 0.85 confidence and the system breaks silently.
Modules
| Module | What it does |
|---|---|
pydantic_cal.metrics |
ECE / MCE / ACE / Brier / reliability curves |
pydantic_cal.decomposition |
Murphy 1973 partition: reliability + resolution + uncertainty |
pydantic_cal.scalers |
Post-hoc calibration: TemperatureScaler / PlattScaler / IsotonicScaler |
pydantic_cal.bootstrap |
Bootstrap CIs + paired before/after tests |
pydantic_cal._geometry |
Internal: Fisher-Rao distance, Jensen-Shannon, Bhattacharyya, Hellinger, KL, Bregman, alpha-divergence |
The _geometry module ships textbook information-geometry primitives (Amari 1985, Chentsov 1972, Nielsen 2018, Lin 1991) on the probability simplex. It is internal because no second consumer needs it yet; it will lift to a standalone f3d1-information-geometry package on PyPI once that changes.
Pydantic-evals integration
Drops directly into dataset.evaluate(report_evaluators=[...]). Each evaluator pulls (confidence, correct) pairs out of the report via the case metrics + assertions and emits a pydantic-evals ScalarResult (ECE / MCE / ACE / Brier) or LinePlot (ReliabilityDiagram).
pip install pydantic-cal[pydantic-evals]
from pydantic_evals import Case, Dataset
from pydantic_cal.evaluators import ECE, Brier, ReliabilityDiagram
dataset = Dataset(cases=[
Case(name="q1", inputs={"prompt": "..."}, expected_output="yes",
metadata={"confidence": 0.92}),
Case(name="q2", inputs={"prompt": "..."}, expected_output="no",
metadata={"confidence": 0.51}),
# ...
])
report = await dataset.evaluate(
task_fn,
report_evaluators=[ECE(n_bins=10), Brier(), ReliabilityDiagram()],
)
By convention each evaluator reads case.metrics["confidence"] (falling back to case.metadata["confidence"]) and case.assertions["correct"] (falling back to case.expected_output == case.output). All three knobs are constructor-overridable: confidence_field=, correct_field=, correct_fn=.
What's behind pydantic_cal.crazy
A paper-locked novel ensemble-structure scaler. Imports raise ImportError until f3d1 paper 1 publishes. The public stack above is unconditionally available and does not depend on the gated method. See src/pydantic_cal/crazy/__init__.py for the unlock conditions.
Layout
pydantic-cal/
src/pydantic_cal/
__init__.py public API
metrics.py ECE / MCE / ACE / Brier / reliability curves
decomposition.py Murphy 1973 partition
scalers.py temperature / Platt / isotonic
bootstrap.py CI machinery
_geometry.py internal info-geometry kernel
crazy/ paper-locked gate
examples/smoke.py end-to-end sanity check
tests/ pytest suite
Sibling projects
The f3d1 ecosystem:
f3dx- Rust runtime your Python imports. Drop-in for openai + anthropic SDKs with native SSE streaming, agent loop with concurrent tool dispatch, OTel emission.pip install f3dx.tracewright- Trace-replay adapter forpydantic-evals. Read an f3dx or pydantic-ai logfire JSONL trace, get apydantic_evals.Dataset.pip install tracewright.f3dx.cache(bundled inf3dxsince 2026-04-30) - Content-addressable LLM response cache + replay. redb + RFC 8785 JCS + BLAKE3.pip install f3dx[cache].pip install pydantic-cal[cache]pulls this in for fixture-backed calibration dataset builds; seeexamples/cached_calibration.py.f3dx-router- In-process Rust router for LLM providers. Hedged-parallel + 429/5xx hot-swap.pip install f3dx-router.f3dx-bench- Public real-prod-traffic LLM benchmark dashboard. CF Worker + R2 + duckdb-wasm. Live.llmkit- Hosted API gateway with budget enforcement, session tracking, cost dashboards, MCP server. llmkit.sh.keyguard- Security linter for open source projects. Finds and fixes what others only report.
License
MIT.
References
- Amari, S. (1985). Differential-Geometrical Methods in Statistics. Springer.
- Chentsov, N. N. (1972). Statistical Decision Rules and Optimal Inference.
- Murphy, A. H. (1973). A New Vector Partition of the Probability Score.
- Lin, J. (1991). Divergence Measures Based on the Shannon Entropy. IEEE TIT.
- Naeini, M. P., Cooper, G. F., & Hauskrecht, M. (2015). Obtaining Well Calibrated Probabilities Using Bayesian Binning. AAAI.
- Nixon, J., et al. (2019). Measuring Calibration in Deep Learning. CVPR Workshops.
- Nielsen, F. (2018). On Information Projections, Bregman Divergences and the Centroids of Continuous Probability Distributions. ICASSP.
- Guo, C., Pleiss, G., Sun, Y., & Weinberger, K. Q. (2017). On Calibration of Modern Neural Networks. ICML.
Release files for pydantic-cal 0.0.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| pydantic_cal-0.0.4.tar.gz | 24.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pydantic_cal-0.0.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 44.9 kB
Release files / pydantic_cal-0.0.4.tar.gz
| Download URL | pydantic_cal-0.0.4.tar.gz |
|---|---|
| Size | 24.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bf8002a118a094492c3742aca686adc32c127ac080bb51427206eb59a6a481d6
|
|
BLAKE2b-256 checksum How to use checksums |
008793ab5e42f1519a5988a021913efe8367c8ae7fec2792642753e1ab8779ff
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 May 2, 2026.
Transparency logRelease files / pydantic_cal-0.0.4-py3-none-any.whl
| Download URL | pydantic_cal-0.0.4-py3-none-any.whl |
|---|---|
| Size | 20.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4b52cf7c10a4e385d95df88173052fc017bd7470c5e55e18eb0e5a2b35e1bb73
|
|
BLAKE2b-256 checksum How to use checksums |
5dec2cd144db9c74b651dc497001548dde59e1f99f588a4043ef2c6bcc68c22b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 May 2, 2026.
Transparency log