Docs · SDK

CLI

liorith-verify. Four commands: one for setup, three for finding out why an integration is not doing what you expected.

keygen

npx liorith-verify keygen

Prints an Ed25519 pair with instructions: the private key as a ready-made environment line, the public key as a PEM to paste into the admin panel under your site.

The pair is generated locally and never sent anywhere. Run it again to rotate — the old key stops working the moment you replace the public key in the panel.

check

npx liorith-verify check --domain demo.liorith.net

--domainrequiredstringThe domain to look up.

--apistringAPI base URL, for a non-production registry.

Prints the full lookup response as JSON. Needs no key.

sign

npx liorith-verify sign \
  --site your-site-id \
  --host your-domain.example \
  --key "$(cat private.pem)"

--siterequiredstringSite id to sign for.

--hostrequiredstringHost to claim.

--keystringEd25519 private key PEM (v2).

--secretstringShared secret for the legacy HMAC scheme (v1).

--registrystringSite base URL the proof URL points at.

Prints a proof URL and stops there. Useful when you want to open the result in a browser — but the URL is good for two minutes and one verification.

verify

npx liorith-verify verify \
  --site your-site-id \
  --host your-domain.example \
  --key "$(cat private.pem)"

Signs and immediately verifies, printing the result as JSON. This is the command that answers “is my setup correct?” — it exercises the key pair, the site id and the host binding in one go.

The proof URL goes to stderr, the result to stdout, so you can pipe the JSON without losing the link.

no_secret means no public key is stored for the site. host_mismatch means the key and site are right but the host is not registered for them. Both are configuration, not code.