Skip to main content
Use these patterns when an integration needs linked receipts, version history, or tag-based lookup. Receipt ID in API responses is qHash.

Typed reference — reference.type: "qhash"

The ownership-basic check accepts a reference object with type: "qhash" and id set to another receipt’s ID. That creates a typed link from one receipt to another.
Reference payloads for the same target commonly hash from qhash:{targetId} in the signed content. Confirm current behavior in the ownership-basic capability reference and live API responses — do not invent receipt IDs.

Version chain — supersedes:<qHash> tag

When you update a memory or instruction receipt, NEUS can tag the new receipt with supersedes:<previousQHash>. Newer receipts point back to older ones.
Use neus_proofs_get to walk the chain and read history.

Tag prefixes for discovery

Tag prefixes help you filter related receipts. Common prefixes include subject facets (topic:, domain:) and review state (quality:draft / quality:approved). Query tagged receipts with neus_proofs_get. To attach an agent profile to a project, see Connect agent context.

Large content

Inline receipt content has a size limit (about 50,000 characters). For larger artifacts, store the canonical file elsewhere and attach a short receipt that references it (reference URL or content hash), or split content across multiple receipts only when your integration explicitly supports that pattern.

Next

Proof receipts

How receipts work on NEUS.

Reuse portable context

MCP journeys for context reuse.

Proofs read

Query receipts by tag and scope.

ownership-basic

Check inputs for content and references.
Last modified on July 13, 2026