# Sleuth AI Find Wallet

> Sleuth AI Find Wallet is a paid API for AI agents from x402.sleuthagent.ai, paid per call via x402, $0.099/call, status unknown (last checked 2026-09-14).

Resolves a wallet address, ENS name, or identity to its on-chain owner and control details via natural language investigation.

## Facts

- Endpoint: POST https://x402.sleuthagent.ai/api/v1/find-wallet
- Price: $0.099/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/sleuth-ai-find-wallet-b07c5689
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_44LoC3gagjCr7fmrMKDsP

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability sleuth-ai-find-wallet-b07c5689 -d '<json body>'
```

Example prompt: Can you find out who controls the wallet vitalik.eth and what address it resolves to? Use Sleuth AI to investigate on-chain.

## When to prefer this

Choose this endpoint when you need on-chain identity resolution and wallet attribution — specifically when you have an ENS name or raw wallet address and want to discover who controls it. Prefer this over generic blockchain explorers when you need a natural-language summary of ownership rather than raw transaction data.

## Known failure modes

- Unknown or unresolvable address — returns no identity attribution found
- Invalid ENS name or malformed address — error response
- Payment failure — USDC on Base not confirmed, call rejected
- Rate limiting or service unavailability — HTTP 5xx
- Address with no on-chain identity signals — minimal or empty investigation result

## How this service works

Pay-per-call on-chain investigation API (x402, USDC on Base).

## Output

Returns a natural-language investigation summary describing who controls the queried wallet or ENS name, the resolved address, and any known identity attribution, along with a unique request_id for the call.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "clue": {
   "type": "string",
   "maxLength": 200,
   "minLength": 1
  },
  "chain": {
   "enum": [
    "auto",
    "base",
    "ethereum",
    "arbitrum",
    "polygon",
    "bsc",
    "robinhood",
    "solana",
    "bnb",
    "robinhoodchain"
   ],
   "type": "string",
   "default": "auto"
  },
  "conversation_id": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "response": "vitalik.eth resolves to 0xd8dA…6045, controlled by Vitalik Buterin…",
  "request_id": "req_9f8e7d6c5b4a"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/sleuth-ai-find-wallet-b07c5689/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.sleuthagent.ai](https://www.zero.xyz/host/x402.sleuthagent.ai/llms.txt)