finance-sentiment

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Finance Sentiment Skill

金融情绪分析Skill

Fetches structured stock sentiment from the Adanos Finance API.

This skill is read-only. It is designed for research questions that are easier to answer with normalized sentiment signals than with raw social feeds.

Use it when the user wants:

cross-source stock sentiment
Reddit/X.com/news/Polymarket comparisons
buzz, bullish percentage, mentions, trades, or trend
a quick answer to "what is the market talking about?"

从Adanos Finance API获取结构化股票情绪数据。

这个skill是只读的，专门用于处理那些通过标准化情绪信号比原始社交信息流更容易回答的调研类问题。

当用户有以下需求时可以使用：

跨来源股票情绪分析
Reddit/X.com/新闻/Polymarket多平台对比
热度、看涨比例、提及量、交易数或趋势查询
快速回答“市场现在在讨论什么？”这类问题

Step 1: Ensure the API Key Is Available

步骤1：确保API密钥可用

Current environment status:

bash

!`python3 - <<'PY'
import os
print("ADANOS_API_KEY_SET" if os.getenv("ADANOS_API_KEY") else "ADANOS_API_KEY_MISSING")
PY`

ADANOS_API_KEY_MISSING

, ask the user to set:

bash

export ADANOS_API_KEY="sk_live_..."

Use the key via the

X-API-Key

header on all requests.

Base docs:

text

https://api.adanos.org/docs

当前环境状态：

bash

!`python3 - <<'PY'
import os
print("ADANOS_API_KEY_SET" if os.getenv("ADANOS_API_KEY") else "ADANOS_API_KEY_MISSING")
PY`

如果返回

ADANOS_API_KEY_MISSING

，请让用户执行以下命令设置：

bash

export ADANOS_API_KEY="sk_live_..."

所有请求都需要在请求头

X-API-Key

中携带该密钥。

基础文档地址：

text

https://api.adanos.org/docs

Step 2: Identify What the User Needs

步骤2：识别用户需求

Match the request to the lightest endpoint that answers it.

User Request	Endpoint Pattern	Notes
"How much are Reddit users talking about TSLA?"	`/reddit/stocks/v1/compare`	Use `mentions` , `buzz_score` , `bullish_pct` , `trend`
"How hot is NVDA on X.com?"	`/x/stocks/v1/compare`	Use `mentions` , `buzz_score` , `bullish_pct` , `trend`
"How many Polymarket bets are active on Microsoft?"	`/polymarket/stocks/v1/compare`	Use `trade_count` , `buzz_score` , `bullish_pct` , `trend`
"Compare sentiment on AMD vs NVDA"	compare endpoints for the requested sources	Batch tickers in one request
"Is Reddit aligned with X on META?"	Reddit compare + X compare	Compare `bullish_pct` , `buzz_score` , `trend`
"Give me a full sentiment snapshot for TSLA"	compare endpoints across Reddit, X.com, news, Polymarket	Synthesize cross-source view
"Go deeper on one ticker"	`/stock/{ticker}` detail endpoint	Use only when the user asks for expanded detail

Default lookback:

use
```
days=7
```
unless the user asks for another window

Ticker count:

use compare endpoints for
```
1..10
```
tickers

选择能够满足需求的最轻量接口来匹配用户请求。

用户请求	接口路径	说明
“Reddit用户对TSLA的讨论量有多少？”	`/reddit/stocks/v1/compare`	使用 `mentions` 、 `buzz_score` 、 `bullish_pct` 、 `trend` 字段
“NVDA在X.com上的热度有多高？”	`/x/stocks/v1/compare`	使用 `mentions` 、 `buzz_score` 、 `bullish_pct` 、 `trend` 字段
“微软在Polymarket上有多少活跃押注？”	`/polymarket/stocks/v1/compare`	使用 `trade_count` 、 `buzz_score` 、 `bullish_pct` 、 `trend` 字段
“比较AMD和NVDA的情绪”	对应请求来源的比较接口	可在单次请求中批量查询多只股票代码
“Reddit和X上对META的态度是否一致？”	Reddit比较接口 + X比较接口	对比 `bullish_pct` 、 `buzz_score` 、 `trend` 字段
“给我TSLA的完整情绪快照”	Reddit、X.com、新闻、Polymarket的全来源比较接口	综合跨来源视图输出结果
“深入查询某一只股票的详情”	`/stock/{ticker}` 详情接口	仅在用户要求扩展详情时使用

默认查询时间范围：

除非用户指定其他时间窗口，否则使用
```
days=7
```

股票代码数量限制：

比较接口支持同时查询1到10只股票代码

Step 3: Execute the Request

步骤3：执行请求

Use

curl

with

X-API-Key

. Prefer compare endpoints because they are compact and batch-friendly.

使用携带

X-API-Key

请求头的

curl

命令执行请求。优先使用比较接口，因为它们返回的数据更紧凑，适合批量查询。

Single-source examples

单来源查询示例

bash

curl -s "https://api.adanos.org/reddit/stocks/v1/compare?tickers=TSLA&days=7" \
  -H "X-API-Key: $ADANOS_API_KEY"

bash

