HashAnchor Guide

HashAnchor turns machine records into portable evidence. Records are batched into a Merkle tree, the root is anchored on a public chain, and each record gets a receipt anyone can verify — offline, and without trusting TLAY.

Start here#

Thousands of records share one on-chain root. Each record's receipt carries the few sibling hashes that lead from it to that root.

Quick Start →Get a free key, anchor a record, and verify its receipt three ways.How anchoring works →The lifecycle, Merkle batching, and every field in a receipt.Verifying receipts →The three checks, how much each trusts, and what a receipt does and does not prove.Settling device payments →Relay authorizations a device already signed to x402 settlement.API and SDK reference →Every method and endpoint, auth, errors, limits and installation.Status and FAQ →What ships, who runs what, and the questions people ask first.

Two jobs, one SDK#

The client SDK does two different things. They share a package and nothing else.

	Anchor and verify machine data	Settle device-signed payments
You want to	prove a record existed, unchanged, at a point in time	relay a payment authorization a device already signed
Auth	API key	no API key
Timing	asynchronous — minutes	synchronous — outcome in the response
You get	a receipt with a Merkle proof and an anchor transaction	one settlement outcome per proof

Note

The client SDK is Apache-2.0 at github.com/TLAY-IO/hashanchor. The server is a hosted service operated by TLAY, with a self-serve free plan. Verifying a receipt needs neither: the proof check runs offline and the anchor is a public transaction.