The calibration record

The calibration endpoint is a signed-or-explicitly-untrusted population and maturity disclosure. Calibration v0 is not an outcome score or public track record.

How do I pull the calibration record?

One free, unauthenticated GET returns a privacy-bucketed count of evaluated mature registrations, forward_outcomes.status=accumulating, and honesty=insufficient_history. It does not publish Brier, base-rate, survived/deflated or hit-rate results.

$ curl -s https://api.alphaassay.com/v1/public/calibration

What does the signed snapshot establish?

Calibration data is served only when the current snapshot has a valid signature. If that condition is not met, the endpoint returns signed:false plus a stale/reason state and no calibration payload. The signature authenticates the bytes under the named key; it does not independently timestamp them or prevent an operator from publishing a different later snapshot. Retain snapshots to compare the record over time. Verdict grades are demote-only in the application contract. The full reasoning: how we grade ourselves.

How should I read the record?

Read the bucket as a population disclosure, accumulating as work still in progress, and insufficient_history as an explicit refusal to infer reliability before a separately defined mature-outcome metric exists. Retained snapshots can prove what state was published, but cannot supply a metric that the payload does not contain.