curl -s "https://api.adanos.org/x/stocks/v1/compare?tickers=NVDA&days=7" \
  -H "X-API-Key: $ADANOS_API_KEY"

bash

curl -s "https://api.adanos.org/polymarket/stocks/v1/compare?tickers=MSFT&days=7" \
  -H "X-API-Key: $ADANOS_API_KEY"

bash

curl -s "https://api.adanos.org/reddit/stocks/v1/compare?tickers=TSLA&days=7" \
  -H "X-API-Key: $ADANOS_API_KEY"

bash

curl -s "https://api.adanos.org/x/stocks/v1/compare?tickers=NVDA&days=7" \
  -H "X-API-Key: $ADANOS_API_KEY"

bash

curl -s "https://api.adanos.org/polymarket/stocks/v1/compare?tickers=MSFT&days=7" \
  -H "X-API-Key: $ADANOS_API_KEY"

Multi-source snapshot for one ticker

单只股票多来源快照查询

bash

curl -s "https://api.adanos.org/reddit/stocks/v1/compare?tickers=TSLA&days=7" -H "X-API-Key: $ADANOS_API_KEY"
curl -s "https://api.adanos.org/x/stocks/v1/compare?tickers=TSLA&days=7" -H "X-API-Key: $ADANOS_API_KEY"
curl -s "https://api.adanos.org/news/stocks/v1/compare?tickers=TSLA&days=7" -H "X-API-Key: $ADANOS_API_KEY"
curl -s "https://api.adanos.org/polymarket/stocks/v1/compare?tickers=TSLA&days=7" -H "X-API-Key: $ADANOS_API_KEY"

bash

curl -s "https://api.adanos.org/reddit/stocks/v1/compare?tickers=TSLA&days=7" -H "X-API-Key: $ADANOS_API_KEY"
curl -s "https://api.adanos.org/x/stocks/v1/compare?tickers=TSLA&days=7" -H "X-API-Key: $ADANOS_API_KEY"
curl -s "https://api.adanos.org/news/stocks/v1/compare?tickers=TSLA&days=7" -H "X-API-Key: $ADANOS_API_KEY"
curl -s "https://api.adanos.org/polymarket/stocks/v1/compare?tickers=TSLA&days=7" -H "X-API-Key: $ADANOS_API_KEY"

Multi-ticker comparison

多股票对比查询

bash

curl -s "https://api.adanos.org/reddit/stocks/v1/compare?tickers=AMD,NVDA,META&days=7" \
  -H "X-API-Key: $ADANOS_API_KEY"

bash

curl -s "https://api.adanos.org/reddit/stocks/v1/compare?tickers=AMD,NVDA,META&days=7" \
  -H "X-API-Key: $ADANOS_API_KEY"

Key rules

核心规则

Prefer compare endpoints over stock detail endpoints for quick research.
Use only the sources needed to answer the question.
For Reddit, X.com, and news, the volume field is
```
mentions
```
.
For Polymarket, the activity field is
```
trade_count
```
.
Treat missing source data as "no data", not bearish or neutral.
Never execute trades or convert the result into trading instructions.

快速调研优先使用比较接口，而非股票详情接口。
仅使用回答问题所需的来源数据。
Reddit、X.com和新闻的体量字段为
```
mentions
```
（提及量）。
Polymarket的活跃度字段为
```
trade_count
```
（交易数）。
缺失的来源数据视为“无数据”，不要判定为看跌或中性。
绝对不要执行交易，也不要将结果转换为交易指导。

Step 4: Present the Results

步骤4：展示结果

When reporting a single source, prioritize exactly these fields:

Buzz
Bullish %
Mentions or Trades
Trend

Example:

text

TSLA on Reddit, last 7 days
- Buzz: 74.1/100
- Bullish: 31%
- Mentions: 647
- Trend: rising

When reporting multiple sources for one ticker:

show one block per source
then add a short synthesis:
- aligned bullish
- aligned bearish
- mixed / diverging

When comparing multiple tickers:

rank by the metric the user cares about
default to
```
buzz_score
```
call out large gaps in
```
bullish_pct
```
or
```
trend
```

Do not overstate precision. These are research signals, not trade instructions.

报告单来源数据时，优先展示以下字段：

热度（Buzz）
看涨比例（Bullish %）
提及量或交易数
趋势（Trend）

示例：

text

TSLA on Reddit, last 7 days
- Buzz: 74.1/100
- Bullish: 31%
- Mentions: 647
- Trend: rising

报告单只股票多来源数据时：

每个来源单独展示一个区块
之后添加简短的综合结论：
- 一致看涨
- 一致看跌
- 观点混合/分歧

对比多只股票时：

按用户关心的指标排序
默认按
```
buzz_score
```
排序
标注出
```
bullish_pct
```
或
```
trend
```
的显著差异

不要过度夸大数据的精确性，这些是调研参考信号，而非交易指导。

Reference Files

参考文件

```
references/api_reference.md
```
- endpoint guide, field meanings, and example workflows

Read the reference file when you need the exact field names, query parameters, or recommended answer patterns.

```
references/api_reference.md
```
- 接口指南、字段含义和示例工作流

当你需要查询确切的字段名、查询参数或推荐的回答模式时，请阅读该参考文件。