An address label is metadata about a particular address on a particular chain. It can help explain what a reader is looking at, but it does not by itself establish who controls the address or whether interacting with it is appropriate.
AirnodeHub’s Kleros Scout listing provides a concrete example. Its document describes an operator-run, read-only view of current Scout registry metadata, including curation state. It explicitly excludes safety scores and Kleros endorsement.
Keep the chain and address together
The getAddressTags operation requires an integer chainId and an EVM address. The chain identifies the contract being described. It is not automatically the chain hosting the registry, which the document identifies as Gnosis, chain 100.
For an illustrative Ethereum-contract lookup, the inputs would identify Ethereum and that contract’s existing address. A matching-looking address on another chain is a different lookup. This describes the documented input contract; it does not claim that any particular label was returned.
Retain state and freshness
The documented response structure includes items, nextCursor and indexedBlock. Preserve the returned curation state with the label, rather than copying only a convenient name into a wallet screen or article.
If another page is needed, the document says to pass nextCursor unchanged. It also warns that pages come from a moving index, not an immutable snapshot. An empty page or an absent label should therefore be reported within that query’s scope, without turning missing metadata into a conclusion about an address.
Separate the registry from the relay
The listing is an API3-operated third-party integration using an indexer and local adapter. Its signature attests to the indexed response served by that Airnode, not to a Kleros ruling or upstream endorsement. Verification binds a signer, request, time and response; it is not a factual-truth or investment-safety guarantee.
The listing and its operations were Free when checked on October 13, 2026. That observation is not a permanent pricing promise. The workflow is a documented example, with no address query, wallet connection or asset movement performed.