---
title: "Get a ZK proof for a risk assessment"
method: GET
path: "/risk/proofs/{proof_id}"
tags: ["Risk"]
---

# Get a ZK proof for a risk assessment

`GET /risk/proofs/{proof_id}`

## Request

- Base URL: `https://api.mnemom.ai/v1`
- URL: `https://api.mnemom.ai/v1/risk/proofs/{proof_id}`
- Auth: HTTP bearer

Retrieve a ZK proof artifact (individual or team-coherence) by its proof id. Proofs are generated fire-and-forget after `/risk/assess` and `/risk/assess/team` and may take tens of seconds to complete. Authorization: JWT required; the proof is returned only after the risk service re-verifies that the assessment it proves belongs to the caller's billing account (resolved from the token, never the path), so a proof owned by another account (or absent) returns 404 and never another tenant's data.

## Path parameters

- `proof_id` string, required

## Response `200`

Proof row (status, artifact, metadata).

- object

## Other responses

- `400`: Bad request
- `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)