Home / Offline verifier
Offline verifier
- What it does
- Check anything LLPRO signed against the signer public key. PASS or FAIL, nothing stored.
- Who it is for
- Agents and their builders.
- Start in one step
- Use it on this page, or ask your agent to call
receipt_verifyat llpro.ai/mcp. - What to expect
- Testing: open to try. Free. No sign-up.
New to this? Start here.
Our Trust tools sign every answer they give. This kit lets anyone check those answers without asking our server: one Python file, standard library only, no install, no network. Run it on your own machine; it prints PASS or FAIL.
Get the kit
| File | Size | SHA-256 |
|---|---|---|
| llpro_verify.py | 43,202 B | e287765ecea5bc6889014d8b283ec50f70e633f59a7d94288c941903769ec56e |
| vectors.json | 94,404 B | 134e92e7d549ecf1557095153848b7356cb60bfaabb48c55011c407c653d099d |
Check the files first (sha256sum llpro_verify.py vectors.json), read the verifier (it is short), then run every test vector:
python3 llpro_verify.py vectors vectors.json
You should see 46 vectors, 0 mismatches. The vectors include the RFC 8032 section 7.1 Ed25519 test vectors, tampered and forged signatures that must fail, and for each product a real answer, a changed answer, a wrong key and a "lying server" answer that is signed but contradicts its evidence.
Check an answer you got
Save the observation and signature you received as result.json, take the product's public key below, and run its line.
Where a line takes more files, pass what you sent too: the kit then re-checks the evidence itself, not just our signature.
| Product | Public key (Ed25519, base64) | Command |
|---|---|---|
| Transaction Audit | +1579f0etkFNPTRb93WTbKBrB+zqqm4vumbP5bahWL0= | python3 llpro_verify.py transaction-audit KEY result.json [bundle.json] |
| Spend Limits | ydDcwxiGDAQGUyEbkJK7i2dI6kqddWcJoHKzS2muabQ= | python3 llpro_verify.py spend-limits KEY result.json [request.json] |
| Witness | sfoAUuRjyvP2yXW/howd1kbWSuIDfwpj/eJuwxwg/xM= | python3 llpro_verify.py witness KEY receipts.json |
| Signed Hand-off | g81me1x+CUgpTp6n6nnCaZICiIE3SSlq87epBEIDb/g= | python3 llpro_verify.py signed-handoffs KEY record.json |
| Signed Run Records | WM0Y137VlzvpcK4ehFAdBle7LFHoxgXd7SnBGTMcqZQ= | python3 llpro_verify.py run-records KEY result.json records.json |
Any other signed LLPRO answer: python3 llpro_verify.py envelope KEY result.json. Machine-readable list: /verify.json.
How it checks
- Signatures are Ed25519 (RFC 8032), written out in the file so you can read every line. It refuses non-canonical S values, non-canonical points and small-order (weak) keys.
- Signed text is canonical JSON: sorted keys, separators
,and:, UTF-8, no ASCII escaping. This is our own canonical form, not RFC 8785; the two agree for the strings and whole numbers our tools sign. - The test vectors are signed by a published test key (
AKZx75hCF1pjlnZif4zYm2gxU3coELmH1qEGFEm9SMk=). Its seed is public on purpose so anyone can rebuild the vectors. Never trust an answer signed by it.
What a PASS does not show
A PASS shows that the named key signed exactly this answer and that its parts agree. It does not show who holds the key, that the facts behind the evidence are true, that money moved or goods arrived, or anything a product's own page says it does not show. Check the product's public key against its page and our key history before you rely on it.
For agents: this page as Markdown · JSON · llms.txt · MCP endpoint llpro.ai/mcp · agent card