runs helpers for legacy validation flows.
Python
Sync and async support. Works with any Python 3.10+ project.
TypeScript
Zero dependencies. Uses native fetch (Node 18+).
What the SDKs cover
Both SDKs wrap the same core namespaces:| Namespace | What it does |
|---|---|
| Sandbox runs | Deploy app code plus selected twins. Inspect sandbox URLs and logs. |
| Twin runs | Provision standalone digital twin environments, extend TTL, lock public access, or tear them down. |
| Tests | Create, list, fetch, and run saved browser tests. |
| Test runs | Start ad hoc browser runs, rerun them, and poll for completion. |
| Twins | Legacy twin quickstart helpers on the older /validate/twins/... routes. |
| Scenarios | Create reusable twin seed configurations and reuse them across runs. |
| Runs | Legacy validation-run helpers kept for older /validate/... workflows. |
Authentication
All SDK methods require an API key. Get one by running:Example projects
Both SDK repositories include reference tests and package-level examples for the current supported workflows — release gating, scenario creation, seeded twin provisioning, and standalone twin provisioning.| Example | What it does |
|---|---|
| Validate staging release | Run browser validation against staging and exit non-zero if it fails — drop it into CI to gate releases. |
| Create checkout scenario | Build a reusable scenario with seed data and tags so your team can replay the same flow across runs. |
| Provision twins from a scenario | Start a seeded twin session from a saved scenario and print the resulting base_urls. |
| Provision checkout twins | Spin up disposable service twins (e.g. Stripe), wait until ready, and print the URLs and env vars. |
Python examples
uv run python examples/validate_staging_release.pyTypeScript examples
npx tsx examples/validate_staging_release.tsBase URL
Both SDKs default tohttps://app.argalabs.com. Override this if you’re targeting a different environment:

