{"ok":true,"workers":[{"wallet":"0x590dc2428870fb37625104870c709ace9dc12d24","displayName":null,"organization":null,"settledWorkCount":1,"tier":"intermediate","hasIdentity":false,"hasCredentials":false,"hasVealthCredential":false}],"total":1,"limit":25,"offset":0,"nextOffset":null,"q":null,"sort":"settledWorkCount_desc","sortExplanation":"Sorted by settledWorkCount descending (most on-chain-confirmed settlements first), tie-broken by wallet address ascending for a stable, reproducible order across pages.","filter":"settledWorkCount > 0 OR identity declared OR credentials declared OR Vealth Credential issued","filterExplanation":"Listed here: wallets with settledWorkCount > 0 (on-chain-confirmed settlement), OR a self-declared identity, OR at least one self-declared credential, OR the paid, issued Vealth Credential. That is the whole rule — nothing else is filtered, nothing with real signal is hidden. A wallet with none of the four is not listed, but its record still exists and reads free at GET /labor/worker/:wallet/record — this directory is a curated view over that same keyless data, not a gate.","profileUrlPattern":"https://vealth.net/worker/{wallet}","rawRecordUrlPattern":"https://vealth.net/labor/worker/{wallet}/record","honesty":"`settledWorkCount` and `tier` come from on-chain-confirmed settlement history. `displayName` and `organization` are self-declared by the wallet's own signature and are never verified; `hasIdentity` and `hasCredentials` are booleans over that same self-declared, unverified data (true only that SOMETHING was declared, not that it was checked). `hasVealthCredential` is a different class entirely: it means the wallet paid and proved control of itself, and Vealth issued it a credential — still no proctored exam yet, a named gap. Nothing here gates a claim or a settlement. The raw, per-wallet truth (credentials, attestations, the full identity record) is always free at GET /labor/worker/:wallet/record — no account, no key."}