Pp Kalshi

<!-- GENERATED FILE — DO NOT EDIT.
     This file is a verbatim mirror of library/payments/kalshi/SKILL.md,
     regenerated post-merge by tools/generate-skills/. Hand-edits here are
     silently overwritten on the next regen. Edit the library/ source instead.
     See the repository agent guide, section "Generated artifacts: registry.json, cli-skills/". -->

Kalshi — Printing Press CLI

Prerequisites: Install the CLI

This skill drives the kalshi-pp-cli binary. You must verify the CLI is installed before invoking any command from this skill. If it is missing, install it first:

1. Install via the Printing Press installer. It defaults binaries to $HOME/.local/bin on macOS/Linux and %LOCALAPPDATA%\Programs\PrintingPress\bin on Windows:

   npx -y @mvanhorn/printing-press-library install kalshi --cli-only

2. Verify: kalshi-pp-cli --version
3. Ensure the reported install directory is on $PATH for the agent/runtime that will invoke this skill.

If the npx install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.6 or newer). This installs into $GOPATH/bin (default $HOME/go/bin), so add that directory to $PATH instead:

go install github.com/mvanhorn/printing-press-library/library/payments/kalshi/cmd/kalshi-pp-cli@latest

If --version reports "command not found" after install, the runtime cannot see the binary directory on $PATH. Do not proceed with skill commands until verification succeeds.

Every Kalshi feature, plus a local SQLite store that records market prices on every sync — so movers, correlations, and price history work offline. Honest about read-only vs read/write keys, with --dry-run on every mutator and a global --read-only safe-mode lock for newsroom and bot deployments.

When to Use This CLI

Reach for kalshi-pp-cli when an agent needs price-over-time or category-level analytics on Kalshi markets — the public API only returns current prices and flat positions, so historical and aggregated questions require the local snapshot store. Use it for daily portfolio reconciliation, signal discovery via correlation across markets, and safe scripting against read-only API credentials.

Unique Capabilities

These capabilities aren't available in any other tool for this API.

Local state that compounds

• portfolio attribution — See your realized P&L broken down by market category and series over any time window — answer 'did politics actually make money this quarter?' in one command.

  Use when an agent needs realized P&L sliced by Kalshi taxonomy — the API returns flat fills and settlements; this command joins them with the category metadata required to attribute correctly.

  kalshi-pp-cli portfolio attribution --since 2026-01-01 --by category --json

• markets history — Show how a market's yes/no price moved over time, with a sparkline rendering — built from snapshots captured by every markets sync.

  Use when an agent asks 'how did this market move' or needs price-over-time for backtesting; the API only returns current price.

  kalshi-pp-cli markets history KXPRES-2028-DJT --since 2026-04-01 --sparkline

• portfolio winrate — Calculate your win/loss ratio, expected value, and ROI across all settled positions, optionally sliced by category.

  Use when an agent evaluates trading-strategy performance; no Kalshi tool computes this.

  kalshi-pp-cli portfolio winrate --category sports --since 2026-01-01 --json

• portfolio calendar — See upcoming settlements with your positions, expected payouts, and category breakdown over the next N days.

  Use when an agent needs to plan around upcoming settlements; the API surfaces positions and event expiries on different endpoints.

  kalshi-pp-cli portfolio calendar --days 14

• markets movers — Find markets with the biggest price swings since the last sync — sorted by absolute delta or by volume change.

  Use when an agent needs to surface notable market activity; the API has no 'recent movers' endpoint.

  kalshi-pp-cli markets movers --window 24h --category politics --json

• markets correlate — Compute Pearson correlation of two markets' price histories — find correlated events for hedging or signal discovery.

  Use when an agent investigates cross-market relationships; no API endpoint or other tool computes correlation across Kalshi markets.

  kalshi-pp-cli markets correlate KXFEDFUNDS-26FEB KXCPI-26FEB --window 30d --json

• portfolio exposure — Break down total exposure by category with concentration warnings when any bucket exceeds a configurable risk threshold.

  Use when an agent needs portfolio-level risk; the API doesn't aggregate exposure by Kalshi taxonomy.

  kalshi-pp-cli portfolio exposure --by category --warn-threshold 0.4 --json

