Yann Long

iFind http API

数据分析v1.0.0
作者:Yann Long更新于 2026-05-11ifind@clawhub_yannlong/ifind
竞品分析

据 AlphaMoat 统计,截至 2026-09,iFind http API 累计下载 1,574 次、获 1 个星标,在全部 5,078 个 AI 技能中排名第 4,722 位,在「数据分析」分类(399 个)中排名第 371 位。

累计安装
141
累计下载
1,574
星标
1
全站排名
#4,722
全站前 93% · 「数据分析」前 93%
平台累计安装累计下载星标评论
ClawHub ↗301,10312
SkillHub ↗1411,5741—

各平台的计数口径不同,统计时间不一致。

这个技能是做什么的

接口覆盖行情、宏观、基金、日历、报告和组合等信息。请求前应核验 API 端点、权限范围及 refresh token 的安全存储;保护令牌,并对数据来源和时间戳进行复核,避免将结果当作个性化投资建议。 需要 Python requests 和已授权 refresh token;核对接口及查询范围,避免泄露凭据。

资料发布于 2026-10-29

可以用来做什么

  • 查询金融与宏观数据
  • 获取基金、日历或报告信息
  • 整理组合相关数据

什么时候用

  • 需要复用本地 iFinD HTTP 封装时
  • 任何 API 请求前确认授权和令牌存储,并在引用数据时核对来源与时间

示例提示词

以下是根据技能文档生成的示例,不代表实际运行结果。

概述 iFinD 查询能力,并说明调用 API 前和使用结果时需要核验什么。

月度数据趋势

累计下载1,574
2239491,6742026-03 · 累计下载 3232026-05 · 累计下载 6862026-07 · 累计下载 1,0082026-08 · 累计下载 1,1622026-09 · 累计下载 1,57426-0326-09
星标1
0122026-03 · 星标 12026-05 · 星标 12026-07 · 星标 12026-08 · 星标 12026-09 · 星标 126-0326-09

2026-09 起统计方法调整:同名技能按作者分别统计,并覆盖全部技能。图中虚线为调整前的月份,与之后的数据不直接比较,也不计算跨越调整的增长。 该技能有同名的其他版本,调整前的数据归属当前下载量最大的这一个。

月份累计下载环比星标
2026-091,574—1
2026-081,162+15.3%1
2026-071,008—1
2026-05686—1
2026-03323—1

SKILL.md 原文

以下是作者发布的原始文件,按纯文本显示,本站未做修改或审核;其中的链接不可点击,命令请核实后再运行。抓取于 2026-10-23。

4.6 KB · ClawHub v1.0.0
---
name: ifind
description: |
  Use a local Python wrapper around the official iFinD QuantAPI HTTP endpoints on quantapi.51ifind.com. Use when the user wants iFinD market, macro, fund, code-conversion, calendar, report, or portfolio data through HTTP without downloading third-party binaries. This skill is especially appropriate when a local `ifind_api.py` wrapper or custom iFinD HTTP integration should be reused, and when refresh_token acquisition and secure local storage must be checked before any API call.
---

# iFinD

Use this skill to query iFinD via the local Python wrapper in `scripts/ifind_api.py`.
展开全部(共 130 行)
## Environment preparation

Before first use, verify Python dependencies.

Required runtime dependency:
- `requests`

A pinned dependency file is provided at `scripts/requirements.txt`.

Check quickly with:

```bash
python3 -c "import requests; print(requests.__version__)"
```

If missing, install it before running any API script:

```bash
python3 -m pip install -r scripts/requirements.txt
```

If the environment is externally managed, prefer a virtual environment, but installing `requests` is allowed for this skill when needed.

## First rule: confirm refresh_token before querying

Before any data call:

1. Check token status with:
   `python3 scripts/ifind_token_store.py status`
2. If missing, prefer letting the agent obtain it directly from the official site:
   - open `https://quantapi.51ifind.com`
   - log in with the user's existing session, or ask the user to complete login if interactive approval is needed
   - go to the account information page
   - locate the `refresh_token`
3. Store it only through:
   `python3 scripts/ifind_token_store.py set --token '<TOKEN>'`
4. Only fall back to asking the user to provide the token if the browser path is unavailable or login cannot be completed.

Never ask the user to paste shell commands that would echo the token back into chat. Never print the token after storing it.

## Preferred token acquisition workflow

Prefer this order:

1. Browser login to `https://quantapi.51ifind.com` and read the token from account information
2. iFinD 超级命令客户端 → 工具 → `refresh_token` 查询
3. Ask the user directly only as a fallback

If browser automation is used, keep the flow minimal and do not browse unrelated pages. Once the token is found, store it immediately and stop exposing it in further output.

## Token storage policy

- Storage path: `~/.openclaw/skills/ifind/credentials.json`
- File permission target: owner read/write only (`600` on POSIX)
- The store script writes the file and tightens permissions automatically.
- The request script reads the refresh_token from that file unless `IFIND_REFRESH_TOKEN` is already present in the environment.
- Prefer the stored token over hardcoding tokens into code or notes.

## Quick workflow

### 1. Verify dependencies and token state

Run:

```bash
python3 -c "import requests; print(requests.__version__)"
python3 scripts/ifind_token_store.py status
```

If `requests` is missing, install it first:

```bash
python3 -m pip install -r scripts/requirements.txt
```

If the token is missing, obtain it through the preferred browser workflow and store it first.

### 2. Choose a calling path

- For direct endpoint calls, use `scripts/ifind_request.py endpoint`
- For common market-data work, use `scripts/ifind_request.py preset`
- For Python integration or patching, read `scripts/ifind_api.py`
- For endpoint details and payload shape, read `references/iFind_API_Reference.md`

### 3. Run the query

Examples:

```bash
python3 scripts/ifind_request.py preset realtime \
  --codes '300033.SZ,600000.SH' \
  --indicators 'open,high,low,latest,changeRatio,volume,amount'

python3 scripts/ifind_request.py preset ohlcv \
  --codes '000300.SH' \
  --startdate '2025-01-01' \
  --enddate '2025-03-01'

python3 scripts/ifind_request.py endpoint get_thscode \
  --payload '{"seccode":"300033","functionpara":{"mode":"seccode","sectype":"","market":"","tradestatus":"0","isexact":"0"}}'
```

## Output discipline

When using returned data in analysis:

- state the endpoint used
- include the symbol universe / code list
- include the requested date range or timestamp
- include the returned `perf`, `dataVol`, or other useful metadata when relevant
- if the API returns an error, surface the error code and message rather than guessing

## References

- `references/iFind_API_Reference.md`: local API wrapper reference and examples from the user
- `references/token-and-storage.md`: refresh_token acquisition and storage procedure
- `scripts/ifind_api.py`: local Python wrapper
- `scripts/ifind_request.py`: CLI for endpoint/preset calls
- `scripts/ifind_token_store.py`: token status/set/remove helper

「数据分析」分类下的热门技能

数据月份:2026-09 · 下载/星标/安装数聚合自公开技能注册库(ClawHub、SkillHub),按月更新。口径说明见数据方法。