Platform

What happens between the corpus and the screen.

Anyone can return rows from a dump. The work is deciding which rows still mean something, and what else they are attached to.

01 / Insights

Raw results are noisy. These are not.

Deduplicated: The same breach arriving from several sources merges into one record rather than repeating down the page.
Dated: Anything from the last two years is marked fresh. Older records are flagged stale so age is never a guess.
Attributed: Every hit names the source it came from, so you can weigh it yourself instead of trusting a total.
Yours to take: Timeline or table view, then out as JSON, CSV, TXT, or PDF.

Result set 4 sources | 1 identity

Source	Seen	Grade
Archive dump	2019-04	stale
Combolist	2026-08	plaintext
Stealer log	2026-09	plaintext
Public index	2024-11	record

Four source rows, one deduplicated identity. Two carry a plaintext credential, so the set grades critical.

02 / Correlation

Start with one thing. See how it connects.

Enter an email, username, IP, password, phone, or name, then choose how far out to walk. Explore it as a graph or drop into the node table.

1 hop

Direct

Records that carry the identifier itself.

2 hop

Shared

Identities that share a field with those records.

3 hop

Inferred

The wider cluster the ML matcher associates.

Risk scores and severity labels ride along with each node, so the cluster tells you where to look first rather than handing you an undifferentiated web.

03 / Privacy

The account knows almost nothing about you.

Signup: A username and a password. No email address, no phone number, no real name. One CAPTCHA at registration.
Network: Tor, a VPN, or a proxy all work identically. The CAPTCHA is the only checkpoint.
Retention: Results are held for one hour so you can return to them, then deleted.
Queries: The identifier you searched is never written to a log.
Payment: Crypto only. BTC, ETH, LTC, USDT, USDC, BNB, TRX. No card and no billing name.

04 / Access

Call it from the assistant you already use.

Premium and Pro accounts carry an API key and an MCP server. Claude Desktop, Claude Code, or any MCP client can reach all 35 tools under the same tier, quota, and rate limits as the web account. Create a key in Settings, then point the client at the endpoint below.

claude_desktop_config.json

{
  "mcpServers": {
    "0xinfo": {
      "type": "http",
      "url": "https://0xinfo.cx/api/mcp",
      "headers": { "Authorization": "Bearer 0x_live_..." }
    }
  }
}

or the Claude CLI

claude mcp add --transport http 0xinfo https://0xinfo.cx/api/mcp --header "Authorization: Bearer 0x_live_..."

See it against a real identifier.

A free account shows how many records exist before you pay to open them.

Create a free account