Signailist Overview
Signailist turns information from different sources into relevant materials, digests and publications. Collect public feeds and channel messages, submit text from your own systems, analyse materials against your topics, and prepare results for your team or audience.
Work in the application, ask an agent through MCP, or connect your system through REST API and webhooks. These interfaces use the same workspace, permissions, processing queues and balance.
Choose your starting point
| Your task | Start here |
|---|---|
| Publish original material on a schedule | Create an author series, then manage it in Autopublish |
| Prepare a first digest | Add sources, configure AI topics, then create a digest |
| Receive a weekly briefing | Prepare a first issue, then configure a weekly schedule |
| Follow releases, games or video channels | Choose GitHub Releases, Steam or YouTube in Sources |
| Set up the workflow with an agent | Connect MCP and copy a workflow prompt |
| Send your own materials and receive results | Use external intake and webhooks and the API reference |
| Plan spending before running work | Read Balance and usage and use the cost calculator |
From source to result
Public feeds / Telegram channels and chats / your system's text
↓
Collection or intake → preparation → AI analysis by topic
↓
Selected materials → digest → text and optional image
↓
Review and approval → publication to Telegram / Discord
↓
Results and status available in the app, API / MCP and subscribed webhooks
Source and destination are independent. Combine materials from several sources in one issue, keep a draft in the workspace, publish it to configured channels, or retrieve results for your own system. Telegram is one supported source and destination; it also provides optional alerts and moderation.
Capabilities
| Stage | What you can do |
|---|---|
| Sources | Collect RSS/Atom, GitHub Releases, Steam news, YouTube feed entries and Telegram messages |
| External intake | Submit versioned text materials through a private workspace source |
| Analysis | Prepare materials, classify content and score relevance against topics with explanations |
| Signals | Track related events and send Telegram alerts when configured thresholds are met |
| Digests and templates | Select materials, define tone and structure, generate text and optional images, and edit drafts |
| Publication | Approve a revision and send it to Telegram, Discord or several destinations with separate delivery status |
| Recurring work | Prepare publications from signals or schedules; control approval, enablement and pauses |
| Integrations | Configure and run work through scoped API keys or MCP access; receive signed webhook events |
| Spending | Estimate usage, inspect charges and reservations, and set workspace and connection limits |
Feed sources provide the content available from the provider. YouTube entries do not include video or transcript analysis. See source requirements and limitations before choosing inputs.
Workspaces and access
Each workspace isolates its materials, configuration and balance. Owners, Editors and Viewers have different permissions. API keys and MCP sessions belong to a selected workspace and cannot exceed their issuer's current rights. Publication requires explicit permission; provider connection and initial authorization may require a browser.
Start with one result
Create a manual draft before enabling recurring publication. The RSS → Discord example walks through a complete issue. If you prefer an agent, use the weekly digest prompt. Check the sources, topic, template, destination and estimated cost, then enable the schedule when ready.
Signailist uses a shared workspace balance with no subscription. Performed work consumes balance; top-ups are handled manually through the administrator. See Balance and usage.