search
App StoreGoogle PlayWeb

News RSS

Individual News Feed

hashtag
1. Overview

News RSS is the real-time stream of individual news produced by NS3's news analysis pipeline (Pipeline A). AI reads every article published across 20+ trusted media outlets, then delivers it with importance classification, structured analysis, related coin mapping, and 16-language translation already completed.

  • Real-time updates: As soon as news is processed and published on the NS3 platform, it appears in the RSS feed.

  • AI Insight: Every article includes structured analysis across five sections — Key Point, Market Sentiment, Similar Past Cases, Ripple Effect, and Opportunities & Risks.

  • Latest 100 items: Each RSS URL returns the most recent 100 news items.

  • 16 languages: All content is delivered simultaneously in 16 languages.

  • 20+ trusted media: Reads from CoinDesk, Cointelegraph, CoinMarketCap, Bloomberg Crypto, Reuters Crypto, Forbes Crypto, Fortune Crypto, The Block, Watcher.Guru, and more.

  • Content filtering: Sponsored content, editorial-wrapped promotions, affiliate listicles, presale/casino/ICO promotions, and exchange marketing campaigns are filtered and never delivered.

hashtag
2. How AI Classification Works

This section explains what data NS3's AI assigns to each news article, and how that data is derived. This is what makes NS3 RSS fundamentally different from traditional news sources.

hashtag
2.1 Level & newsType

"Would a crypto market participant NEED to know this today?" → Level 1, 2. "Nice to know but can wait until tomorrow?" → Level 3. "Is there anything to analyze beyond the headline?" → If no, Level 4. "Is this journalism, or promotional noise?" → If noise, Level 5.

Every article is assigned an importance Level (1–5) and a newsType (breaking / important / normal). These two fields are derived from a single classification system.

When classification is uncertain, AI always downgrades by one level. The principle: underestimation is better than overestimation.

Level
newsType
Meaning
Insight

1

breaking

Event that can move the entire market immediately

Full Insight (5 sections)

2

important

Event that can realistically change market rules, access, or liquidity expectations

Full Insight (5 sections)

3

normal

General crypto news

Full Insight (5 sections)

4

normal

Routine notices, digests

Key Point only

5

Noise - Excluded from feed

How classification works

Every article passes through a four-stage classification pipeline.

Stage 1 (L5 Noise Filter): Removes promotional noise that harms feed quality. Sponsored content, editorial-wrapped promotions, and affiliate/traffic bait are classified as Level 5 and excluded from the feed entirely. All genuine reporting, analysis, and commentary from trusted sources passes this filter regardless of topic.

Stage 2 (L4 Filter): Separates routine data and analysis-thin content from news that warrants full five-section insight. Digests, routine operational notices, contextless data points, and content where analysis sections would produce only generic statements (opinions, forecasts, small-scale project updates, chart analysis, unexecuted governance proposals) are classified as Level 4.

Stage 3 (L2 Condition Table): Articles that pass Stages 1 and 2 are checked against a structured condition table across seven categories. If the article's core event matches any condition, it is classified as Level 2. If no condition matches, it is classified as Level 3.

The seven categories:

  1. Regulation / Legal (legislative votes, formal guidance, court rulings, enforcement actions)

  2. Institutional / Product Launch (Tier-1 institution or Top-2 exchange launches)

  3. Macro Data / Policy (U.S./China official data, central bank rate decisions)

  4. Market Structure / Security (hacks $30M+, liquidation cascades $1B+, exchange halts, stablecoin depegs)

  5. Institutional Capital Flows (public company $1B+ crypto purchase, sovereign allocation)

  6. Geopolitical / Macro Shock (chokepoint disruption, war escalation with market reaction)

  7. Crypto Ecosystem Shift (executive orders, mainnet upgrades, major platform crypto integration)

Stage 4 (L1 Override): Only Level 2 articles are eligible for upgrade to Level 1. An article is upgraded only when all three conditions are met: systemic scope (can reprice broad risk assets market-wide), already executed (not planned or expected), and immediate transmission (impact reaches participants within hours).

