News, grouped into events
NFN now groups related coverage news into events, in the web app, REST API and MCP server.
A company files quarterly results. A newswire reports the figures, and local publications follow with their own coverage. In an article feed, each report is a separate headline, and readers work out for themselves whether the headlines describe a new development or the same release.
NFN now groups that coverage into one event, with the source articles attached.
Each event has a summary and lists the companies involved. As new articles are published, they are added to the event and its summary is revised. Larger developments may also have a story: a longer narrative built from the same sources.
Read developments in the feed
News now opens on the events feed, with the article and story feeds only a click away. Each row in the feed is one development. Open it to view the summary, see the source articles, or read the associated story when available.
The events feed starts on Notable, which shows material developments. Switch to All to include routine filings, scheduled disclosures and commentary. Filter by event type, such as earnings, M&A or management changes. Company, watchlist, country, exchange, stock index, category and sector pages have an events feed too.
Give AI agents one record per development
Previously, AI agents searched articles for the full news record, searched stories for a synthesis, then reconciled the overlapping results themselves. Through the MCP server, Claude, ChatGPT and other agents now get one record per development, with the source articles attached.
search_events finds developments by company, market, event type, significance or date. get_event returns the summary, companies, article IDs and any related story IDs. list_event_types returns the taxonomy. get_company_news groups a company's recent developments by type.
Build on events through the REST API
The REST API exposes the same event structure. GET /api/v1/events lists developments, and GET /api/v1/events/:id returns one with its article IDs and any related story IDs. GET /api/v1/event_types returns the taxonomy. GET /api/v1/companies/:id/events narrows the list to a company.
Article and story responses also include their event ID, so integrations can move between a development and its coverage without matching articles themselves.
Events and the calendar
Events are not the same as calendar events. Events describe developments that have happened. Calendar events remain the place for scheduled earnings dates, AGMs, dividends and investor days.
When a calendar event has news coverage, the calendar now shows the related event. Expand the entry to read the summary, see the source articles, or open the story when there is one. You can follow the news on a scheduled date from the calendar itself, without switching to the company's news feed and matching articles to the day.
Availability
Existing API keys work with the event endpoints and MCP tools. The Plus plan now includes 2,500 MCP requests a month, so you can connect Claude, ChatGPT or another agent and start querying events. Access to content and available history follows existing plan limits.
Next steps
View our API documentation to learn how to build events into your workflows.
To see events in action, visit the news feed.