rez-python-apiv1.0.0

A VFX studio uses the rez Python API inside a CI system to programmatically resolve software environments for each target platform before running compiles. Each build job constructs a ResolvedContext with the exact request list, inspects success and failure_description to surface solver errors early, and uses get_environ() to launch the compiler with the correct PATH. Because config is read once at import, the CI container pins rez 3.4.0 and imports rez.config only after mounting the studio's config file.

A pipeline TD writes a tool that pre-resolves every shot's environment and serialises it to a .rxt file via context.save(), so render nodes can ResolvedContext.load() it without re-solving. This eliminates minutes of solver time per frame and guarantees that re-renders days later use the same package versions. The tool also calls get_resolve_as_exact_requests() to archive pinned requirements alongside the .rxt for audit.

An internal web tool lets artists paste a request string and see what the resolver chose. The backend calls ResolvedContext(requests) and reads resolved_packages, resolved_ephemerals, get_tools() and which('foo') to render a table of variants, tool paths and environment variables. This is the programmatic equivalent of rez-context --so, but available to users who never open a terminal.

A studio engineering team embeds rez to validate that a requested package set is solvable before allocating expensive licensed software sessions. They construct a context with a timestamp and max_fails limit, and if success is false they show failure_description to the requester instead of tying up a license. Resolved contexts are cached in memory and re-serialised with write_to_buffer() for downstream services.

A game studio's asset validation service imports rez.packages.get_package and rez.resolved_context to confirm that every asset's declared dependencies still resolve against the latest package repository state. It uses Package and Variant objects to inspect .requires and .tools, then performs headless resolves for each asset. Failures block the asset from entering the shared depot, preventing broken dependencies from reaching artists.

Consultancies offer fixed-scope engagements to embed the rez Python API into a studio's existing build, render and asset pipelines. Deliverables include CI resolve wrappers, .rxt baking services and internal inspection dashboards, all tailored to the client's rez version and config layout.

A hosted service runs resolves on behalf of subscribers, exposing the rez Python API through a REST layer. Customers send request strings and receive resolved context JSON, environment dictionaries or downloadable .rxt artifacts without managing their own rez installation or config immutability constraints.

Publishes paid courses, reference architectures and open-core helper libraries that teach teams to drive rez from Python correctly, including the config-read-once caveat and version pinning. Enterprise tiers bundle internal workshops and a private support channel for API questions.