---
title: "PQ Receipt Re-Anchor Tool"
method: POST
path: "/v1/tools/reanchor_receipt_pq"
tags: ["post-quantum", "PQC", "SLH-DSA", "ML-DSA", "FIPS 205", "FIPS 204", "dual signature", "attestation", "receipt", "re-anchor"]
---

# PQ Receipt Re-Anchor Tool

`POST /v1/tools/reanchor_receipt_pq`

## Request

- Base URL: `https://ainumbers.co`
- URL: `https://ainumbers.co/v1/tools/reanchor_receipt_pq`
- Auth: none declared

Countersigns an existing AINumbers receipt with a post-quantum SLH-DSA-SHA2-128f (FIPS 205, primary) + ML-DSA-65 (FIPS 204, secondary) dual signature, entirely client-side. The original receipt bytes, digest, and every existing proof are never touched — the tool only appends two new, independent proof-set members. Ephemeral in-browser keygen, zero-storage: no sessionStorage/localStorage/IndexedDB.

**Tool URL:** https://ainumbers.co/tools/623-pq-receipt-reanchor.html
**AP2/Policy Mandate export:** yes

## Request body

- object

## Response `200`

Successful tool execution result

- object
  - `reanchored_receipt` object: The original receipt with two appended proof-set members: SLH-DSA-SHA2-128f and ML-DSA-65

---

[API](https://skmtc.dev/ainumbers/apis/ainumbers-co-fintech-intelligence-suite.md) · [All operations](https://skmtc.dev/ainumbers/apis/ainumbers-co-fintech-intelligence-suite/llms.txt) · [OpenAPI document](https://skmtc.dev/ainumbers/apis/ainumbers-co-fintech-intelligence-suite/revisions/b462e4f5bb28?raw)