• watch diff — Maintain a local watchlist of tickers; watch diff shows price/volume change vs the last sync per watched market — Riley's daily-snapshot ritual reduced to one command.

  Use when an agent tracks a stable set of markets across runs; the API has no watchlist concept.

  kalshi-pp-cli watch diff --since 24h

Honest auth

• --read-only — Global env-var/flag lock that blocks every mutating command client-side regardless of which key tier is loaded — pair with --dry-run on every mutator for safe scripting against read-only credentials.

  Use when an agent runs against an unknown Kalshi key tier — the read-only key tier exists and mid-script 403s are common; this surfaces the constraint client-side before the API is hit.

  kalshi-pp-cli --read-only portfolio create-order --ticker KXTEST --side yes --count 1 --yes-price 50 --dry-run

• subaccounts rollup — Aggregate positions, fills-today, balance, and exposure-by-category across every subaccount you can see — household view of risk and resting orders.

  Use when an FCM-tier user needs aggregate risk across subaccounts; no Kalshi tool surfaces a household view.

  kalshi-pp-cli subaccounts rollup --by category --json

Command Reference

account — Manage account

• kalshi-pp-cli account get-api-limits — Endpoint to retrieve the API tier limits associated with the authenticated user.
• kalshi-pp-cli account get-endpoint-costs — Lists API v2 endpoints whose configured token cost differs from the default cost. Endpoints that use the default...

api-keys — API key management endpoints

• kalshi-pp-cli api-keys create — Endpoint for creating a new API key with a user-provided public key. This endpoint allows users with Premier or...
• kalshi-pp-cli api-keys delete — Endpoint for deleting an existing API key. This endpoint permanently deletes an API key. Once deleted, the key can...
• kalshi-pp-cli api-keys generate — Endpoint for generating a new API key with an automatically created key pair. This endpoint generates both a public...
• kalshi-pp-cli api-keys get — Endpoint for retrieving all API keys associated with the authenticated user. API keys allow programmatic access to...

communications — Request-for-quote (RFQ) endpoints

• kalshi-pp-cli communications accept-quote — Endpoint for accepting a quote. This will require the quoter to confirm
• kalshi-pp-cli communications confirm-quote — Endpoint for confirming a quote. This will start a timer for order execution
• kalshi-pp-cli communications create-quote — Endpoint for creating a quote in response to an RFQ
• kalshi-pp-cli communications create-rfq — Endpoint for creating a new RFQ. You can have a maximum of 100 open RFQs at a time.
• kalshi-pp-cli communications delete-quote — Endpoint for deleting a quote, which means it can no longer be accepted.
• kalshi-pp-cli communications delete-rfq — Endpoint for deleting an RFQ by ID
• kalshi-pp-cli communications get-id — Endpoint for getting the communications ID of the logged-in user.
• kalshi-pp-cli communications get-quote — Endpoint for getting a particular quote
• kalshi-pp-cli communications get-quotes — Endpoint for getting quotes
• kalshi-pp-cli communications get-rfq — Endpoint for getting a single RFQ by id
• kalshi-pp-cli communications get-rfqs — Endpoint for getting RFQs

events — Event endpoints

• kalshi-pp-cli events get — Get all events. This endpoint excludes multivariate events. To retrieve multivariate events, use the GET...
• kalshi-pp-cli events get-eventticker — Endpoint for getting data about an event by its ticker. An event represents a real-world occurrence that can be...
• kalshi-pp-cli events get-multivariate — Retrieve multivariate (combo) events. These are dynamically created events from multivariate event collections....

exchange — Exchange status and information endpoints

• kalshi-pp-cli exchange get-announcements — Endpoint for getting all exchange-wide announcements.
• kalshi-pp-cli exchange get-schedule — Endpoint for getting the exchange schedule.
• kalshi-pp-cli exchange get-status — Endpoint for getting the exchange status.
• kalshi-pp-cli exchange get-user-data-timestamp — There is typically a short delay before exchange events are reflected in the API endpoints. Whenever possible,...

fcm — FCM member specific endpoints

