x402 Document Index

Documentation Index

Fetch the complete documentation index at: https://docs.algovoi.co.uk/llms.txt

Use this file to discover all available pages before exploring further.

This page is a neutral index of documents in the x402 receipt-format ecosystem. It is maintained by AlgoVoi as the author of the canonicalisation substrate (urn:x402:canonicalisation:jcs-rfc8785-v1). Inclusion is informational; absence is not normative. The index is organised three ways:

• By IETF posting status — what’s on the datatracker today.
• By author / publisher — who wrote what.
• By canonicalisation anchor — which documents share which canon pin.

Each entry links to the document’s primary surface and notes the canonicalisation discipline it anchors to.

​

Authoritative anchor

The canonicalisation discipline this ecosystem converges on is specified in:

• IETF Internet-Draft: draft-hopley-x402-canonicalisation-jcs-v1 (Independent Submission, Informational; AlgoVoi sole authorship)
• URN: urn:x402:canonicalisation:jcs-rfc8785-v1
• Registration authority: Section 10.1 of the I-D above

A document is considered part of the x402 receipt-format ecosystem if it pins this URN as its canonicalisation discipline. Documents that pin a different canonicalisation discipline are out of scope of this index.

​

By IETF posting status

​

POSTED on IETF datatracker

13 IETF Internet-Drafts in x402 namespace as of 2026-05-25.

• AlgoVoi-authored: 6 (canonicalisation discipline + 5 receipt formats: compliance, settlement, cancellation, refund, composite-trust-query)
• Vauban-authored: 6 (STARK receipts + lifecycle FSM + claim algebra + Starknet anchor + delegation binding + PQC discipline)
• Sato/Soos-authored: 1 (MJWT, broader agentic-AI authorisation scope)

​

Canonicalisation anchor coverage

Of the 12 in-scope x402 receipt-format I-Ds (excluding draft-sato-soos-mjwt):

• 7 of 12 cite urn:x402:canonicalisation:jcs-rfc8785-v1 explicitly (all 6 AlgoVoi I-Ds + draft-vauban-x402-stark-receipts)
• 5 of 12 reference “JCS canonical preimage discipline” terminology and RFC 8785 directly, without citing the URN registration registered in §10.1 of draft-hopley-x402-canonicalisation-jcs-v1 (all the post-2026-05-25 Vauban revisions: lifecycle-fsm, vpsf-algebra, starknet-anchor, delegation-binding, pqc-receipts)

The 5 non-URN-citing Vauban I-Ds use the canonicalisation discipline as published by this document index, including the schema-normalisation rules (integer-millisecond timestamps, ordered arrays as significant, in-band canon_version pin) that extend beyond RFC 8785 alone. A normative reference to draft-hopley-x402-canonicalisation-jcs-v1 or the urn:x402:canonicalisation:jcs-rfc8785-v1 URN in next revisions of those I-Ds would make the anchor citation unambiguous; this is observed as an anchor-citation gap at the time of revision below, not as a substrate fork. The substrate is uni-anchor in implementation (both AlgoVoi and Vauban encode JCS RFC 8785 with the same schema-normalisation rules) and uni-anchor in URN-registration authority (only urn:x402:canonicalisation:jcs-rfc8785-v1 is defined in this namespace). The gap is at the citation layer only.

​

Published specifications (not yet at IETF)

​

By author / publisher

​

AlgoVoi (substrate author)

​

Vauban Pay (seritalien, egoriklok)

​

Sato / Soos

​

Crest Deployment Systems LLC (Andy Salvo)

​

PEAC Protocol

​

By canonicalisation anchor

No document published in x402 namespace pins a different canonicalisation URN; the substrate is uni-anchor in URN registration as of the registry revision below. The 5 Vauban I-Ds in the second row use the discipline as encoded by draft-hopley-x402-canonicalisation-jcs-v1 (including the schema-normalisation rules extending RFC 8785 — integer-millisecond timestamps, ordered arrays as significant, in-band canon_version pin) but cite only RFC 8785 in Normative References, not the AlgoVoi-authored I-D where the discipline is registered. A normative reference to draft-hopley-x402-canonicalisation-jcs-v1 or the urn:x402:canonicalisation:jcs-rfc8785-v1 URN in next revisions would make the citation unambiguous and consistent with draft-vauban-x402-stark-receipts, which already cites it explicitly. Any future document publishing a different canonicalisation URN would create a substrate fork; the substrate-author position is committed to maintaining a single canonical anchor and welcomes substrate-layer alignment proposals before any divergence.

​

Cross-reference: Adopters Registry

Parties publishing artefacts under urn:x402:canonicalisation:jcs-rfc8785-v1 are listed in the Substrate Adopters Registry. The Adopters Registry is the operational record of observed adoption; this Document Index is the bibliographic record of documents in the namespace. Both surfaces are maintained by AlgoVoi as the substrate author. Authorship of artefacts and authorship of the canonicalisation discipline are separate facts; both surfaces record both.

​

Cross-impl validation

The 8-implementation cross-validation matrix is the operational evidence of canonicalisation-discipline interop. As of 2026-05-25: Attestation: _attestations/2026-05-25-8-impl-5-format-cross-validation.md. Any new document anchoring to this URN inherits the same cross-impl validation discipline by construction; vector sets for the new document slot into the 8-impl runner suite mechanically.

​

Maintenance

This index is observed at the time of the most recent revision below. New entries are added via:

1. Pull request against chopmob-cloud/docs, editing this page (x402-document-index.mdx).
2. GitHub issue at chopmob-cloud/algovoi-jcs-conformance-vectors/issues titled x402 document index submission: {document identifier}.
3. Email to chopmob@gmail.com with subject x402 document index submission.

To qualify for inclusion, a document MUST:

• Anchor to urn:x402:canonicalisation:jcs-rfc8785-v1 in-band (via canon_version field, normative reference, or equivalent unambiguous citation).
• Be published in a publicly-citable surface (IETF datatracker, package registry, GitHub repository, hosted endpoint, or DID-anchored URL).

The index records the inclusion fact, not co-authorship of the substrate or endorsement of the document’s content.

​

Revision history