Identity across web3 platforms is fragmented by design — an address, an ENS name and a Farcaster handle are separate namespaces with no built-in join. Resolving between them is the first step of almost any real research task and is otherwise several manual lookups. Being a thin client over next.id's relation graph is both the strength and the limit: the answer is only as complete as that graph, and an identity absent from it returns nothing rather than a maybe. Worth knowing that this returns claimed and verified links, not a behavioural inference — an absence here is not evidence that two accounts are unrelated.
A single-tool identity resolver over next.id's relation graph, covering Ethereum addresses and domain names alongside Farcaster, Lens and other web3 platforms.
- get-related-address takes an identity on one platform and returns the identities related to it on the others.
- The data comes from next.id's relation server, so the links are the ones that source has verified rather than inferred from on-chain activity.
Nothing to supply. The configuration points at a relation service, which can be the public one or your own.
One command — npx -y @fengshanshan/server-relate-account