• kalshi-pp-cli fcm get-fcmorders — Endpoint for FCM members to get orders filtered by subtrader ID. This endpoint requires FCM member access level and...
• kalshi-pp-cli fcm get-fcmpositions — Endpoint for FCM members to get market positions filtered by subtrader ID. This endpoint requires FCM member access...

historical — Manage historical

• kalshi-pp-cli historical get-cutoff — Returns the cutoff timestamps that define the boundary between live and historical data. ## Cutoff fields -...
• kalshi-pp-cli historical get-fills — Endpoint for getting all historical fills for the member. A fill is when a trade you have is matched.
• kalshi-pp-cli historical get-market — Endpoint for getting data about a specific market by its ticker from the historical database.
• kalshi-pp-cli historical get-market-candlesticks — Endpoint for fetching historical candlestick data for markets that have been archived from the live data set. Time...
• kalshi-pp-cli historical get-markets — Endpoint for getting markets that have been archived to the historical database. Filters are mutually exclusive.
• kalshi-pp-cli historical get-orders — Endpoint for getting orders that have been archived to the historical database.
• kalshi-pp-cli historical get-trades — Endpoint for getting all historical trades for all markets. Trades that were filled before the historical cutoff are...

incentive-programs — Incentive program endpoints

• kalshi-pp-cli incentive-programs — List incentives with optional filters. Incentives are rewards programs for trading activity on specific markets.

kalshi-trade-manual-search — Manage kalshi trade manual search

• kalshi-pp-cli kalshi-trade-manual-search — Retrieve available filters organized by sport. This endpoint returns filtering options available for each sport,...

kalshi-trade-manual-search-2 — Manage kalshi trade manual search 2

• kalshi-pp-cli kalshi-trade-manual-search-2 — Retrieve tags organized by series categories. This endpoint returns a mapping of series categories to their...

live-data — Live data endpoints

• kalshi-pp-cli live-data get — Get live data for multiple milestones
• kalshi-pp-cli live-data get-by-milestone — Get live data for a specific milestone.
• kalshi-pp-cli live-data get-game-stats — Get play-by-play game statistics for a specific milestone. Supported sports: Pro Football, College Football, Pro...

markets — Market data endpoints

• kalshi-pp-cli markets batch-get-candlesticks — Endpoint for retrieving candlestick data for multiple markets. - Accepts up to 100 market tickers per request -...
• kalshi-pp-cli markets get — Filter by market status. Possible values: unopened, open, closed, settled. Leave empty to return markets...
• kalshi-pp-cli markets get-orderbooks — Endpoint for getting the current order books for multiple markets in a single request. The order book shows all...
• kalshi-pp-cli markets get-ticker — Endpoint for getting data about a specific market by its ticker. A market represents a specific binary outcome...
• kalshi-pp-cli markets get-trades — Endpoint for getting all trades for all markets. A trade represents a completed transaction between two users on a...

milestones — Milestone endpoints

• kalshi-pp-cli milestones get — Minimum start date to filter milestones. Format: RFC3339 timestamp
• kalshi-pp-cli milestones get-milestoneid — Endpoint for getting data about a specific milestone by its ID.

multivariate-event-collections — Manage multivariate event collections

• kalshi-pp-cli multivariate-event-collections create-market-in — Endpoint for creating an individual market in a multivariate event collection. This endpoint must be hit at least...
• kalshi-pp-cli multivariate-event-collections get — Endpoint for getting data about multivariate event collections.
• kalshi-pp-cli multivariate-event-collections get-multivariateeventcollections — Endpoint for getting data about a multivariate event collection by its ticker.

portfolio — Portfolio and balance information endpoints