Level definitions and examples

Level 1 — Critical (Systemic Regime Shift)

A systemic event requiring immediate attention from all market participants. L1 is upgraded from L2 only when all three conditions are met: systemic scope, already executed, and immediate transmission.

  • FOMC emergency inter-meeting rate decision announced

  • Major country enacts immediate crypto ban with enforcement

  • Active military strikes close Strait of Hormuz with oil surging 30%+ in hours

  • Major algorithmic stablecoin collapse (Terra/UST-level event)

Actor restrictions: macro/policy events require U.S. or China. Stablecoin events require USDT or USDC. L1 is expected to occur 0 times on most days.

Level 2 — Important (Meaningful Market Change)

A concrete event that changes rules, access, liquidity expectations, or institutional demand. Determined by the Stage 3 condition table across seven categories.

  • Legislative vote passes on crypto-related bill

  • Regulatory agency issues formal crypto guidance or framework

  • Court delivers ruling in a case with industry-wide implications

  • Tier-1 institution (BlackRock, Fidelity, Goldman Sachs) or Top-2 exchange launches new product or service

  • U.S./China official economic data release (CPI, NFP, GDP, rate decision)

  • Protocol hack with confirmed losses of $30M+

  • Major energy chokepoint disrupted with market reaction described

  • Executive order signed addressing crypto assets

Level 3 — General

Default for articles that pass Stages 1 and 2 but do not match any L2 condition. Meaningful at the project or sector level, with enough substance for five-section analysis.

  • Single ecosystem operational issues, mid-size security incidents

  • Token unlock/vesting/distribution changes, limited governance decisions

  • Institutional pilots without market-wide access shift

  • Mid-size economy macro policy

  • Research reports without binding action

Level 4 — Routine / Data

Routine notices, digests, and content where five-section analysis would produce only generic statements.

  • Summaries/digests/roundups/market updates (always Level 4)

  • Routine listings/delistings, fee events, maintenance

  • Contextless whale alerts, on-chain movements, standalone data points

  • Analyst price predictions, chart analysis, opinion pieces without accompanying official action

  • Small-scale project updates, partnership announcements below $50M

  • Unexecuted governance proposals, testnet launches

Level 5 — Noise

Promotional content disguised as news. Excluded from the feed entirely.

  • Sponsored articles, advertorials, paid content, exchange marketing campaigns

  • Editorial-wrapped promotions for unknown projects with unverifiable claims

  • Affiliate-driven ranking listicles, clickbait price predictions, recurring pick-list filler

  • "How to buy" guides, presale/ICO promotions, airdrop claim guides

I/A/T Scoring (downstream ranking)

After classification, Level 1-3 articles are independently scored on three dimensions. They are used by Top News RSS and Daily Market Update RSS for story ranking.

  • Impact (I): Scope of effect (0 = narrow, 1 = sector, 2 = broad market)

  • Actionability (A): How concrete the core event is (0 = narrative, 1 = verifiable marker, 2 = binding/operative now)

  • Transmission (T): Path to crypto markets (0 = weak, 1 = plausible near-term, 2 = direct crypto infrastructure)

hashtag
2.2 AI Insight

Level 1–3 articles include structured analysis in five sections. Level 4 articles include Key Point only.

Section
Core question

Key Point

What happened? Fact-only summary of the core event. Level 1–2 includes "Why it matters."

Market Sentiment

How is the market likely to read this event? Provides directional label (Bullish/Bearish/Neutral) + catalyst label.

Similar Past Cases

What happened in comparable past events? Level 1–2 provides web-search-verified historical cases.

Ripple Effect

Where could this event spread? Transmission mechanism analysis.

Opportunities & Risks

What to monitor next? Conditional action cues: "If X happens, then Y is a signal to..."

hashtag
2.3 mentionedCoins

