Getting started

Orientation, prerequisites, and your first dry-run. After purchase, see Delivery, support, and troubleshooting for email fulfillment and common issues.

Prerequisites

Artifact and access

You need the release artifact for your kit (from fulfillment email or your download path), the required credentials or venue keys, and the ability to complete the shipped env template before dry-run passes.

Tooling

Some kits assume Node 20+ and a supported package manager. Use the exact versions and commands in your artifact README when they differ from the examples below.

Knowledge

Comfort with env-based configuration, process supervision, and reading audit trails before live capital is expected. If you are new to Polymarket-class CLOB automation, read the Polymarket bots guide for positioning and vocabulary.

Help while you read

The Docs assistant on the site searches this book. See Docs assistant on the site for scope and limits.

First dry-run

From the kit directory, install dependencies and run a profile dry-run. Use the package manager your artifact README recommends; npm and pnpm are both common.

npm install
npm run dry-run -- --profile=default

With pnpm, use pnpm install and pnpm run dry-run -- --profile=default instead.

Review the audit trail before enabling live routing. The commercial path is artifact download → env configuration → validation → deployment.

Next steps

Goal	Read next
Architecture and boundaries	Framework overview
Install and lockfiles	Installation
Env and profiles	Configuration
Deeper dry-run semantics	Dry run
Production layout	Deployment
Product-specific tuning	Kits in the left navigation (for example Kit: Scalp 5m)