• kalshi-pp-cli portfolio amend-order — Endpoint for amending the max number of fillable contracts and/or price in an existing order. Max fillable contracts...
• kalshi-pp-cli portfolio amend-order-v2 — Endpoint for amending the price and/or remaining count of an existing event-market order using the V2...
• kalshi-pp-cli portfolio apply-subaccount-transfer — Transfers funds between the authenticated user's subaccounts. Use 0 for the primary account, or 1-32 for numbered...
• kalshi-pp-cli portfolio batch-cancel-orders — Endpoint for cancelling a batch of orders. The maximum batch size scales with your tier's write budget — see [Rate...
• kalshi-pp-cli portfolio batch-cancel-orders-v2 — Endpoint for cancelling a batch of event-market orders using the V2 response shape. The maximum batch size scales...
• kalshi-pp-cli portfolio batch-create-orders — Endpoint for submitting a batch of orders. The maximum batch size scales with your tier's write budget — see [Rate...
• kalshi-pp-cli portfolio batch-create-orders-v2 — Endpoint for submitting a batch of event-market orders using the V2 request/response shape. The maximum batch size...
• kalshi-pp-cli portfolio cancel-order — Endpoint for canceling orders. The value for the orderId should match the id field of the order you want to...
• kalshi-pp-cli portfolio cancel-order-v2 — Endpoint for cancelling event-market orders using the V2 response shape. Returns `{order_id, client_order_id,...
• kalshi-pp-cli portfolio create-order — Endpoint for submitting orders in a market. Each user is limited to 200 000 open orders at a time.
• kalshi-pp-cli portfolio create-order-group — Creates a new order group with a contracts limit measured over a rolling 15-second window. When the limit is hit,...
• kalshi-pp-cli portfolio create-order-v2 — Endpoint for submitting event-market orders using the V2 request/response shape (single-book bid/ask side and...
• kalshi-pp-cli portfolio create-subaccount — Creates a new subaccount for the authenticated user. Subaccounts are numbered sequentially starting from 1. Maximum...
• kalshi-pp-cli portfolio decrease-order — Endpoint for decreasing the number of contracts in an existing order. This is the only kind of edit available on...
• kalshi-pp-cli portfolio decrease-order-v2 — Endpoint for decreasing the remaining count of an existing event-market order using the V2 request/response shape....
• kalshi-pp-cli portfolio delete-order-group — Deletes an order group and cancels all orders within it. This permanently removes the group.
• kalshi-pp-cli portfolio get-balance — Endpoint for getting the balance and portfolio value of a member. Both values are returned in cents.
• kalshi-pp-cli portfolio get-fills — Endpoint for getting all fills for the member. A fill is when a trade you have is matched. Fills that occurred...
• kalshi-pp-cli portfolio get-order — Endpoint for getting a single order.
• kalshi-pp-cli portfolio get-order-group — Retrieves details for a single order group including all order IDs and auto-cancel status.
• kalshi-pp-cli portfolio get-order-groups — Retrieves all order groups for the authenticated user.
• kalshi-pp-cli portfolio get-order-queue-position — Endpoint for getting an order's queue position in the order book. This represents the amount of orders that need to...
• kalshi-pp-cli portfolio get-order-queue-positions — Endpoint for getting queue positions for all resting orders. Queue position represents the number of contracts that...
• kalshi-pp-cli portfolio get-orders — Restricts the response to orders that have a certain status: resting, canceled, or executed. Orders that have been...
• kalshi-pp-cli portfolio get-positions — Restricts the positions to those with any of following fields with non-zero values, as a comma separated list. The...
• kalshi-pp-cli portfolio get-resting-order-total-value — Endpoint for getting the total value, in cents, of resting orders. This endpoint is only intended for use by FCM...
• kalshi-pp-cli portfolio get-settlements — Endpoint for getting the member's settlements historical track.
• kalshi-pp-cli portfolio get-subaccount-balances — Gets balances for all subaccounts including the primary account.
• kalshi-pp-cli portfolio get-subaccount-netting — Gets the netting enabled settings for all subaccounts.
• kalshi-pp-cli portfolio get-subaccount-transfers — Gets a paginated list of all transfers between subaccounts for the authenticated user.
• kalshi-pp-cli portfolio reset-order-group — Resets the order group's matched contracts counter to zero, allowing new orders to be placed again after the limit...
• kalshi-pp-cli portfolio trigger-order-group — Triggers the order group, canceling all orders in the group and preventing new orders until the group is reset.
• kalshi-pp-cli portfolio update-order-group-limit — Updates the order group contracts limit (rolling 15-second window). If the updated limit would immediately trigger...
• kalshi-pp-cli portfolio update-subaccount-netting — Updates the netting enabled setting for a specific subaccount. Use 0 for the primary account, or 1-32 for numbered...