Related token symbols are automatically mapped to each article.

  • Based on CoinMarketCap ID table (updated daily)

  • Only coins explicitly mentioned in the article are included

  • Sorted by relevance: core asset → directly impacted asset → structural role asset

hashtag
2.4 Translation

NS3 translation is Equivalent Comprehension Transfer.

Purpose: Each language reader achieves the same level of understanding and the same level of actionability as an English-reading audience.

Core principle: How something is said may change. What is said never changes.

  • Allowed: Sentence splitting/merging, replacing awkward phrasing with local finance collocations, natural clause reordering

  • Forbidden: Adding/deleting/changing facts, strengthening/weakening certainty, adding analysis/opinions/background

When translation choices conflict — for example, a locally natural phrase that slightly shifts comprehension — resolve by the following priority:

Optimization priority

  1. Equivalent comprehension for local readers

  2. Newsroom desk tone and delivery quality

  3. Natural localization

Supported languages (16): English, 简体中文, 繁體中文, 한국어, 日本語, Русский, Türkçe, Deutsch, Español, Français, Tiếng Việt, ไทย, Bahasa Indonesia, हिन्दी, Italiano, Português

hashtag
3. How RSS Fields Map to UI

This section shows how each RSS field is rendered in the actual NS3 app.

UI Element
RSS Field

① Relative time

pubDate — client converts absolute timestamp to relative format

② Headline title

title

③ AI Summary text

description

④ Thumbnail image

media:content — falls back to default image when missing

⑤ IMPORTANT / BREAKING badge

newsType

⑥ Coin tags

mentionedCoins

⑦ AI INSIGHT button (click destination)

link

⑧ Full AI Insight analysis

insight — 5-section markdown (Level 1–3) / Key Point only (Level 4)

Design principle: All core content — headline, summary, navigation target, timestamp, image, classification, and analysis — is fully driven by RSS fields. This guarantees consistent behavior across web, mobile, and partner integrations.

Example feed: https://ns3.aiarrow-up-right

hashtag
4. Validate the Data Yourself

You can verify data quality directly before integration.

News data & analysis quality

Provide the RSS URL below to any AI model and ask what your platform could build with it.

Example prompt:

circle-check

Read the RSS feed at the following URL. Based on the data structure and content available in each item, list the specific news features and user experiences our crypto platform could build using this feed — without any additional data source or AI processing on our side. https://api.ns3.ai/feed/news-data?lang=en

Translation quality

Provide two RSS URLs — one in English and one in your target language — to any AI model and ask whether users in both languages would receive the same information.

Replace the language code to test any of the 16 supported languages: en · zh-CN · zh-TW · ko · ja · ru · tr · de · es · fr · vi · th · id · hi · it · pt

Example prompt:

circle-check

Read the news data at the following URLs — one in English and one in Korean. Compare the two and evaluate whether a Korean-speaking user would get the same level of information and the same ability to act on the news as an English-speaking user. https://api.ns3.ai/feed/news-data?lang=en https://api.ns3.ai/feed/news-data?lang=ko

chevron-rightTechnical specification for developers starts belowhashtag

Section 5-12 is documentation for developers.

hashtag
5. RSS URL & Languages

hashtag
Base URL

hashtag
16 Language URLs

Language
Code
URL

English

en

https://api.ns3.ai/feed/news-data?lang=en

简体中文

zh-CN

https://api.ns3.ai/feed/news-data?lang=zh-CN

繁體中文

zh-TW

https://api.ns3.ai/feed/news-data?lang=zh-TW

한국어

ko

https://api.ns3.ai/feed/news-data?lang=ko

日本語

ja

https://api.ns3.ai/feed/news-data?lang=ja

Русский

ru

https://api.ns3.ai/feed/news-data?lang=ru

Türkçe

tr

https://api.ns3.ai/feed/news-data?lang=tr

Deutsch

de

https://api.ns3.ai/feed/news-data?lang=de

Español

es

https://api.ns3.ai/feed/news-data?lang=es

Français

fr

https://api.ns3.ai/feed/news-data?lang=fr

