Skip to content

knowledge: 補 storage_objects 整日下載說明 + 修正 TaiwanOptionTick 名稱 bug#10

Open
linsamtw wants to merge 1 commit into
masterfrom
feature/storage-objects-bulk-download
Open

knowledge: 補 storage_objects 整日下載說明 + 修正 TaiwanOptionTick 名稱 bug#10
linsamtw wants to merge 1 commit into
masterfrom
feature/storage-objects-bulk-download

Conversation

@linsamtw
Copy link
Copy Markdown
Contributor

@linsamtw linsamtw commented Jun 2, 2026

變更

  1. storage_objects 整日下載說明knowledge/datasets.md(GPT Custom GPT + MCP server 的 single source of truth)為 5 個支援 bulk download 的 dataset 補上說明 —— TaiwanStockPriceTick / TaiwanStockKBar / TaiwanFuturesTick / TaiwanOptionTick / TaiwanStockTradingDailyReport,含 /api/v4/storage_objects?dataset=&date= endpoint 與 SDK use_object=True,並註明整日下載限 Sponsor Pro(與逐檔查詢的 Backer/Sponsor tier 不同)。新增的三個(KBar/FuturesTick/OptionTick)註明逐交易日提供、無歷史回補。
  2. 修正 dataset 名稱 bug:原本寫 TaiwanOptionTIck(大寫 I)且有「T 大寫 I 大寫」的誤導註記 → 改為正確的 TaiwanOptionTick。已用 live API 驗證:TaiwanOptionTick 回 HTTP 200(44 萬筆)、TaiwanOptionTIck422 invalid —— 舊文件會讓 GPT/MCP 構造出錯誤請求。

產出物

chatgpt/instructions.txt / chatgpt/knowledge_bundle.mdchatgpt/build_instructions.pyknowledge/*.md 產生(gitignored),已本機重跑驗證:instructions 7986/8000 chars 未超標、bundle 帶入 5 筆 bulk download、無殘留 TaiwanOptionTIck。

相依

storage_objects bulk download 的三個新 dataset 要等 api/financialdata/dataflow 上線且 DAG 產出 parquet 後才有資料;文件描述採「逐交易日、無歷史回補」未誇大。

🤖 Generated with Claude Code

- datasets.md(GPT/MCP single source of truth)為 5 個 dataset 補 Bulk download
  (Sponsor Pro) 說明:TaiwanStockPriceTick / TaiwanStockKBar / TaiwanFuturesTick
  / TaiwanOptionTick / TaiwanStockTradingDailyReport,含 /v4/storage_objects
  endpoint + SDK use_object=True;註明整日下載限 Sponsor Pro(與逐檔查詢 tier 不同)
- 三個新資料集(KBar/FuturesTick/OptionTick)註明逐交易日提供、無歷史回補
- 修正 bug:TaiwanOptionTIck(大寫 I)→ TaiwanOptionTick,並移除誤導性「T 大寫 I
  大寫」說明。已用 live API 驗證 TaiwanOptionTick 回 200、TaiwanOptionTIck 回 422
- chatgpt/{instructions.txt,knowledge_bundle.md} 為 build_instructions.py 產出物
  (gitignored),release 時重新產生即帶入上述變更
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant