LiteRegistry tool clients
The canonical client API is literegistry_tool_client. Each service client has its
own module and all clients share the same asynchronous ToolClient transport.
| Client | Dedicated module | Purpose |
|---|---|---|
RemoteCodeExecutionClient |
literegistry_tool_client.code |
Remote Python execution |
TerminalExecutionClient |
literegistry_tool_client.terminal |
Restricted terminal pipelines |
PodmanExecutionClient |
literegistry_tool_client.podman |
Stateful container sessions |
SearchClient |
literegistry_tool_client.search |
Search queries |
FetchClient |
literegistry_tool_client.fetch |
URL extraction via Jina or LiteRegistry |
WebTerminalExecutionClient |
literegistry_tool_client.webterminal |
Browse/fetch plus terminal pipelines |
JudgeClient |
literegistry_tool_client.judge |
Rubric judging |
RewardModelClient |
literegistry_tool_client.reward_model |
Sequence classification |
SubmitToolClient |
literegistry_tool_client.submission |
Rollout-local rubric submissions |
Import from the package for normal use:
from literegistry_tool_client import (
FetchClient,
SearchClient,
TerminalExecutionClient,
WebTerminalExecutionClient,
)
terminal = TerminalExecutionClient()
fetch = FetchClient(
local_search_server_url="http://127.0.0.1:1212/search",
local_search_model_path="fetch",
)
webterminal = WebTerminalExecutionClient(terminal, fetch)
search = SearchClient(model_path="search")
Install independently (only aiohttp is required), or through LiteRegistry:
pip install literegistry-tool-client
pip install 'literegistry[tool_client]'
This package has no dependency on PrimeBeaker, Verifiers, Torch, or the
LiteRegistry server. It also exports AssetStore and WebAssetStore for
rollout-local state. The existing literegistry-podman-client package remains
available for its separate low-level Podman session API; PodmanExecutionClient
here implements the common ToolClient.execute() interface.
PrimeBeaker's primebeaker.client and primebeaker.clients imports remain
compatibility facades for these same classes.
Metadata
Release files for literegistry-tool-client 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| literegistry_tool_client-0.1.1.tar.gz | 17.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| literegistry_tool_client-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 39.9 kB
Release files / literegistry_tool_client-0.1.1.tar.gz
| Download URL | literegistry_tool_client-0.1.1.tar.gz |
|---|---|
| Size | 17.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0d3d38e793bee5fdb33a456387243ade43d6ec4810c1d3c7ab887bf13ca9ffe6
|
|
BLAKE2b-256 checksum How to use checksums |
0b38bb4a245729aca85e0b4d2855448a7da4f7cb20515f38b1a18a8e4b1976d0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 11, 2026.
Transparency logRelease files / literegistry_tool_client-0.1.1-py3-none-any.whl
| Download URL | literegistry_tool_client-0.1.1-py3-none-any.whl |
|---|---|
| Size | 22.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e3eacf8e264375b36c3816d62e1829a1cd1f1030805cf4ef0037534a5ff908a6
|
|
BLAKE2b-256 checksum How to use checksums |
ba300331c72504f4a5043b2ea9945bbbfc2aa37a447998a6a82e77a233d376a8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 11, 2026.
Transparency log