wallet_check
shallowio.vike/data · Verify this server
Everything we know about ONE address in one call: a wallet checker / address lookup. Each part is its own block: `ens` (reverse ENS name), `tags` (names attached to the address, e.g. a token's name), `labels` (per chain: entity and wallet type), `label_sources` (which source claimed what about the address, read for Ethereum; third-party providers are named provider_a to provider_e), `label_origins` (BNB Chain, Base, HyperEVM: the origins each chain's label records and what each claimed, `origin` one of third_party (provider_a), model (our heuristic, with its source, confidence (null = not scored) and tier), cross_chain (copied from the same address's label on `from_chain`) or unknown; a claim can differ from the label), `onchain` (transfer count per chain where the address is active), `code` (per chain, the code found at the address when last checked: contract, eip7702 delegated wallet, safe multisig or proxy; a chain absent means no code when checked, or not checked), `token` (name, symbol and chain when it is a token contract), `first_funder` (per chain: the earliest inbound coin and priced token transfers we hold, with sender and label; not proof of who funded the wallet), `exchanges` (per chain: the centralised exchanges it sent to and received from over 365 days, a lower bound), `hl_trader`, `hl_vault`, `hl_builder` (its Hyperliquid identity), `polymarket` (the Polymarket account at this address, its owner, and the accounts it owns), and `summary` (plain observed facts read off the blocks, never a verdict such as 'safe'). first_funder and exchanges cover every chain the address has transfers on, or only `chain`. A block missing from the answer could not be read; an empty one means we looked and found nothing. Use when the user pastes an address and asks 'whose wallet is this', 'what is this address' or 'check this wallet'; for one chain's funder or exchanges with other floors or windows, use wallet_first_funder / wallet_exchange_usage.
1 trials · measured 10 days ago
wallet_check scores 100.0/100 on Vouch's measured behaviour index, from 1 real invocation trials against io.vike/data, measured 12 Nov 2026 under methodology v0.2.0. Every measured component scored 100.
Component breakdown
| Component | Weight | Value |
|---|---|---|
| Reliability | 35% | not applicable |
| Schema integrity | 25% | 100.0 |
| Failure behaviour | 15% | not applicable |
| Latency | 15% | not applicable |
| Concurrency | 10% | not applicable |
Tool details
- Transport
- remote
- Credential class
- self-provisionable
- Input schema
- not declared
- Output schema
- not declared
- Side-effect classification
- unclassified
Score history
| Day | Score | Tier | Methodology |
|---|---|---|---|
| 2026-11-12 | 100.0 | shallow | v0.2.0 |
Probe evidence
| Probe | Outcomes |
|---|---|
| schema_integrity | pass: 1 |
Raw request/response logs are not archived yet — the outcome counts above are drawn directly from every recorded trial.
Embed this score
Available for every tool, scored or not — not a verification perk. Always links back to this page.
[](https://vouch.tools/tools/c4bb1bf9-1221-477b-aeea-74971f00aecf)