Skip to main content

Balance and usage

Signailist has no subscription: performed work is charged to the selected workspace’s shared balance, whether started in the app, through MCP or through the API. Top up manually through the administrator. A source may be free to access while collecting, saving, analysing and publishing its materials still uses paid service resources.

Estimate before starting​

Open the cost calculator before collecting sources or launching AI, publishing or webhooks. Select a 30-day workload and models to see estimated costs by stage. The application billing page links to the same calculator. This is a planning estimate, not a subscription, spending limit or reservation; actual text length, source sharing and delivery attempts affect charges.

You can also give an agent just the pricing page URL. Its HTML includes links to the calculation guide and the public JSON catalog: final prices, input constraints, stage formulas, example workloads and results. The guide includes a runnable Python example. No sign-in or JavaScript execution is required. Ask the agent to state workload assumptions and exclusions; use API/MCP estimates and workspace budget checks before actually running work.

What uses the balance​

  • Collecting Telegram, RSS/Atom, GitHub Releases, Steam and YouTube, including checks that find no new entries.
  • Looking up a YouTube channel or Steam game name when adding a source, even when the new source starts paused.
  • Receiving and saving versioned materials from your own systems, and physical outgoing webhook delivery attempts.
  • Saving feed entries, preparing materials, AI topic scoring and generating text or images.
  • Publishing to the selected Telegram and Discord channels. Each destination is tracked separately.

An external service may require several requests to obtain one result. Failed requests also consume resources. If delivery cannot be confirmed, check the destination before retrying: the publication may already exist.

Where a public feed is collected once for several workspaces, the collection cost is shared between the participating workspaces. Personalised AI processing, storage and delivery remain separate.

When the balance runs out​

New collection, name lookups, AI work and publication require a positive workspace balance. Adding a source that needs a name lookup can therefore require balance before you enable its collection.

You can still read saved materials, view your balance and pause sources. Opening application pages does not itself create a usage charge. After topping up, check that the required sources and schedules are enabled.

Reviewing spending​

Open Workspace settings → Billing to see your balance, spending groups and operation history. Small operations may cost less than the rounded amount shown in a summary. Usage amounts include an infrastructure estimate; they are not a copy of an external provider’s invoice.

Source collection combines Telegram and feed collection, source name lookups and feed storage. In operation history, combine Operation type, Platform (Telegram, RSS/Atom, GitHub Releases, Steam or YouTube) and Source to narrow the list. These filters apply to the history; the balance and spending cards keep the selected period's totals. Enable Show exact amounts to see small charges in full.

Pausing a source stops future collection. It does not cancel work already started, AI tasks or publication schedules; manage those separately.

API, MCP and webhooks​

Integrations use the same workspace balance. External material intake and physical webhook delivery attempts have their own usage operations; MCP adds no access surcharge. The integration settings show reserved and available funds separately. Workspace and connection daily limits use UTC days. Read-only access, pausing and revocation remain available without balance. See the developer guide for costs, retries and interrupted-reservation review.