sharketo-market-intelligence/sharketo-skills

sharketo-python

Use when integrating the Sharketo Python SDK into an application, service, report, notebook or dashboard.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/sharketo-market-intelligence/sharketo-skills --skill sharketo-python

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

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

  1. 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.
  2. 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.
  3. Use application integration for client reuse, stream lifecycle, status refresh and error handling.
  4. 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 dataReference
SPX/NDX compact inventory summariesSDK clients and summary models
SPX/NDX strike contributions, exposure/spot/IV history, session BookmapInventory rendering
Opt-in conditional-price exposure profilesProfiles
SPX/NDX replacement quotesPrices
BTC/ETH current crypto exposure stateCrypto inventory
SPX/NDX/SPY/QQQ cache-only dealer snapshotsDealer Exposures
SPX/NDX expiry-flow latest and selected hourly historyExpiry flow
Bounded daily reconstructed inventory historyDaily history
Full per-asset seasonal analysis and compact seasonal tablesSeasonality
Curated volatility catalog, asset and term-structure snapshotsVolatility
Curated relative-rotation catalog, group and screener snapshotsRRG
Modeled positioning and scenario-flow snapshotCTA Flow
SDK/skill installation, version matching, host discovery or exportInstallation
Portal API key creation or first-time server-side credential configurationFirst-time API key setup
Access failures and sanitized diagnosticsSDK 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.