Search, quote and buy sit in the same server as the wallet and the API key flow, so a strategy runs end to end — on infrastructure you are running yourself.
A self-hosted Node server that routes Kalshi trades through the DFlow protocol on Solana. It covers the whole path: getting an API key, generating or importing a Solana wallet, finding markets, quoting them, and placing the trade.
- kalshi_search_markets, kalshi_get_events, kalshi_get_event and kalshi_get_market find a market by search or by working down from events
- kalshi_get_quote returns the price you would get; kalshi_get_live_data returns the market's live state
- kalshi_buy_yes and kalshi_buy_no take either side of a contract
- Wallet handling: kalshi_get_wallet_info, kalshi_get_wallet_status, kalshi_get_balances and kalshi_get_deposit_address
- Bring your own key or take it back out: kalshi_import_private_key and kalshi_export_private_key
- kalshi_signup and kalshi_request_api_key handle the account and key from inside the same session
You host it yourself: the vendor has wound its platform down, the public endpoints are gone, and the project is no longer maintained. Running an instance needs Node, a PostgreSQL connection string and a hex encryption key for the stored wallets. Keys for DFlow and Jupiter, a Solana RPC endpoint, an admin key and the listening port are all optional — the Jupiter key is what enables the swap tools.
One command — npx -y @quantish/kalshi-server