AlgoVoi launches $6,000 Compliance Gate SDK and perpetual licences

2026-08-10

community · compliance · agentic-payments · x402 · licensing · self-hosted · update · web · updated

The x402 open standard answered how an AI agent pays: a server returns HTTP 402 Payment Required, the agent moves stablecoins on-chain, and a proof of payment unlocks the resource. The question that followed — how a supervisor proves years later that the payment was screened against sanctions lists, authorised under policy and settled, without trusting whoever ran the check — is the one AlgoVoi has turned into a product line. The UK-registered gateway, which began as an Algorand-native x402 wallet, has published a pricing page that states the new model in its own words: 'One time perpetual licences, not a monthly rent and not a cut of every transaction.'

The homepage headline changed with it, from 'Verifiable Agent Payments, Self-Hosted x402' to 'Agent Payments You Can Prove, Self Hosted.' The hosted rails that defined the product at launch — 60 days of testnet, KYC unlocking $1,000 of free mainnet volume, then a 0.50% take — are still live for merchants. The new catalogue is for operators who want the software inside their own perimeter instead of a vendor's cloud.

A catalogue instead of a subscription

The pricing page splits the catalogue into headline bundles and 'substrate add-ons' — individual signed primitives sold per module. Every licence buys the same posture: self-hosted with operator-held custody, air-gap capable, no per-transaction fee, and audit output that verifies with public libraries rather than AlgoVoi software.

The add-on shelf, priced from $3,000 to $6,000, supplies the signing primitives a deployment may already own pieces of.

Compliance Gate: a verdict with no customer data in it

The centrepiece of the new catalogue — and the only add-on with a dedicated product page in the current site — is Compliance Gate. The product page describes it as the same compliance gate that runs in AlgoVoi's production payment gateway, packaged as an embeddable SDK for 'agentic-commerce and crypto payments.' The mechanism is the whole point. A payer's wallet address is screened against the operator's own sanctions / PEP (politically exposed persons) / AML provider — AlgoVoi names Chainalysis, TRM, Elliptic or an internal list — and what enters the signed receipt is not the address but its hash: sha256(network:address). 'The address goes in (you have to screen it); only sha256(network:address) comes out.' The verdict is a closed ALLOW / REFER / DENY enumeration — a REFER (for example, a suspicious-activity-report obligation) is byte-distinct from a DENY — and the receipt is signed with Falcon-1024, a NIST-standardised post-quantum signature designed to stay secure against attacks from future quantum computers, at the highest security tier. Verification needs no callback and no shared infrastructure: the receipt checks out from the public key alone.

The statelessness is a deliberate regulatory choice. Because the gate is deterministic — same inputs always yield the same verdict, bound in a recomputable receipt — it accumulates no behavioural score, the kind of stateful reputation system that invites exposure under GDPR Article 22's restrictions on decisions based solely on automated profiling, and under the EU AI Act's record-keeping expectations. AlgoVoi is equally explicit about where the product's authority ends: the gate certifies the verdict and never holds sanctions data, but it does not perform the sanctions lookup itself — that remains the provider's data — and formal certification is the responsibility of the buyer and their counsel.

Why sell licences instead of taking a cut

The licensee profile these pages are written for is regulated firms — payment service providers, virtual asset service providers, exchanges, MLRO (money laundering reporting officer) teams — that must evidence a screening decision to a regulator or counterparty years after the fact, not just run the check. The EU's MiCA regulation, for instance, requires five-to-seven-year records of cryptoasset services. A statutory retention window is a poor fit for a dependency on someone else's hosted cloud, which is the problem the licence model attacks: you hold the funds and the keys, the software runs without phoning home, and evidence is produced and retained inside your own perimeter. As the pricing page puts it: 'You run the software in your own infrastructure, you hold the keys and the funds, and the evidence stays yours.'

One loose end a prospective buyer will hit before checkout: the pricing page lists the Verifiable Compliance Suite at $15,000, as shown above, while the suite's own landing page quotes $5,000 for one perpetual licence that installs and runs the whole estate. The two pages have not been reconciled.

The open substrate underneath

None of this is new plumbing. The receipts run on AlgoVoi's canonicalisation substrate, published since April: JSON is normalised under the JSON Canonicalization Scheme (RFC 8785), so an identical object always serialises to identical bytes and any implementation re-derives the same hash, then bound by the action_ref primitive — the SHA-256 of canonicalised agent_id, action_type, scope and timestamp_ms fields. The discipline is written up in AlgoVoi-authored IETF Internet-Drafts; draft-hopley-x402-canonicalisation-jcs-v1 is at revision -04 and expires in November 2026. An adopters registry on the docs site records outside parties publishing under the discipline — Supership/Crest Deployment Systems, PEAC Protocol and Nobulex among them — with conformance vectors cross-validated across independent implementations. The registry is AlgoVoi's own record of observed adoption, not an independent attestation.

GitHub activity around August 10 shows the same small team pushing on the protocol layer itself: an open offline verifier for its post-quantum 'Reseal' format, an RFC 9421 HTTP message-signature verifier, an official Python SDK for Google's A2A agent-to-agent protocol, and copies of the x402 and AP2 protocol codebases in its own organisation. The homepage now also advertises AlgoVoi's listing on the A2A protocol's partners page — a directory running to several hundred organisations, from AWS and Microsoft down to individual startups, so the listing is broad community membership rather than a selective endorsement.

The scoreboard so far

The commercial reality is young. Public adoption of the open layer is thin: the post-quantum substrate package @algovoi/substrate-pqc recorded 26 downloads on npm in the last month and 5 in the last week, and the organisation's public GitHub repositories carry a handful of stars (four, one each, out of 112 repositories). The licences are sold self-serve from a suite store, but that store is a JavaScript application that resists direct inspection, so whether every listed SKU is actually purchasable at checkout could not be confirmed from outside. The substance remains checkable: the standards work is public, byte-reproducible and independently re-implementable, even where the storefront itself resists inspection.

The argument the pricing page makes is a bet about the future: that in 2032, an auditor should be able to take a signed, categorical ALLOW receipt, recompute it from its disclosed fields with two public libraries, and conclude that an autonomous agent's payment was screened, authorised and settled — without AlgoVoi existing, without a network connection, and without trusting anyone. Whether that is worth the headline price to a regulated payment firm is the question the new pricing page puts to the market.

Source

• AlgoVoi
• Pricing page
• Compliance Gate
• A2A protocol partners
• IETF Datatracker: draft-hopley-x402-canonicalisation-jcs-v1
• Agentic payment compliance: verifiable receipts | AlgoVoi
• Compliance: UK MLRs, GDPR, AML, sanctions | AlgoVoi
• Substrate Adopters Registry - AlgoVoi Platform
• Verifiable Compliance Suite: self-hosted, post-quantum records | AlgoVoi

Source: https://www.algovoi.co.uk/