---
title: "Verify a Dojo completion receipt against the published JWKS."
method: POST
path: "/dojo/receipt/verify"
tags: ["Dojo"]
---

# Verify a Dojo completion receipt against the published JWKS.

`POST /dojo/receipt/verify`

## Request

- Base URL: `https://api.mnemom.ai/v1`
- URL: `https://api.mnemom.ai/v1/dojo/receipt/verify`
- Auth: none required

PUBLIC — in-band Ed25519 verification of a posted completion-receipt JWS against the CURRENTLY published JWKS (`/v1/.well-known/jwks.json`; active + retired-window keys). Returns the structured verdict (`valid`, `payload`, `key_id`, `errors`). A bad / tampered / expired receipt is `valid:false` with the failing checks enumerated — the endpoint itself is still 200 (the verification ran). 'Verify, don't trust': the same check can be run offline against the public key. MNE-802.

## Request body

- object
  - `receipt` string, required: The receipt JWS Compact serialization to verify.

## Response `200`

The structured verification verdict (valid:true/false).

- object
  - `valid` boolean, required
  - `key_id` string, nullable, required
  - `payload` object, nullable, required: The receipt's decoded payload. On `valid:true` this is a full `DojoCompletionReceipt/v1` payload (the shape of `receiptResponseSchema.payload`). On `valid:false` it is the BEST-EFFORT decoded payload — untrusted and possibly partial or arbitrary (whatever the presented, unverified JWS decoded to) — echoed for diagnostics, so it is intentionally NOT constrained to the strict receipt shape (a tampered/bogus receipt must still surface as a 200 `valid:false`, never a 500). `null` when the JWS could not be parsed at all.
  - `errors` string[], required

## Other responses

- `400`: Bad request
- `403`: Cross-origin write refused (`cross_origin_rejected`). A state-changing request that carries the browser session cookie must come from a first-party origin (`Origin`, or failing that `Referer`) and must not send a form-style body (text/plain, urlencoded, multipart) the operation does not declare. Bearer and API-key callers are never subject to this check.
- `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)