使用方法
- 复制安装命令,在自己的智能体环境安装前先检查源码包。
- 从原始文档核对所需工具、凭据和支持的宿主。
- 说明输入材料与期望交付物,并对照来源检查输出。
npx skills add https://github.com/sharketo-market-intelligence/sharketo-skills --skill sharketo-python开始前需了解
- 安装不包含模型订阅、API 额度或访问文件的权限。
- 仓库星数和安装量反映活跃情况,不等于独立质量或安全测试。
按源仓库内容呈现,保留标题、案例、代码、表格、链接以及原文引用的演示图片。
Sharketo Python SDK
Developer API access
All SDK data access requires effective Apex access, including live prices and get_access() diagnostics. A usable key or Pro portal/integration access is insufficient. The backend evaluates effective access, including valid existing grants; do not infer it from a billing label or add a client-side plan gate/preflight. For denied access, preserve sanitized capability/plan metadata and follow terminal diagnostics.
Personal-use scope
Developer access covers private, noncommercial applications used only by the subscriber. Work for an employer or client is outside this scope. See personal-use boundaries for hosting, sharing and code publication.
Start from the user's application
- If the SDK is missing or its version is uncertain, follow installation for the matching PyPI release and offline verification. Skill installation alone does not install the SDK.
- Select a family below and read its API and data semantics before coding. For client options, summary models, errors or stream limits, read the relevant section of the SDK reference.
- Use application integration for client reuse, stream lifecycle, status refresh and error handling.
- Check the changed behavior with the application's tests and the relevant guide's offline fixture. For agent-run live checks, follow the validation workflow.
Select a capability
| Requested data | Reference |
|---|---|
| SPX/NDX compact inventory summaries | SDK clients and summary models |
| SPX/NDX strike contributions, exposure/spot/IV history, session Bookmap | Inventory rendering |
| Opt-in conditional-price exposure profiles | Profiles |
| SPX/NDX replacement quotes | Prices |
| BTC/ETH current crypto exposure state | Crypto inventory |
| SPX/NDX/SPY/QQQ cache-only dealer snapshots | Dealer Exposures |
| SPX/NDX expiry-flow latest and selected hourly history | Expiry flow |
| Bounded daily reconstructed inventory history | Daily history |
| Full per-asset seasonal analysis and compact seasonal tables | Seasonality |
| Curated volatility catalog, asset and term-structure snapshots | Volatility |
| Curated relative-rotation catalog, group and screener snapshots | RRG |
| Modeled positioning and scenario-flow snapshot | CTA Flow |
| SDK/skill installation, version matching, host discovery or export | Installation |
| Portal API key creation or first-time server-side credential configuration | First-time API key setup |
| Access failures and sanitized diagnostics | SDK error boundary |
Common boundaries
- Consume complete replacement states instead of handling raw full, delta or tail messages.
- Preserve supplied financial values, classifications, units, signs, provenance and null versus zero. Label application calculations separately.
- Keep source time, publication time, receipt time and transport status separate. If source freshness is unknown, leave it unknown. For calendar-date fields, follow date-only display.
- Keep API keys server-side and out of browser inputs, frontend bundles, notebook cells and outputs, URLs and logs.
- For production defaults or custom environments, follow endpoint configuration.
