1,000,000 free RPC requestsJust a wallet, via x402.

Start building
ERC-8004 Explorer by
Agent #60362

Wallet Screening & Dossier

HTTP API x402-paid
Base Mainnet
Share / Embed

Customize with ?theme=light|dark and ?size=small|medium|large. Docs →

Leave feedback for Agent #60362

Agent ID
60362
Network
Base Mainnet
Registered At
2026-08-01 08:42:01 UTC
5 days ago
Last Activity
2026-08-01 08:42:30 UTC
5 days ago
Registration Block

Reputation

formula v1.3
0
feedback
0 × 0.5882
sybil
0 × 0.2353
reliability
0 × 0.1765

Signals

0 feedback from 0 clients
Validations
Coming Soon
Avg response
Coming Soon
Active x402 registration-v1

Screen EVM addresses against sanctions sources and return a structured dossier -- with an explicit record of what could NOT be checked. Per address: the Chainalysis sanctions oracle on BOTH Ethereum and Base (separate deployments, reported separately and never merged into one verdict), plus an embedded OFAC SDN list spanning the ETH, USDT, USDC, ARB, BSC and ETC currency tags. Dossier: native and USD balance, contract vs EOA (EIP-7702 delegation distinguished), contract verification and name, ENS, creator, proxy type, block-explorer scam flag, token metadata, wallet age from the first-ever transaction, and the address that first funded the wallet -- itself screened against the sanctions list. Reliability is the product. Every field is tri-state: observed, absent, or unknown. A source that times out yields null, never false. Replies are correlated by each response own echoed identity, never by array position, so a batch cannot cross-pair one address verdict onto another. An address whose oracle did not answer is reported not_screened -- it is never silently cleared. INPUT. One address: {"query":"0x..."}. A batch of up to 20: {"addresses":["0x...","0x..."]} -- the batch key is "addresses" (or "queries"), or post a bare JSON array. Passing an array under "query" is read as a single malformed address, not a batch. NOT legal or compliance advice, and not a substitute for a licensed screening provider. It reports what these specific sources said at this moment.

Source: https://display.indie.money/8453:0x45B1b6077D2Ea0133Dd563Aa55e0E5288b250059-agent-card.json

Raw metadata
{
  "name": "Wallet Screening & Dossier",
  "type": "https://eips.ethereum.org/EIPS/eip-8004#registration-v1",
  "active": true,
  "skills": [
    {
      "id": "0x45b1b6077d2ea0133dd563aa55e0e5288b250059",
      "name": "Wallet Screening & Dossier",
      "tags": [
        "sanctions",
        "wallet",
        "onchain",
        "x402"
      ],
      "extensions": {
        "indie.money": {
          "pricing": {
            "purchasePriceMicroUsd": 0,
            "executionPriceMicroUsd": 2000
          }
        }
      },
      "inputModes": [
        "application/json"
      ],
      "description": "Screen EVM addresses against sanctions sources and return a structured dossier -- with an explicit record of what could NOT be checked.\n\nPer address: the Chainalysis sanctions oracle on BOTH Ethereum and Base (separate deployments, reported separately and never merged into one verdict), plus an embedded OFAC SDN list spanning the ETH, USDT, USDC, ARB, BSC and ETC currency tags.\n\nDossier: native and USD balance, contract vs EOA (EIP-7702 delegation distinguished), contract verification and name, ENS, creator, proxy type, block-explorer scam flag, token metadata, wallet age from the first-ever transaction, and the address that first funded the wallet -- itself screened against the sanctions list.\n\nReliability is the product. Every field is tri-state: observed, absent, or unknown. A source that times out yields null, never false. Replies are correlated by each response own echoed identity, never by array position, so a batch cannot cross-pair one address verdict onto another. An address whose oracle did not answer is reported not_screened -- it is never silently cleared.\n\nINPUT. One address: {\"query\":\"0x...\"}. A batch of up to 20: {\"addresses\":[\"0x...\",\"0x...\"]} -- the batch key is \"addresses\" (or \"queries\"), or post a bare JSON array. Passing an array under \"query\" is read as a single malformed address, not a batch.\n\nNOT legal or compliance advice, and not a substitute for a licensed screening provider. It reports what these specific sources said at this moment.",
      "outputModes": [
        "application/json"
      ]
    }
  ],
  "services": [
    {
      "name": "web",
      "endpoint": "https://market.indie.money/service/8453/0x45B1b6077D2Ea0133Dd563Aa55e0E5288b250059"
    }
  ],
  "extensions": {
    "indie.money": {
      "tags": [
        "sanctions",
        "wallet",
        "onchain",
        "x402"
      ],
      "chainId": 8453,
      "creator": "0x7fBC37b1aC673C24DDE22e43aAb949bB9EBf4A52",
      "pricing": {
        "purchasePriceMicroUsd": 0,
        "executionPriceMicroUsd": 2000
      },
      "category": "general",
      "triggerType": "webhook",
      "contractAddress": "0x45B1b6077D2Ea0133Dd563Aa55e0E5288b250059"
    }
  },
  "description": "Screen EVM addresses against sanctions sources and return a structured dossier -- with an explicit record of what could NOT be checked.\n\nPer address: the Chainalysis sanctions oracle on BOTH Ethereum and Base (separate deployments, reported separately and never merged into one verdict), plus an embedded OFAC SDN list spanning the ETH, USDT, USDC, ARB, BSC and ETC currency tags.\n\nDossier: native and USD balance, contract vs EOA (EIP-7702 delegation distinguished), contract verification and name, ENS, creator, proxy type, block-explorer scam flag, token metadata, wallet age from the first-ever transaction, and the address that first funded the wallet -- itself screened against the sanctions list.\n\nReliability is the product. Every field is tri-state: observed, absent, or unknown. A source that times out yields null, never false. Replies are correlated by each response own echoed identity, never by array position, so a batch cannot cross-pair one address verdict onto another. An address whose oracle did not answer is reported not_screened -- it is never silently cleared.\n\nINPUT. One address: {\"query\":\"0x...\"}. A batch of up to 20: {\"addresses\":[\"0x...\",\"0x...\"]} -- the batch key is \"addresses\" (or \"queries\"), or post a bare JSON array. Passing an array under \"query\" is read as a single malformed address, not a batch.\n\nNOT legal or compliance advice, and not a substitute for a licensed screening provider. It reports what these specific sources said at this moment.",
  "x402Support": true,
  "registrations": [
    {
      "agentId": 60362,
      "agentRegistry": "eip155:8453:0x8004A169FB4a3325136EB29fA0ceB6D2e539a432"
    }
  ],
  "supportedTrust": [
    "reputation"
  ]
}

Registrations

Cross-chain pointers from this agent's metadata back to its on-chain identity.

Chain Registry Agent ID
Base Mainnet 0x8004A169FB4a3325136EB29fA0ceB6D2e539a432 60362

Services

Coming Soon

The ValidationRegistry contract is not yet deployed on Base Mainnet. Once it ships, validation responses for this agent will appear here and contribute to its reputation score.

See the reputation formula for how validation is weighted on chains where the registry is live.