Liorith Registry · Docs

Documentation

The registry answers two separate questions. Everything here follows from keeping them apart.

Two questions

Does the registry list this domain? That is a lookup. Ask /check with a domain and you get the entry it is listed under - or the fact that there is none. No key, no signature, no setup.

Does this request really come from that site? That is a proof. The site signs a short-lived token with its private key, and /verify checks the signature against the public key on file. Only this second question involves cryptography.

Mixing them up is the most common integration mistake. A registry entry records which site a domain is listed under. It never says that the link in front of you came from that site.

Start here

GuideQuickstartA domain lookup in one request, and a working proof endpoint in about ten minutes.GuideConceptsSites, domains, categories, entry states, and what the blocklist does and does not claim.ReferenceAPI referenceEvery endpoint, its parameters, its response shape, and its rate limit.ReferenceStatus codesAll values of status and result, what each one means, and how to act on it.ReferenceProof formatThe signed message, the Ed25519 signature, the replay window, and the host binding.SDKSDK & CLISign proofs, run lookups, and mount a badge from JavaScript or the command line.

Base URLs

The API and the human-readable site are separate hosts. Machine clients talk to the API; every response that has a page behind it carries the page URL in the body, so you never need to build one yourself.

Base URLstext

API   https://api.registry.liorith.net
Site  https://registry.liorith.net

There is no authentication and no API key. Every endpoint documented here is public and answers GET requests. Rate limits apply per IP and are listed with each endpoint.