Tiếng Việt

vi

https://api.ns3.ai/feed/news-data?lang=vi

ไทย

th

https://api.ns3.ai/feed/news-data?lang=th

Bahasa Indonesia

id

https://api.ns3.ai/feed/news-data?lang=id

हिन्दी

hi

https://api.ns3.ai/feed/news-data?lang=hi

Italiano

it

https://api.ns3.ai/feed/news-data?lang=it

Português

pt

https://api.ns3.ai/feed/news-data?lang=pt

lang is a required parameter. All other parameters are optional.

hashtag
6. Item Field Specification

hashtag
6.1 Standard RSS Fields

title

  • Meaning: AI-generated news headline

  • Type: string (CDATA-wrapped)

  • Use: Primary headline text in feed lists

description

  • Meaning: Core summary of the original article (1–4 sentences)

  • Type: string (CDATA-wrapped)

  • Use: Article preview snippet

  • Note: CDATA-wrapped; the content is plain text, not HTML. Normalize whitespace and line breaks on the client side.

link

  • Meaning: NS3 AI INSIGHT page URL (click destination)

  • Type: URL string

  • Use: Used when linking to the NS3 Insight page rather than serving AI Insight internally.

guid

  • Meaning: Unique item identifier (deduplication, update tracking)

  • Type: URL string, isPermaLink="true"

  • Note: Currently matches link, but do not assume they always match.

  • Recommended: Use guid for deduplication, link for navigation.

pubDate

  • Meaning: Publish time from the original source

  • Type: RFC 822/1123 format (e.g., Tue, 27 Jan 2026 06:33:37 GMT)

  • Use: Timeline ordering, "3 min ago / 2 hours ago" display

media:content

  • Meaning: Social preview image URL from the original source

  • Type: URL string, medium="image"

  • Note: May be missing. Some sources do not provide preview images.

hashtag
6.2 NS3 Extended Fields

mentionedCoins

  • Meaning: Token symbols related to the article

  • Type: string (CSV format, e.g., BTC,ETH,SOL)

  • Note: May be missing. If no token is explicitly mentioned, the value may be empty or the tag absent.

  • Parsing: Split by , → trim each item → normalize to uppercase

newsType

  • Meaning: AI-assigned news type

  • Values: normal | important | breaking

  • Type: enum string

  • Use: "Breaking only", "Important only" UI filters

level

  • Meaning: AI-assigned news importance (1 = most important)

  • Values: 1 | 2 | 3 | 4 | 5

  • Type: integer

  • Use: Push notification / exposure priority policy

  • Note: Level 5 is excluded from the RSS feed.

storyKey

  • Meaning: Structured event identifier for story clustering. Encodes the core event as four fields: who did what to whom, with what figure.

  • Type: object with four string fields, or null

  • Clustering logic: Two articles describe the same story when 3 or more of the 4 fields match.

Field
Meaning
Example values

entity

Primary actor or subject

sec, blackrock, trump, bitcoin

action

Core action or event type

ruling, launch, agreement, suspension

target

Object, instrument, or context

ripple-lawsuit, spot-btc-etf, iran-war

figure

Key numeric value, or none

500m, 30pct, none

hashtag
6.3 AI Insight Field

insight

  • Meaning: Full AI structured analysis

  • Type: string (CDATA-wrapped, markdown format). Render as rich text or parse individual sections by splitting on ## headings.

  • Section delimiter: ## headings

Level 1–3 structure:

Level 4 structure:

Parsing guide: Split on the ## string to extract individual sections. Depending on your platform's needs, render the full insight or selectively use specific sections.

hashtag
7. Filtering (URL Parameters)

All filter parameters are appended to the base URL as &key=value. URL-encode parameter values when they contain reserved characters.

hashtag
7.1 Token filter: crypto (multi)

Returns only news related to a specific token.

hashtag
7.2 News type filter: newsType (single)

hashtag
7.3 Exclude sources: excludeSources (multi)

Source IDs are listed in the table in Section 8.

