npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@stryketrade/sdk

v0.1.28

Published

Public TypeScript SDK for Stryke prediction markets.

Readme

@stryketrade/sdk

Typed infrastructure for Stryke bot developers.

Published as @stryketrade/sdk. Node.js 22 or newer is required.

Anonymous read-only MCP

Connect to the production MCP without a wallet or credentials:

import { StrykeReadOnlyMcpClient } from "@stryketrade/sdk";

const mcp = await StrykeReadOnlyMcpClient.connect();
try {
  const environment = await mcp.getEnvironment();
  const current = await mcp.getCurrentPythMarkets({ symbol: "BTC" });
  const marketId = current.markets[0]?.marketId;
  if (marketId) {
    const market = await mcp.getMarket(marketId);
    const quote = await mcp.previewQuote({
      marketId,
      action: "buy",
      side: "up",
      amount: { value: "0.01", unit: "SOL" },
    });
    console.log({ environment, market, quote });
  }
} finally {
  await mcp.close();
}

Connection fails closed unless the endpoint exposes exactly the four documented tools and marks each one read-only. Tool failures throw StrykeMcpToolError, preserving code, retryable, retryAfterMs, and remediation. Discover market IDs dynamically and never change origin, symbol, source, collateral, or network as an implicit fallback.

Start

From an empty project:

npm init -y
npm install @stryketrade/sdk

Connect to the mainnet API, select one canonical market, and request an executable quote:

import { MarketsClient, QuotesClient, StrykeClient } from "@stryketrade/sdk";

const client = await StrykeClient.connect({
  apiBaseUrl: process.env.STRYKE_API_BASE_URL ?? "https://api.stryketrade.com",
});
const market = await new MarketsClient(client).current("BTC", "five_minute");
const quote = await new QuotesClient(client).get({
  market,
  action: "buy",
  side: "yes",
  amount: "10000", // API-authoritative minimum at time of writing
  maximumSlippageBps: 100,
});

market.intervalLifecycle is the authoritative interval state. Only active and closing markets may be quoted or prepared; upcoming, locked, and closed fail locally with quote_blocked before an API request. Refresh the market list before retrying.

market.reference contains the immutable opening target and its provenance:

  • aligned: the target is linked to the matching Polymarket round;
  • native: the one-minute target is Stryke's own opening reference; and
  • degraded: Polymarket was unavailable at open and Stryke locked its documented fallback target. Check fallbackReason.

Strategies that compare venues must require aligned; do not treat degraded as a Polymarket observation. Enabled market symbols are advertised by client.capabilities.assets, so MarketsClient can accept newly configured assets without an SDK release. A missing symbol is rejected before discovery.

Inspect quote.closingProtection.phase and effectiveFeeBps. closing quotes remain executable at the returned fee. locked and expired are returned as non-retryable quote_blocked errors; missing or unknown policy fields fail closed as incompatible API data.

Successful quotes are accepted only for the SDK's supported programId and mathVersion. Use normalizedSideProbabilityBps for market/strategy comparisons and averageExecutionPriceBps for the sized trade. Canonical grossAmount, feeAmount, netAmount, sharesIn, sharesOut, and post-trade side state remain integer strings so no precision is lost.

To exit a position, pass the exact raw side balance to sellAvailable. It either returns a quote for that entire balance or throws a typed error; it never silently reduces the sell and leaves residual shares. A retryable failure may be retried on a later loop tick with a freshly read balance and market.

Use the returned market and quote unchanged with TransactionsClient. Simulate before wallet approval, then submit, confirm, and reconcile the same stable action ID. Use PositionsClient and its API-authoritative terminal action to claim or refund; do not infer settlement locally.

There are two distinct non-winning recovery operations. When the API marks a position refundable with a positive authoritative amount and a valid underfunded or zero-winner reason/deadline, terminalActionFor(position) returns refund; prepare it with TransactionsClient.prepareTerminal. The SDK never infers collateral refund eligibility from market conditions.

After the deployed program has no remaining winning/refundable entitlement, a wallet-owned position account can separately expose cleanup_available. A losing-side token balance may remain and does not by itself block account close. Check positionCleanupAvailable(position), then call new CleanupClient(client, rpc).prepareAll(owner, "SOL"). Review and execute each returned transaction through the same dedicated owner signer. The client accepts only close_user_position instructions from the compatible program and requires signer, fee payer, rent recipient, and requested owner to agree.

The cleanup plan reports recoverable position rent and estimated network fees separately. It does not describe shared market-series or strike-market initialization rent as wallet-recoverable. positionCleanupAvailable uses the API-authored selfCloseAvailable flag and same-owner rent recipient. The minimal program has no cleanup grace period, so the SDK does not invent a timestamp or zero-total-share gate. Transaction preparation revalidates the live account state and returns only a reviewed close_user_position instruction. Each materialized transaction retains the authoritative cleanup item and market identity for its chunk so a consumer can match the chosen position rather than blindly executing the first close_all chunk.

For the fastest safe introduction, install and run the reference bot:

npm install @stryketrade/reference-bot
npx stryke-reference-bot doctor --profile=paper
npx stryke-reference-bot --profile=paper

Signed execution requires a separately funded wallet adapter plus every explicit live gate. Mainnet is the default; devnet remains compatible when the API advertises cluster: "devnet". Private keys never belong in SDK configuration or logs.

Typed errors

All public SDK failures use StrykeSdkError and one of these stable codes:

  • configuration and compatibility: configuration, compatibility, validation, unsupported_asset, unsupported_expiry, api_response;
  • read and quote: source_unavailable, source_stale, quote_blocked;
  • transaction and wallet: intent_mismatch, wallet_rejected, simulation_failed, submission_failed, confirmation_timeout, confirmation_unknown, blockhash_expired, duplicate_action; and
  • position and resolution: position_state, claim_state.

retryable distinguishes transient failures. Error context is deliberately bounded and strips credentials, API keys, signatures, signed transactions, and raw payloads.

Market and position lifecycle evidence uses stryke.pilotLifecycle.v1. Normalized state is always accompanied by the raw status, raw reason, observation timestamp, and optional observed slot.

For the complete paper-to-live quickstart, configuration, and error recovery, see https://github.com/dannydoritoeth/stryke-sdk.