Delivery, support, and troubleshooting
What to expect after purchase, where documentation and files live, and what to check when something looks wrong.
What you receive after purchase
Standard kits are fulfilled by email to the address used at checkout. That message should include:
A signed license file (
.lic) for offline verificationDownload links or artifact references for your kit
Pointers back to this public documentation (no login required)
Timing is usually within minutes. If your provider shows a completed payment and nothing arrived, use the steps below before changing production config.
Documentation and downloads
Framework install, config, dry-run, deploy
Getting started and Framework chapters in this book
Product-specific kit behavior
Kits in the left navigation of this book, plus your shipped README inside the artifact
License semantics and .lic format
Chat-style search over this book
Optional signed-in tools on the main site (/app) are for convenience (for example downloads and support). They are not required to read this manual or deploy from the emailed artifact.
If the fulfillment email is missing
Check spam and promotions folders for the checkout address.
Confirm the payment completed on the checkout provider.
Contact support on the site with the email used at checkout and approximate time of purchase. Include
licensePublicIdif you already have it from a partial delivery.
License file issues
If the runtime rejects the .lic file:
Confirm you are using the file attached to fulfillment for the correct product.
Follow verification steps in License file format (v1).
Do not run live execution on a failing verification path unless you are in an explicitly documented dev mode.
Getting help
Product and deployment questions: Contact on the marketing site.
Context for Polymarket-class kits: Polymarket bots guide.
For framework changes and release expectations, see Release notes.
Last updated