If , is a reserved character in your environment, use URL encoding: excludeSources=1%2C2

hashtag
7.4 Exclude levels: excludeLevels (multi)

Excludes articles at specific levels.

Level
newsType
Meaning
Insight

1

breaking

Event that can move the entire market immediately

Full Insight (5 sections)

2

important

Event that can realistically change market rules, access, or liquidity expectations

Full Insight (5 sections)

3

normal

General crypto news

Full Insight (5 sections)

4

normal

Routine notices, digests

Key Point only

5

Noise - Excluded from feed

hashtag
7.5 Exclude categories: excludeCategories (multi)

Excludes articles in specific categories. Category IDs:

ID
Category

1

Market Trends

2

Regulation & Policy

3

Institutional Updates

4

Market Outlook & Expert Views

5

General

6

Exchange & Venue Operations

7

Macro & Geopolitical

Example: Exclude exchange listing news and routine notices:

Multiple categories can be excluded:

hashtag
7.6 Result limit: limit (single)

Controls the number of items returned. Default is 100.

limit
Estimated tokens
Use case

10

~7,000–9,500

Quick scan

20

~14,000–19,000

Recommended default

50

~35,000–47,500

Broad range

100 (default)

~68,000–94,000

Full feed

Token estimates are based on Level 2–3 articles (5-section insight included). Level 4 articles contain Key Point only and are significantly lighter at approximately 250 tokens per item.

This parameter was introduced primarily for AI agent integrations, where each RSS fetch consumes context window tokens. Reducing the item count directly reduces token cost per call. For traditional polling integrations, limit is also useful when the platform only needs a fixed number of recent items per poll cycle (e.g., displaying the latest 10 articles on a homepage widget), reducing payload size and parse time.

limit controls only the number of items returned. Increasing the limit does not produce new news. It adds older articles. Combine with filters for best results:

hashtag
7.7 Recommended filter for exchanges

When using News RSS as the news feed on an exchange platform, competitor exchange listings, fee changes, and routine operational notices are typically unwanted. The following filter combination blocks approximately 99% of other exchange-related news:

Parameter
Effect

excludeCategories=6

Removes Exchange & Venue Operations (competitor listings, fee changes, regional expansion, maintenance, system updates, exchange-targeted regulatory actions)

excludeLevels=4

Removes routine notices and data-only articles.

hashtag
7.8 Combined filters

Multiple parameters can be combined.

BTC-related news only, exchange operations excluded, promotional noise excluded, latest 20 items:

hashtag
8. Original Source Media

Media sources by NS3. Use the source ID with the excludeSources parameter.

ID
Source Name

1

Cointelegraph

2

CoinDesk

3

CoinMarketCap

4

Watcher.Guru

5

The Daily Hodl

6

Beincrypto

7

Decrypt

8

The Block

9

Bloomberg Crypto

10

Forbes Crypto

11

Reuters Crypto

12

Fortune Crypto

13

CoinNess

14

Odaily

15

CryptoSlate

16

Bitcoin Magazine

17

DL News

18

The Defiant

19

Protos

20

Wu Blockchain

hashtag
9. Error Handling & Edge Cases

Client implementations should handle the following cases by default.

hashtag
9.1 Missing media:content (no image)

  • Cause: The original source does not provide a social preview image.

  • Product: Use a default image/logo or a no-image card layout.

  • Engineering: Treat missing media:content@url as null. Do not throw exceptions.

hashtag
9.2 Missing or empty mentionedCoins

  • Cause: No token is explicitly mentioned, or AI cannot confidently map symbols.

  • Product: Hide the coin tag area.

  • Engineering: Allow both missing tag and empty string. If parsing yields an empty array, treat as "no tokens."

hashtag
9.3 Potential guid vs link mismatch

  • guid and link currently share the same value, but this is not guaranteed. They may diverge in future updates.

  • Use guid for deduplication, link for navigation.

