Welcome to the Kash developer documentation. Build trading bots and agents against the protocol, sign transactions directly on-chain, embed markets in your website, and access real-time market data.Documentation Index
Fetch the complete documentation index at: https://docs.kash.bot/llms.txt
Use this file to discover all available pages before exploring further.
Kash is non-custodial across every surface. User funds always sit in Privy-managed MPC smart accounts that the user controls — Kash never holds keys or funds, on any path. The split below is about who orchestrates execution, not custody.
Pick your surface
REST API
Kash-orchestrated programmatic access at
api.kash.bot. Place trades, manage portfolios, receive HMAC-signed webhooks. API-key authenticated; trades are signed by the user’s own Privy smart account via scoped delegation. Kash backend builds the userop, sponsors gas, and routes bridging. Right surface for bots, agents, and market makers who want managed execution without running infra.Protocol SDK
Self-orchestrated access. Plug in your own signer (EOA, smart account, HSM, Fireblocks), your own RPC, your own bundler — transactions never touch Kash servers. TypeScript and Python implementations with cross-language parity.
CLI
kash — the same primitives as the SDK, packaged as a scripting-friendly command-line client. Ideal for one-offs, CI jobs, shell scripts, and agent integrations.Public Embed API
Read-only public REST surface at
app.kash.bot/api. Drop iframes and market data into websites and articles. No authentication required.Which one do I want?
- Want Kash to orchestrate execution (build trades, sponsor gas, bridge funds) on top of the user’s Privy smart account? → REST API.
- Want to sign and submit transactions entirely with your own infrastructure? → Protocol SDK.
- Want to script flows from a terminal or CI? → CLI.
- Embedding markets in a website for humans? → Public Embed API.
Quick links
REST API Quickstart
Generate a key, place your first trade, receive your first webhook — under 5 minutes.
Protocol SDK Quickstart
Sign your first on-chain trade from an EOA in under 10 minutes.
Embed Quickstart
Embed your first prediction market in 5 minutes.
TypeScript SDK
Typed REST client. Trades, markets, portfolios, webhooks, retries.
Python SDK
Native Python implementation of the Protocol SDK, plus a Hummingbot connector.
API Error Catalogue
Every error code, what it means, and how to recover.
What can you build?
Trading bots & agents
Use the REST API to place trades, monitor portfolios, and react to market events via webhooks. Supports idempotent retries, high-value confirmation gates, and per-key rate limiting.Self-orchestrated trading & market-making
Use the Protocol SDK (TypeScript or Python) to sign and submit transactions yourself against the on-chain AMM with your own signer, RPC, and bundler. Combine with the REST API’s quote endpoint for live pricing, or quote on-chain directly. (Both paths are non-custodial — this one just keeps the entire execution stack in your infra.)Scripting & ops
Use the CLI for shell-driven workflows: list markets, place trades, rotate webhook secrets, redeliver events, decode error codes — all with a stable JSON envelope for piping intojq or agent contexts.
Embed prediction markets
Use the Public Embed API to drop iframes and read-only market data into news sites, financial platforms, or community forums. Markets are read-only — users are directed to X to make predictions.Support
Need help? We’re here for you:Technical Support
Email [email protected] for technical questions
Partnership Inquiries
Contact [email protected] for whitelabeling or revenue sharing