---
title: "Get proof status"
method: GET
path: "/checkpoints/{checkpoint_id}/proof"
tags: ["Verification"]
---

# Get proof status

`GET /checkpoints/{checkpoint_id}/proof`

## Request

- Base URL: `https://api.mnemom.ai/v1`
- URL: `https://api.mnemom.ai/v1/checkpoints/{checkpoint_id}/proof`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-Mnemom-Api-Key`
  - API key in cookie `mnemom_session`

Get the ZK proof status for a checkpoint: the most recent proof record's `proof_id`, `checkpoint_id`, `status`, `proof_type`, `image_id`, `proving_duration_ms`, `verified`, `verified_at` and timestamps. **Authorization:** any authenticated caller (401 without credentials); there is deliberately no ownership check. This is public verification material with no private content — it carries no agent id, reasoning, concerns, session, card or proof bytes, only whether (and how) the checkpoint's verdict was proven — the same stance as the public, redacted `GET /checkpoints/{checkpoint_id}/certificate`. A checkpoint with no proof returns 404.

## Path parameters

- `checkpoint_id` string, required

## Response `200`

Proof status and data

- ProofStatusResponse: ZK proof status and metadata for a checkpoint
  - `proof_id` string, required: Proof identifier (prf-{8 random chars})
  - `checkpoint_id` string, required: The checkpoint this proof is for
  - `status` 'pending' | 'proving' | 'completed' | 'failed' | 'deferred' | 'skipped_card_gap' | 'skipped_noise' | 'dead_letter', required: Current proof status. `pending`/`proving`/`completed`/`failed` are the core lifecycle. `deferred` = proof held pending alignment-card reconciliation (tiered proving); `skipped_card_gap`/`skipped_noise` = reconciliation concluded no proof was needed; `dead_letter` = proving abandoned after exhausting retries. Mirrors the verdict_proofs status CHECK constraint.
  - `proof_type` string, required: Proof system (e.g., sp1-stark)
  - `image_id` string, nullable: SP1 verifying-key hash of the guest program: 64 lowercase hex characters, no `0x` prefix (set when proving begins). Older proof records store a 132-character hex-of-hex form; the API returns it in this canonical form.
  - `proving_duration_ms` integer, nullable: Wall-clock proving time in milliseconds (set when completed)
  - `verified` boolean, required: Whether the proof has been verified
  - `verified_at` string, date-time, nullable: When the proof was verified (null if not yet verified)
  - `created_at` string, date-time, required: When the proof request was created
  - `updated_at` string, date-time, required: When the proof record was last updated

## Other responses

- `401`: Authentication required
- `403`: Forbidden
- `404`: Resource not found
- `429`: Rate-limit exceeded. The global per-IP limiter (100 requests/minute, applied to every `/v1/*` route) rejected this request. Back off until the window resets — `Retry-After` carries the cooldown in seconds and `X-RateLimit-Reset` the absolute reset time.
- `500`: Server error — request was well-formed but the server failed to fulfill it. Typically a downstream dependency (DB / RPC / external API) returned an unexpected error.
- `503`: An upstream dependency is currently unavailable. The request was not processed; retry after the cooldown window.

---

[API](https://skmtc.dev/mnemom/apis/mnemom-api.md) · [All operations](https://skmtc.dev/mnemom/apis/mnemom-api/llms.txt) · [OpenAPI document](https://skmtc.dev/mnemom/apis/mnemom-api/revisions/274b7a6ea182?raw)