The shop is a channel now. Can you query it?
A large part of the trade that used to need a forum account now happens in Telegram channels, groups and megagroups. Telepathy searches that message corpus full-text and pulls eleven kinds of indicator out of every message as it is indexed, so a wallet, an IBAN or a card BIN is a filter rather than a string you hope to spot.
What Telepathy sees
Eleven indicators, lifted from every message
Phone numbers, emails, crypto wallets, IBANs, card numbers, IPs, domains, URLs, CVEs, file hashes and channel links are extracted at index time. Nine of the eleven (crypto, email, domain, ip, cve, hash, card, phone and IBAN) are each their own query parameter; URLs and channel links are extracted and carried on every hit but are not independently filterable yet. Wallets resolve across six chains, Bitcoin through Ethereum, Litecoin, Monero, Solana and Tron, so an address matches whichever one it belongs to.
Channels, groups and megagroups
The three container types behave differently and are indexed as what they are, so you can scope a query to broadcast channels alone, or follow a handle from a channel into the group where the conversation actually happens.
Media is part of the record
Messages that carried a file are marked as such and can be isolated in one filter, which is the difference between reading an advertisement and finding the sample that was attached to it.
Sorted your way, dated precisely
Newest-first, oldest-first or by relevance, over date ranges that accept either an ISO date or date-math. Every hit carries the time we indexed it, so the age of what you are reading is on the record instead of assumed.
The indicators come out before you ask for them
Every message is read for eleven categories of indicator as it is indexed. What the message did not carry is dimmed, because this is a schema rather than a lucky example.
TELEPATHY · EXTRACTION
sample message · synthetic6 OF 11 CATEGORIES PRESENT IN THIS MESSAGE · THE REST RUN ON EVERY MESSAGE AND FOUND NOTHING HERE
Same data, same permissions, over HTTP
Everything the console shows, the API serves. Real endpoint, sample response, masked values.
GET /api/telepathy/search
REQUEST
curl -H "X-API-Key: sk_••••••••" \ "https://console.generalintels.com/api/telepathy/search\ ?q=combolist&chat_type=channel&crypto=bc1••••&date_from=2026-07-01&sort=date_desc&size=20"
RESPONSE · 200
{
"total": 34,
"page": 1,
"size": 20,
"pages": 2,
"took_ms": 41,
"items": [
{
"id": "9c4e••••",
"telegram": {
"chat": { "type": "channel", "username": "••••" },
"extracted": { "phones": [], "ibans": [] }
},
"threat_actor": { "username": "••••" },
"post": {
"content": "…fresh logs, ULP format, escrow via…",
"created_at": "2026-07-14T08:31:02Z"
},
"iocs": { "crypto_wallets": ["bc1••••"], "domains": ["••••"] },
"attachments": [{ "media_type": "document", "mime_type": "application/zip" }]
}
]
}Channel and handle identifiers are redacted in this sample. Nine of the eleven extracted indicator categories are also query parameters: crypto, email, domain, ip, cve, hash, card, phone, iban. URLs and channel links are carried on the record but are not filters yet. Paging past the result-window ceiling asks you to narrow with a filter rather than truncating in silence.
What a call costs you
Telepathy meters on the API, on a daily ceiling of its own rather than out of a pool shared with the other modules. Working the same corpus in the console is unmetered on every tier.
Full API reference ships with your workspace: every endpoint, versioned.
Telepathy, honestly answered
The other windows
Your competitors will learn about the leak from the invoice.
Learn about it from the log batch.
NDA-friendly briefings · global coverage · no slideware