@denpa/sdk
import { DenpaClient } from "@denpa/sdk";
const denpa = new DenpaClient({ baseUrl: "https://denpa.ai", apiKey: "dk_…" });The SDK is a thin, typed layer over the REST contract. It adds nothing the API does not do; it saves you the shapes.
Entry points
Section titled “Entry points”| Import | What |
|---|---|
@denpa/sdk | DenpaClient, types (Signal, PartnerChannel, …), StationsApi, programQuery |
@denpa/sdk/react | hooks for React clients (useProgramClock, …) |
@denpa/sdk/signal | SignalModel and the signal threshold constants |
@denpa/sdk/connection | DreambothSignal — the legacy reconnecting WebSocket client — and its event types (PrimeEvent, LeaderboardUpdate, SignalUpdate, ChatMessage, VolatilityUpdate); also re-exported from the root |
Defaults
Section titled “Defaults”baseUrl— the hub,https://denpa.ai, for market pages, binding, overlay, receipts, wire, situations, program.DENPA_API_URL/DENPA_WS_URL— the Hono API service for the categorised feed, AURA and realtime.- Every read resolves to a well-formed empty value rather than throwing; render
NO SIGNAL.
Status
Section titled “Status”The SDK is a workspace package (packages/sdk, 0.2.0, private). There is no npm publish yet; standalone forks use the REST endpoints directly (Fork Zero is the reference). If you are asked to “wire the SDK” from outside the monorepo, use REST.