The chat inside the product is the place where you talk to your agent about the news. No need to switch to another window, copy data and explain which event you mean: the agent sees the same material, events and settings you see on the screen.
Why a chat inside the product
Because management here is a conversation. “Add a source”, “too much noise, fix it”, “why did I not get the message about this supplier?” — normal phrases, not an attempt to find the right setting in a list of forty parameters. The agent knows your data and answers from it, not in general terms.
Connecting
The chat needs your Xedant Agent: two values are set — the address and the key for reaching the agent. Usually they are set at installation, together with the other settings.
- Without the connection the chat is simply hidden — everything else works: collection, monitors, events, alerts, publishing, feeds, management.
- Commands can be given by hand too — every screen has buttons that copy a ready management command: that works when there is no chat.
- The agent key is a secret — it is not shown in the interface and is masked when the settings are read.
What the agent can do
- Add and configure sources — sites, feeds, Telegram channels, search queries, product pages.
- Create monitors and rules — “watch the price”, “everything about regulation — into a separate digest”.
- Explain an event — what happened, how important it is, and why it decided so.
- Assemble a publication draft — from an event or a story, in your style; it publishes only after your “yes”.
- Answer a data question — “how many times was the competitor mentioned this month”, “which sources are silent”.
- Cut the noise — adjust the thresholds and rules so the alerts become useful again.
Command cards on the screens
On every screen, a button sits next to the item. It does not perform the action itself; it prefills a ready phrase for the agent: “check the monitor now”, “prepare a draft for this event”, “pause the monitor for a day”, “repeat the delivery”. You see what exactly will be sent, and you can adjust the wording before sending.
This is more convenient than it sounds: no need to remember what a command or an object is called. The button already knows the context of what you opened.
The chat panel
The chat opens at the side and does not cover what you are looking at: you can keep an event card in front of you while discussing it with the agent. Conversations are saved — the history can be revisited to see what you asked a month ago.
The chat list also includes the ones you had through other agents: work with the product is visible in one place, not smeared across different windows.
Working without an agent
Without a connected agent the product stays fully manageable — you simply give the commands yourself. The command buttons copy a ready management command, and it can be sent from your own system. Everything else works as usual: collection, events, alerts, publishing, feeds and analytics do not depend on the chat.
License
The license restricts exactly one action — sending a message to the AI agent chat. Everything else works without it: collection, monitors, events, rules, alerts, channels, publishing, feeds, analytics and management over the API.
When the license term has expired, a clear notification arrives instead of a silent breakage. Details about the terms and prices are on the News Agent Licensing page.
What to expect from the model
- The agent answers from your data — it sees the events, the material and the settings, not “the news in general”. That is why the answers are specific: not “the market is restless” but “three suppliers raised prices this week”.
- The model can be wrong — which is why the product has quote verification, the honest “unscored” mark and the decision journal. Important things should be checked against the source links.
- Spending is visible — how much went to conversations and processing is shown in analytics: Analytics, Search & Exports.
Next: short answers to frequent questions — the News Agent FAQ section, and the rules and prices — the Licensing section.
Next → Documentation index