API pipeline: Have AI read groups in batches, post an overview to your channel and hand picks to a radar

Index: API pipelines — index · Lifecycle: API pipeline: Create, configure, start, stop, measure and delete a Telegram campaign of any kind

Goal: AI reads what is said in your groups in batches, posts an overview with its picks to a Telegram channel of yours, and can hand the picks to a radar for first contact.

Steps

1. Create (Paused).

POST /v0/my/campaigns
Idempotency-Key: scout-bali-1
{"title": "Bali rentals scout", "kind": "mtproto_ai_scout", "project_nonce": "<Pro project>",
 "agenda": "<swappable agenda>", "oracles": ["<oracle nonce>"], "tg_groups": ["<preset nonce>"],
 "batch_window": "6h", "batch_messages": 500, "outreach_campaign": "<your radar nonce>"}
→ {"nonce": "470390000000000001", "kind": "mtproto_ai_scout", "status": "Paused", …}

• agenda: tells the AI what matters to you, what is noise and how to write the overview.
• A batch closes every batch_window (15m | 30m | 60m | 3h | 6h | 12h | 24h | 72h; default 6h) or after batch_messages messages (50–2000; default 500), whichever comes first.
• outreach_campaign (optional): one of your radars; picks the AI marks for outreach go to it for first contact. API pipeline: Listen to Telegram groups for people who need you: create and tune a radar, work its matches and make first contact (draft, send, auto outreach)

2. Start. POST /v0/my/campaigns/470390000000000001/start → {"success": true, "status": "Active", "is_active": true}. On the first start one of your oracles creates a Telegram channel « · AI Scout»; its invite link is on the card as overview_chat_link.

3. Read. Each batch posts an overview with its picks (reason + link to the message) to that channel and keeps it in the campaign's overviews_workspace: GET /v0/my/workspaces/<overviews_workspace>.

4. Stop. POST …/stop. It runs until you stop it.

Behind

• Every batch is an AI run under your agenda; its cost shows in your AI spend: API pipeline: See your AI spend. Prices: link
• Picks handed to a radar follow that radar's outreach rules.

Rules

• Start needs a Pro project, an agenda, oracles and groups: 400 ai scout requires an agenda assigned, ai scout requires oracles assigned, ai scout requires telegram groups assigned.
• batch_window / batch_messages outside the sets → 400; outreach_campaign must be a radar you own (400 outreach_campaign must be a radar campaign).

API surface