StreamBot

Ask it the way you would ask a colleague who knows the product. It works out which of three jobs you mean and says so, with the interpreted filters shown so you can correct it.

• ▸Help and navigation - how a page works, where a control lives, what your plan includes. It links you to the right place; it does not move you there.
• ▸Building screens - describe a report ("Canadian gold projects at feasibility with a study this year") and it shows the validated filters with a few genuine matching rows. You open the full screen yourself, and with Pro you can save it as a report.
• ▸Research - a question that needs the database read, compared or summarised, with every figure carrying its source and date. Research is the only kind of request that counts against your monthly allowance.

• ▸Navigate for you. Every result is a preview with an Open link; nothing changes the page under you.
• ▸Change your billing. Plan changes, cancellation and card details stay in Settings and on the pricing page.
• ▸Edit shared data. It reads the database; it cannot write to a company, project, deal or article. Corrections go through Report error in the company or project header, or the flag on the affected row. It cannot submit that form for you.
• ▸Act on other people’s data. It only ever sees your own watchlist, saved items and alerts, and only what your plan already lets you open.
• ▸Invent a field, a source or a number. If the data is not there it says so rather than guessing.

Help, navigation and filter-building are free on every plan and never count. Research requests are metered per calendar month, and the numbers below are the same ones on the pricing page.

StreamBot help, navigation and filter-building are included on every plan; only research requests count.

Signed out, you get one introductory research request to see how it works - no monthly reset, and help and filter-building stay open. A research request never unlocks data your plan does not include: a Free account researching a Pro dataset sees the same preview rows the rest of the app shows, with an honest note about what the full screen would add.

StreamBot tells you before a request is spent. A research answer asks you to confirm with a Run research button and shows how many requests remain this month; the rail carries the same figure next to your plan. Compare all plans.

StreamBot can act on your own lists when you ask it to - follow a company, save a deal or an article, save a screen you built together. It prepares the action for you to confirm with a button. It only reports success after the change is confirmed.

• ▸You ask - "follow these three" - then click the proposed action to confirm. A general question never triggers a write.
• ▸It confirms with a receipt - what changed, in one line, in the conversation.
• ▸The receipt links to the place it changed - your watchlist, the saved reports list, the alerts page - and the rest of the app updates at once.
• ▸Undo is where it always was: the star, the bookmark or the bin on the row itself.

Page context starts off. Select Limit request to in the composer to attach the current page or screener filters to your next message. A chip shows what you selected; remove it to send without that context. Explain unread and Ask about my watchlist attach the items you selected. Attaching context never sends a message on its own; nothing leaves until you press Send.

For follow-up questions, StreamBot uses the last 12 messages in the same chat. Your conversation history stays saved. Start a New chat for fresh context; your previous chats remain in History.

• ▸History - conversations are kept per account and listed under History in the workspace header.
• ▸Delete a chat - open History using the clock icon in the StreamBot header, select the bin beside the chat, then confirm Delete?. When deletion succeeds, its messages and associated stored results are removed from our active server database.
• ▸New chat starts a separate conversation. The × beside Continue chat only dismisses that suggestion. Neither deletes the saved chat.
• ▸Deleting a chat keeps your watchlist, saved research screens, alerts and usage counters. Remove saved items separately if you no longer want them.
• ▸Signed out - chats are stored on our server under a signed browser session. After signing in, Keep your chats lets you explicitly transfer that session’s chats to your account.
• ▸Explaining an update never marks it read. Opening the alert does, exactly as before.

Model-backed answers use OpenAI. Your message, relevant recent conversation, attached context and the records needed to answer are sent for processing; this can include your notifications when you ask about them. Do not include passwords, API keys or other secrets. Chats are stored in Supabase. Inactive signed-in chats are eligible for cleanup after 180 days, and anonymous chats after 30 days, through a daily bounded sweep. You can delete a chat sooner from History. Backups may retain deleted content until they expire, and model-provider records have separate retention rules. Chats are not end-to-end encrypted. Read how we handle your data for storage, processing and privacy contact details.

The watchlist guide covers following and saving in full, the alerts guide covers how updates reach you, and the research screens guide explains what happens to a screen StreamBot builds once you save it.