SDK access and downloads
Understand the package, access requirements and integration boundaries.
Access requirements
Sign in and activate an evaluation before downloading the SDK or browser example. Viewer accounts can inspect existing workspace resources but cannot activate an evaluation. An expired evaluation requires CEBS assistance; repeatedly selecting Activate does not restart its clock.
Package contents
| Package | Contents | Purpose |
|---|---|---|
| Evaluation SDK | Versioned browser runtime, OCR workers, public OCR models and third-party license notices | Self-hosted functional evaluation |
| Browser example | HTML, JavaScript, CSS and setup instructions | Capture lifecycle and integration starting point |
| Production entitlement | Issued only through the approved commercial process | Not included in either development download |
Directory layout
your-project/
index.html
app.js
example.css
sdk/
0.2.0/
sdk.js
ocr.worker.js
onnx/
models/
licenses/Keep the supplied runtime layout intact. The SDK checks pinned runtime and model hashes. Mixing files from different builds can cause integrity failures. Keep license notices with redistributed assets.
Loading and caching
Load sdk.js from your own origin and point assetBaseUrl to its directory. Prepare the reader on page load to reduce waiting after the user starts capture. Preparation does not request the camera. Cache versioned assets according to your deployment policy and release the prepared reader when the page no longer needs it. SDK binaries and public OCR weights contain no account data; do not treat obscuring their URLs as a production license control.
Production licensing
A portal evaluation, a configured domain and a commercial quote are distinct from a signed production entitlement. Confirm authorized origins, edition, environments, expected volume, support and renewal terms with CEBS. No production approval is issued automatically by this portal.