{
  "markdown": "# Chipzen SDK\n\n> **🟢 Chipzen is in open beta — open to all.** Sign up and submit a bot at [chipzen.ai](https://chipzen.ai), or join the community on [Discord](https://discord.gg/5JNGkT9Dh).\n\n\nThe Chipzen SDK provides everything a developer needs to build a bot\nfor the [Chipzen](https://chipzen.ai) AI poker competition platform:\nthe **wire protocol spec**, **client libraries** (Python, JavaScript,\nRust starters), a **reference bot**, and the **developer manual**.\n\n## What this is\n\n- Client libraries + scaffolding for connecting a bot to Chipzen over\n  the two-layer WebSocket protocol.\n- The protocol specification (Layer 1 transport, Layer 2 poker game\n  state).\n- A protocol test fixture and reference bot you can read in 40 lines.\n- Developer-facing docs for packaging your bot as a container image\n  and getting it through the upload + review pipeline.\n\n## What this is NOT\n\nThis SDK is for **packaging + protocol conformance**. It is **NOT** for\ntuning bot strategy.\n\nThe SDK gives you three things and nothing else:\n\n1. A protocol adapter so your bot speaks the Chipzen wire protocol\n   without you hand-rolling WebSockets.\n2. A `chipzen-sdk validate` command that confirms your bot will be\n   accepted by the upload pipeline (size, imports, sandbox-blocked\n   modules, decide() timeout sniff, optional protocol-conformance smoke\n   test against an in-process mock server).\n3. Per-language Dockerfile patterns that produce IP-protected images in\n   the format the Chipzen platform expects.\n\nIt does **not** include a local match simulator, a hand evaluator, an\nopponent pool, or a way to measure your bot's win rate locally. Bot\nstrength testing happens after upload — the Chipzen platform runs\ncomprehensive bot-vs-bot evaluation as part of the submission pipeline.\n\n## Quickstart\n\nThe 10-minute walkthrough -- build the reference check-fold bot, tweak\none line of `decide()`, upload it, play it -- lives in\n[`docs/QUICKSTART.md`](docs/QUICKSTART.md).\n\nAfter the quickstart, read [`docs/DEV-MANUAL.md`](docs/DEV-MANUAL.md)\nfor the full developer manual: SDK reference, protocol details, testing\nharness, debugging surfaces, performance budgets, containerization,\nand troubleshooting.\n\n**Working with a coding agent.** Two sets of copy-pasteable prompts you\nhand to a coding agent (Claude Code, Codex, Cursor, …):\n\n- [`docs/BUILDING-WITH-AI-AGENTS.md`](docs/BUILDING-WITH-AI-AGENTS.md) —\n  starting from nothing. Gets you from an empty directory to a bot that\n  passes `chipzen-sdk validate`, then a few strategy variations\n  (tight-aggressive, pot-odds, position-aware) to build on.\n- [`docs/PACKAGING-WITH-AI-AGENTS.md`](docs/PACKAGING-WITH-AI-AGENTS.md) —\n  already have a bot and short on time. The agent does the packaging for\n  you, either producing an upload-ready Docker image or wiring up the\n  remote-play API path.\n\n## Layout\n\n```\nchipzen-sdk/\n  packages/        Per-language SDK packages (Python, JavaScript,\n                   Rust). Each ships a Bot adapter, a validate CLI /\n                   library, and an IP-protected Dockerfile recipe. All\n                   three are published (alpha): Python on PyPI as\n                   `chipzen-bot`, JavaScript on npm as `@chipzen-ai/bot`,\n                   Rust on crates.io as `chipzen-bot` (library) +\n                   `chipzen-sdk` (CLI). Each package also ships its own\n                   IP-protected starter under packages/<lang>/starters/.\n  starters/        Raw-WebSocket protocol-reference scaffolds (one per\n                   language) that talk the two-layer protocol directly,\n                   no SDK dependency — read these to understand the wire\n                   format. For day-to-day bot development use the\n                   SDK-based starters under packages/<lang>/starters/\n                   instead. (The Python entry here now just points at\n                   packages/python/starters/python/.)\n  examples/        Worked examples. reference-bot/ is the smallest\n                   possible Chipzen bot (~40 LOC) — read this first.\n  docs/            QUICKSTART, DEV-MANUAL, the protocol spec, and the\n                   PORTING-BETWEEN-SDKS cheat-sheet for translating a\n                   bot between the Python, JavaScript, and Rust SDKs.\n  docs/protocol/   Layer 1 (TRANSPORT-PROTOCOL.md) + Layer 2\n                   (POKER-GAME-STATE-PROTOCOL.md). Authoritative.\n```\n\n## Where to file issues\n\n- **SDK / starters / protocol bugs** -> open an issue here on\n  [chipzen-ai/chipzen-sdk](https://github.com/chipzen-ai/chipzen-sdk/issues).\n- **Platform / matchmaking / account / billing / Clerk auth issues**\n  -> email `support@chipzen.ai` or post in our Discord. The SDK repo's\n  issue templates intentionally route platform questions away from\n  here so SDK / protocol signal stays clean.\n\n## Contributing\n\nYes please. See [`CONTRIBUTING.md`](CONTRIBUTING.md) for the contribution\nflow, including the **Developer Certificate of Origin** sign-off that\nevery commit needs (`git commit -s` adds the trailer). Pull requests\nrun a fast CI matrix (lint + DCO check + protocol test fixture) for\neach starter language.\n\n## License\n\n[Apache License 2.0](LICENSE). The Apache 2.0 NOTICE file is at\n[`NOTICE`](NOTICE).\n\n## Source-of-truth note\n\nThis repo is the **canonical home of the Chipzen SDK**. Some SDK code\nalso lives in the (currently private) Chipzen platform repo, which is\nthe platform's source of truth for everything else; that mirror exists\nbecause the SDK was originally developed alongside the platform and is\nin the process of being fully separated. All external development —\nissues, PRs, releases — happens here.\n",
  "bytes": 5628,
  "sha": "75ffda41145fd9ae9166dd23e355f5696564999c623553792e7efbca04f9a5db",
  "repo_slug": "chipzen-ai/chipzen-sdk",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_chipzen_ai_chipzen_mcp_4fe6eb13/readme"
}