A second WebSocket that waits for the summary
Articles are on the site, on REST, and on /v1/stream as soon as they are ingested. A new socket, /v1/stream/summaries, sends the same article a few seconds later, after the AI summary is written.
The live feed does not wait for an AI summary. /v1/stream and the website show the article at ingestion, with summary null until it is ready. /v1/stream/summaries is the delayed socket: its welcome message says so, and each article on it includes the summary. REST returns the summary once it is stored.
Which socket do I open?
Use wss://ws.marketnewsapi.com/v1/stream when you want the headline the moment it is ingested. Use wss://ws.marketnewsapi.com/v1/stream/summaries when you want to wait for the summary. Both use the same channels and the same plan limits. The WebSocket guide shows the welcome message from each socket.