walletlink.social

Resolve one or more Ethereum addresses to the social identities attached to them: X handle, Farcaster account, ENS name, Lens profile, GitHub account. COST: one match credit per address that resolves to an X handle or a Farcaster account. An address that resolves to nothing is free, and so is one carrying only an ENS name, a Lens profile or a GitHub account. Up to 50 addresses per call on the def

Find the wallets in the index attested to an X account. The reverse of resolving an address. Only wallets whose recorded sources are all attested come back, so a wallet whose attested link sits beside a correlated source is left out; resolving that address still shows it, labeled. Needs a key that belongs to an account: a key bought with USDC alone gets ACCOUNT_REQUIRED. COST: one match credit pe

Find the wallets in the index attested to a Farcaster account. Only wallets whose recorded sources are all attested come back, so a wallet whose Farcaster verification sits beside a correlated source is left out; resolving that address still shows it, labeled. Needs a key that belongs to an account: a key bought with USDC alone gets ACCOUNT_REQUIRED. COST: one match credit per wallet returned, an

How much of the index carries each identity type. Use it to judge whether a lookup is worth making before making it. COST: free on both meters. It resolves no wallet and consumes no rate limit. A key whose balance is zero can still read the free endpoints; the balance and coverage reads keep answering at zero, and only a call that could bill refuses with NO_CREDITS. addresses_with_an_identity ov

How many match credits the configured key has left, and how much of the request allowance it has used. COST: free on both meters. Call it before a reverse lookup, which can spend up to 100 credits in one go. matches_available is the meter that stops a metered call: at zero, the resolve and reverse tools refuse, while this tool and the coverage tool keep answering, so a drained key can always rea

Submit a list of addresses as a background job. A job runs a deeper scan than the resolve tool: an address the index has not checked, or holds only stale answers for, is resolved against live sources, so a job can find identities the resolve tool reports as never seen. Use it for lists larger than one resolve call, or when misses are worth re-checking. COST: billed on matches exactly like resolvi

Progress and results for a job submitted with walletlink_submit_job. While the job runs it reports processed counts; on completion it reports the resolved records and what was billed. COST: free on both meters, so a drained key can still collect results it already paid for. A field that is absent was not measured. Absent is not false: a missing reachability means the handle was not checked, never

A dry run over a list of addresses: how many are in the index, how many were checked and found bare, how many have never been seen, and the band a resolve would bill inside. Counts only, no identities. Use it to decide whether a list is worth resolving, and which tool to spend on. COST: free on the match meter, always, even at zero balance. It weighs the rate window exactly like resolving the sam