The Harbor Crew · by WorkMap
Public read-only report

Check several addresses at once

One report checks up to five EVM addresses at a reference block on Ethereum, Base, Arbitrum One and Polygon. It reports EIP-7702 delegation indicators, code size, SHA-256 fingerprints and explorer links.

0.02 USDC per batchNative USDC on BaseUp to 5 addresses4 networks
Try one free network check

Enter one public EVM address to inspect its current code indicator on a single network. No wallet connection or payment. The four-network report adds recorded block heights, code sizes and SHA-256 fingerprints.

Choose one network. This preview reads public code only and does not inspect balances or transaction history.


        
Need a four-network snapshot? Continue to the paid report.

      

      

        

          
          
          Do not paste seed phrases or private keys. The list is processed to produce the report and sent to public RPCs; it is not stored in the service database. The payment transaction will be public on Base.
        

        

          
          
        

        

          
          
        

      

      
Payment comes from your wallet; next you'll sign a free authorization tied to this batch.

      

      
Before confirming, check Base, native USDC, the amount and recipient in your wallet. Your wallet needs a small amount of ETH on Base for network fees. The later signature does not send funds; it binds the payment to these addresses. Confirmed transfers are irreversible. If an RPC fails, keep the hash and retry recovery without paying again.

      
Payment recipient: 0x556cA364EA9512fca9E501349630EfF15f16B9a9 · Native USDC contract: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913

      
The report describes public data. An indicator, code or hash does not prove malicious intent, wallet ownership or authority to recover assets.

      

        Agent API integration
        
The endpoint returns the same JSON report for a batch of 1–5 addresses. Pay first from a Base wallet you control; the service never asks for or receives private keys.

        
1. Send the payment directly

        
Transfer exactly 0.02 native USDC on Base to the recipient and contract shown above. Keep the transaction hash. You need ETH on Base for the network fee.

        
2. Sign the batch with the paying wallet

        
Sign this message with personal_sign. Replace the placeholders; lowercase the hash and addresses and sort the addresses alphabetically, separated by commas. Use LF line breaks with no extra spaces or lines:

        
The Harbor Crew Cross-Chain Report
version=1
chainId=8453
tx=<payment transaction hash>
addresses=<lowercase addresses sorted alphabetically and separated by commas>

        
3. Send the request

        
POST /api/v1/cross-chain-report
Content-Type: application/json

{
  "txHash": "0x<32-byte transaction hash>",
  "payerAddress": "0x<address that sent the payment>",
  "addresses": ["0x<public EVM address>"],
  "signature": "0x<65-byte personal_sign signature>"
}

        
An HTTP 202 response means the payment is still confirming. Retry with the same hash and batch; do not pay again. A payment cannot be reused for a different batch. The final response includes the JSON report. See the OpenAPI schema.

      

    

    
← Back to The Harbor Crew