Records anyone can check, from the field onwards.
Turn on ledger records once, and every field record and fact your company confirms goes on the ledger as a fingerprint. Anyone you share a record with checks that it is unchanged, without an account and without A-REX.
In figures
- DailyRecords anchored on the ledgerOnce a day per company, in the platform’s code.
- 3Ledgers that receive the anchor: Bitcoin, your EVM ledger and HederaHedera when it is turned on (its test network during the alpha).
- 0.33 sTo re-check 18 records without A-REXverify-facts.mjs on a local ledger node; a public node adds network time.
Counted in the platform’s code or measured on the A-REX test environment, November 2026. Not customer results.
The problem
From "trust us" to "check it yourself"
A record is only as good as the proof that nobody changed it.
Only fingerprints go on the ledger: values, names, places, documents and amounts stay in your company's records.
Changed after the fact
A date or a dose in a field register can be edited quietly, and a reader cannot tell.
Our word against yours
A buyer has to trust the system that shows the record, or ask for the paper.
Proof that exposes the data
Publishing records to prove them would show names, plots and prices to everyone.
What it does
Turn it on once
One proposal your owner approves turns ledger records on for the company. From then on, what your people confirm goes on the ledger by itself.
Read the full moduleCheck it without us
A free script, verify-facts.mjs, checks a file of records or an evidence pack against the ledger on any computer with Node.js, with nothing to install and no account.
Read the full moduleFingerprints on public ledgers
Each day's fingerprint of your records is also published on public ledgers, Bitcoin and Hedera among them, so the proof outlives any one service.
Read the full moduleCorrections leave a trace
A recorded fact is never edited: it is voided and recorded again, and both stay readable. A field record changed after its anchor waits for the next one.
Read the full moduleHow it works
From a record in the field to a match anyone can see.
Your people record
Field work and facts, confirmed by a person of your company.
The fingerprint goes on the ledger
Facts one by one; field work in tonight's anchor.
You share the record
With a buyer, a verifier or an auditor, in a report or an evidence pack.
Anyone checks it
In the console, or with the script, against the ledger itself.
Field work, kept as it was
A spraying, a fertiliser application, a harvest: recorded on the day, in the day's anchor that night.
- A field record changed after its anchor goes back to waiting.
- The check says the day it matches, never more than that.
- Your buyers check it without an account.
What goes where
The ledger holds proof, not data. Everything a fingerprint stands for stays in your company's records.
| Part | In practice |
|---|---|
| On the ledger | A fingerprint per fact, and one fingerprint per day for each kind of field work: a value that proves a record without revealing it. |
| Never on the ledger | The values themselves, names, plots and their geometry, documents, personal data and amounts of money. |
| When | Facts one by one; field work in one anchor a day, shortly after midnight in your company's time zone. |
| What a match shows | That the record existed unchanged on that day, recorded by your company. It does not show that the work happened this way. |
| The script | verify-facts.mjs, with an evidence pack or a file of records. It runs on Node.js 20 or later, with nothing to install. |
| In the alpha | Records go on test ledgers while the production service is prepared, and Hedera runs on its test network. |
Who uses it
The owner turns it on; everyone you share with can check.
Owner
Approves turning ledger records on, with a second factor.
Operator
Records field work and facts as usual; nothing more to do.
Buyer
Checks that the records behind a delivery match the ledger.
Verifier or auditor
Runs the script on an evidence pack, with no account.
Anyone checks that a record was included, with no A-REX service and no software from the issuer.
Resources
The guides, the open standard and the details behind every screen.
- GuideRecords anyone can checkOnce a day, a fingerprint of what your company recorded is published on public ledgers. Anyone can then check that a report, a document or your audit trail has not changed since that day, without A-REX.
- ModuleRecords on the ledger in fullEvery module in full: what it records, who approves and what it checks.
- GuideHelp centerGuides for every screen of the console
- StandardThe A-REX standardThe open standard, kept by the A-REX Foundation
- DevelopersDevelopersAPI, events, signed webhooks and the MCP server
- TrustSecurity and trustApprovals, keys, personal data and agents
Let your buyers check your records themselves.
Tell us which records your buyers ask about. We will turn ledger records on in a sandbox and show you a match, from the field to the script.
Explore more