+++ nonce = "330494191513632781" project_nonce = "999" owner = "596642625" language = "en" title = "Radars" content_hash = "abff8b13a99dcfde60d934509437bcf661af7b73204927aee8cbcba620f490ce" +++

Radars

A radar is the mechanism by which your project listens to Telegram. You define which groups it monitors (via a group preset), which signals it cares about (keywords, example phrases), and what bounds apply (geography, budget).

A radar has two modes — two distinct products inside the same mechanism.

Radar with oracle participation. When a signal is caught, an oracle reaches out to the correspondent in DM. The trigger is a match against your project's intentions, and the project goes first in the candidate list the oracle holds for that conversation. But the oracle represents the registry, not just one project: what's guaranteed is that your project is in the list, not that the correspondent will pick it. The correspondent may ask the oracle to search more, surface alternatives, compare — and the correspondent decides which project to spawn a meeting with. Charging happens only when a meeting is created and the winning project is yours.

Radar without oracle participation. Same scanner, same filtering — but no outbound. The radar simply finds matches and stores them in the cabinet as caught messages. You open a caught message and see the text, the keywords that matched, the context. The location (the group where the message appeared, the link to the specific message) is locked; unlock it for the minimum lead price. This is the volume-and-control mode: useful when you want to see what's being said across many chats at once, and you want to do the outreach yourself.

A radar is managed like any campaign: start, pause, resume, stop. Matches and results are visible in the cabinet, including a staging area showing what the radar is "thinking of catching" before a match gets confirmed.