AlgoVoi publishes 16 open-source packages on PyPI and npm under Apache 2.0, plus a 28-tool MCP server on three registries. Every package is covered by the same JCS canonicalisation substrate and backed by the 8-implementation cross-validation attestation (512/512 byte-for-byte agreements across Python, TypeScript, Go, Rust, Java, PHP, .NET, Ruby). All packages are Apache 2.0. All Python and TypeScript package pairs are byte-for-byte identical on the same input.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.
Substrate layer
The substrate packages provide the foundational primitives — JCS canonicalisation, hash derivation, and PQC signing — on which every receipt format depends.algovoi-substrate / @algovoi/substrate
JCS RFC 8785 canonicalisation with AlgoVoi discipline rules: in-band
canon_version pin, type-validation pre-canonicalisation, action_ref atomic primitive, composite trust-query algorithm, audit chain primitive, and transactional action_ref lifecycle.Specified in IETF Internet-Draft draft-hopley-x402-canonicalisation-jcs-v1.algovoi-substrate-pqc / @algovoi/substrate-pqc
PQC-aware additive successor to v1. Adds ML-DSA-65 (FIPS 204 final), Falcon-1024, SLH-DSA, and hybrid schemes to the 12-row
signature_algorithm open-enum. Fail-closed verifier discipline.24/24 PQC cross-product matrix (4 producers × 6 verifiers: PQClean, @noble/post-quantum, Bouncy Castle 1.84).Verification layer
algovoi-audit-verifier / @algovoi/audit-verifier
Reference verifier for AlgoVoi selective-disclosure audit bundles. Checks per-row
content_hash, hash-chain continuity, HMAC-SHA256 bundle signature, selection criteria, and off-VM Object Lock anchor. Standalone — no AlgoVoi infrastructure trust required.103 tests (Python 65 + TypeScript 38). Hosted at verify.algovoi.co.uk.algovoi-rfc9421-verifier / @algovoi/rfc9421-verifier
Reference verifier for RFC 9421 HTTP Message Signatures and RFC 9530 Digest Fields. Ed25519 and ECDSA-P256. Byte-for-byte parity confirmed by 24/24 cross-implementation agreements.Use for: inbound request verification, proxy-chain re-validation, conformance test harnesses.
Receipt and attestation formats
Four IETF-specified receipt formats covering the full payment lifecycle — admission, settlement, cancellation, and refund. Each is canonicalised underurn:x402:canonicalisation:jcs-rfc8785-v1, backed by conformance vectors, and cross-implementation-verified byte-for-byte.
algovoi-refund-receipt / @algovoi/refund-receipt
Post-settlement refund receipt. Closed
FULL / PARTIAL / REJECTED enumeration. Composes with compliance receipts in the audit chain.IETF: draft-hopley-x402-refund-receiptalgovoi-settlement-attestation / @algovoi/settlement-attestation
Multi-chain settlement attestation. Closed
SETTLED / PENDING_FINALITY / REVERSED enumeration. settlement_chain field covers all 8 AlgoVoi chains. MiCA Art. 80 / AMLR Art. 56 compliant record structure.IETF: draft-hopley-x402-settlement-attestationalgovoi-cancellation-receipt / @algovoi/cancellation-receipt
Mandate cancellation receipt. Closed
USER_REQUESTED / MERCHANT_REQUESTED / COMPLIANCE_TERMINATED / EXPIRED enumeration. Independent cancellation_timestamp_ms and effective_from_ms for PSD2 Article 64 direct-debit revocation.IETF: draft-hopley-x402-cancellation-receiptalgovoi-composite-trust-query / @algovoi/composite-trust-query
Verifier-side composite trust query response. Top-of-stack above the four receipt formats. Closed
TRUSTED / PROVISIONAL / INSUFFICIENT_EVIDENCE / UNTRUSTED enumeration. Supports verifier-of-verifier composition.IETF: draft-hopley-x402-composite-trust-queryMCP server
algovoi-mcp / @algovoi/mcp-server
28-tool MCP server exposing AlgoVoi’s gateway to Claude Desktop, Claude Code, Cursor, Windsurf, and any MCP-compatible assistant. Tools span payments, protocol challenges (x402, MPP, AP2), A2A agent calls, recurring payment authorities, MPP subscription lifecycle, discovery, and compliance.Available on PyPI, npm, and the MCP Registry.
28 tools across 8 chains
Base, Algorand, Solana, Stellar, Hedera, Tempo, VOI, and ARC testnet. All tools work identically across both Python and TypeScript implementations.Tools:
create_payment_link, verify_payment, screen_recipient, get_compliance_attestation, generate_mpp_challenge, try_mpp_endpoint, fetch_agent_card, send_a2a_message, and 20 more.Conformance cross-validation matrix
All packages are validated against the same conformance corpus.| Layer | Result | Implementations |
|---|---|---|
| JCS RFC 8785 substrate | 512/512 byte-for-byte agreements | Python, TypeScript, Go, Rust, Java, PHP, .NET, Ruby |
| PQC substrate (ML-DSA-65) | 24/24 cross-product agreements | 4 producers × 6 verifiers (PQClean, @noble/post-quantum, Bouncy Castle 1.84) |
| RFC 9421 HTTP signatures | 24/24 cross-implementation agreements | Python, TypeScript (+ 6 external) |
| Receipt formats (all 4) | 8 vectors + invariants each | Python, TypeScript (byte-for-byte) |
IETF Internet-Drafts
Six Independent Submission Internet-Drafts, sole AlgoVoi authorship, all on the IETF Datatracker.| Draft | Package(s) |
|---|---|
draft-hopley-x402-canonicalisation-jcs-v1 | substrate, substrate-pqc |
draft-hopley-x402-compliance-receipt | substrate (compliance receipt shape) |
draft-hopley-x402-refund-receipt | refund-receipt |
draft-hopley-x402-settlement-attestation | settlement-attestation |
draft-hopley-x402-cancellation-receipt | cancellation-receipt |
draft-hopley-x402-composite-trust-query | composite-trust-query |
Adopters
Six entries in the Substrate Adopters Registry with AlgoVoi as registry editor: AlgoVoi v1, AlgoVoi v2, Supership/Crest, PEAC Protocol, Nobulex, Vauban Pay. JSON SchemaStore entry for the compliance receipt v1 schema (merged PR #5726).Acquisition
All 16 package namespaces (PyPI + npm scopes@algovoi/*), the MCP server registrations, and the 6 IETF I-D authorship positions are transferable to a buyer. See acquisition for the full transferable asset list.