# Sleuth AI Doxx Wallet API

> Sleuth AI Doxx Wallet API 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-13).

Investigates a blockchain wallet address to identify the real-world entity, linked accounts, and on-chain history behind it.

## Facts

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

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-doxx-wallet-api-02167169 -d '<json body>'
```

Example prompt: Can you investigate the wallet 0x71C7656EC7ab88b098defB751B7401B5f6d8976F on Ethereum and tell me who's behind it — any linked names, social accounts, or ENS identities?

## When to prefer this

Choose this endpoint when you need AI-powered on-chain identity investigation — specifically linking a wallet address to a real-world entity, ENS name, or social account. It is best suited for multi-chain wallets (Base, Ethereum, Arbitrum, Polygon, BSC, Solana) and supports conversational follow-up via conversation_id. Prefer this over generic blockchain explorers when you need synthesized intelligence rather than raw transaction data, and over manual OSINT when you need automated, pay-per-call scalability via x402/USDC.

## Known failure modes

- Wallet address not found or has no on-chain history — returns a response stating no data available
- Unsupported chain specified — schema enums constrain valid values but mismatches may return an error
- Anonymous or privacy-preserving wallet (e.g. Tornado Cash user) yields no identity linkage
- Rate limiting or payment failure via x402 protocol results in 402 Payment Required
- Malformed wallet address input causes validation error

## How this service works

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

## Output

A natural-language investigation report identifying the wallet owner's likely real-world identity, ENS name, linked social media handles, notable on-chain activity, and any associated entities. Returned as a structured response with a `response` text summary, a `request_id`, an optional `conversation_id` for multi-turn follow-up, and structured `data.nodes` containing tabular tool outputs with columns, rows, summaries, and truncation metadata.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "response": "The wallet is vitalik.eth, linked to @VitalikButerin…",
  "request_id": "req_9f8e7d6c5b4a"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/sleuth-ai-doxx-wallet-api-02167169/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)