hashtag
9.4 pubDate parsing failure

  • pubDate is typically RFC 822/1123, but environments may vary.

  • Engineering: Parse RFC 822/1123 first, then fall back to ISO 8601 (defensive parsing).

hashtag
9.5 insight field handling

  • Level 1–3: Contains all 5 sections.

  • Level 4: Contains ## Key Point section only.

  • When splitting on ## , account for the variable number of sections.

hashtag
9.6 HTTP error handling

Status
Meaning
Recommended action

200

Success

Process feed normally

304

Not Modified

Use cached version (when conditional request headers are supported)

400

Bad Request (e.g., invalid lang code)

Check parameter values

500, 502, 503

Server error

Retry after 30–60 seconds. Do not retry immediately in a tight loop.

If the server is unreachable or returns a non-200 response, continue serving the last successfully fetched feed until the next successful poll.

hashtag
10. Polling & Caching

News RSS updates in real time.

hashtag
Recommended polling interval

  • 5 minute – 15 minutes

  • Adjust based on traffic, cost, and UX balance.

hashtag
Caching principles

  • If the server provides ETag / Last-Modified, use conditional requests (If-None-Match / If-Modified-Since).

  • If not provided: Set a short client-side TTL (e.g., 1–5 minutes) and refresh.

  • Feeds are limited to the latest 100 items. Clients inactive for extended periods may miss intermediate items.

hashtag
11. Implementation Checklist

hashtag
12. FAQ

Q: How many Level 1 articles occur per day?

Level 1 is reserved for system-level events that can move the entire market immediately. Most days produce zero. Even during major events, expect 1–2 per day at most. Level 2 articles average 30–50 per weekday. The majority of articles are Level 3.

Q: Is newsType "breaking" the same as a News Flash RSS headline?

No. newsType "breaking" is a classification assigned by the news analysis AI based on an individual article's importance. News Flash RSS is a separate feed produced by a different pipeline (paid breaking news services → AI rewrite). The sources and production processes are entirely different.

Q: How many articles are included in a feed?

Each RSS URL returns the latest 100 items by default. Use the limit parameter to reduce the number of items returned (e.g., limit=20 returns the latest 20). Filters such as crypto, newsType, and excludeCategories narrow the scope first, then the feed returns up to 100 (or the specified limit) items within that scope. Increasing the limit does not produce new news. It adds older articles.

Q: If a digest article contains a major event, does its Level get elevated?

No. Digest/roundup/market update articles are always Level 4, regardless of what they contain.

Q: Why do multiple articles about the same event appear?

NS3 reads articles from 20+ media outlets. When multiple outlets cover the same event, each is analyzed and delivered independently. Every article includes a storyKey field (entity, action, target, figure) that identifies which event it belongs to. Articles with 3 or more matching storyKey fields describe the same story. Partners can use storyKey to build their own story grouping or deduplication. For pre-built story clustering, use Top News RSS, which groups related articles and delivers a ranked Top 10.

Q: Can I receive only articles at specific levels?

Use the excludeLevels parameter to exclude specific levels. For example, &excludeLevels=4 delivers only Level 1–3 articles. newsType=important filters to Level 2 articles only.

Q: Why are some articles missing images?

The original source does not provide a social preview image. Handle this in your UI with a default image or a no-image layout.

Q: Why are some on-chain movement or liquidation articles classified as Level 4?

When an article reports only a data point (e.g., a wallet transfer with no stated reason, a small liquidation snapshot, or a price-level crossing with no catalyst), there is nothing to analyze beyond the headline. These articles receive Key Point only. If the same type of article includes a stated cause, a known-event connection, or systemic framing, it passes to Level 3 with full analysis.

Q: Are geopolitical or macro news articles excluded as off-domain?

No. All genuine reporting from trusted sources passes the feed regardless of topic. Geopolitical events, macroeconomic data, and traditional finance news are classified at Level 2-4 based on their market impact. Only promotional noise (sponsored content, affiliate listicles, editorial-wrapped promotions) is excluded as Level 5.

Last updated