Skip to main content

agi-diy

Python client for api.agi.diy. Lease a VLA policy, run it over the LeRobot remote-inference protocol (zenoh). One call = one token per action in the chunk.

pip install agi-diy
agi login
agi run act/so101 --probe      # first run: "installing lerobot[remote] from source (~2 min, once)…", then the chunks
import agi

with agi.Policy("act/so101") as session:
    actions = session.predict(
        {"observation.state": state, "observation.images.top": top, "observation.images.wrist": wrist},
        task="pick up the cube",
    )  # np.ndarray [action_horizon, dof] — 100×6 for act/so101, 50×6 for smolvla/so101

The key comes from AGI_API_KEY or ~/.agi/credentials (AGI_API_KEY=agi_sk_live_…).

Surface

agi.Policy("act/so101")          # POST /v1/sessions → lease; raises agi.NoSlots / agi.InsufficientCredits / agi.AuthError
session.endpoint                 # "tcp/bore.pub:35706"  (verbatim from the runner; session.encoding = "jpeg")
session.deployment               # "d_…"
session.url                      # "zenoh://bore.pub:35706/d_…"  → strands_robots.Policy(session.url)
session.connect()                # admitted lerobot.remote_inference.RemoteClient
session.predict(obs, task="…")   # one chunk, np.ndarray
session.policy()                 # strands-robots policy: arm.run(session.policy(), seconds=30)
session.rollout_args()           # flags for lerobot-rollout
session.close()                  # DELETE /v1/sessions/:id (also a context manager; atexit ends forgotten leases)
session.detach()                 # keep the lease past process exit
agi.ensure_lerobot()             # install lerobot[remote] now instead of on the first call
agi.models(); agi.me(); agi.usage(); agi.sessions(); agi.health()

CLI (agi or agi-diy, so uvx agi-diy login works): agi login · agi models · agi session act/so101 · agi run act/so101 --probe · agi rollout act/so101 -- --robot.type=so101_follower … · agi usage.

connect(), predict(), agi run and agi rollout speak LeRobot's remote-inference protocol, which is on lerobot main only (PyPI 0.6.1 lacks it, and PyPI forbids git dependencies). The first call installs lerobot[remote] @ git+https://github.com/huggingface/lerobot@d3793b7e into the running interpreter (GIT_LFS_SKIP_SMUDGE=1; uv pip when there is no pip), replaces a transformers outside >=5.4.0,<5.6.0 first, prints one line, and continues. AGI_NO_INSTALL=1 prints the command instead. Python 3.10–3.12 is what lerobot tests on; 3.13+ gets a one-line note. agi rollout runs python -m lerobot.scripts.lerobot_rollout in that same interpreter. The REST part has no dependencies.

Errors subclass agi.Error with .error, .status, .retry_after_s.

Metadata

Release files for agi-diy 0.2.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for agi-diy 0.2.0
File Size Uploaded Provenance
agi_diy-0.2.0.tar.gz 18.4 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for agi-diy 0.2.0
File Interpreter ABI Platform
agi_diy-0.2.0-py3-none-any.whl Python 3 none any Details

Total release size: 33.1 kB

Release files / agi_diy-0.2.0.tar.gz

Download URL agi_diy-0.2.0.tar.gz
Size 18.4 kB
Tags Source
SHA-256 checksum
How to use checksums
71a69d1e8877ace5fce94df41a0c98e264161c07b20490202ef76a787441959f
BLAKE2b-256 checksum
How to use checksums
5c42ad95e4b18ae5ac976ec74790650aa7e9070d879e4a51bba17a02e0dbfa94
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.11

Release files / agi_diy-0.2.0-py3-none-any.whl

Download URL agi_diy-0.2.0-py3-none-any.whl
Size 14.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
619a7361eada351d48e9f0dca19f905042530e017bef52a1e257e6f1568609ae
BLAKE2b-256 checksum
How to use checksums
6d1c50933c31097e1ccb385eecf48ee95e69dc1756a5774fe82f90999b32edb7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.11

Security for agi-diy 0.2.0

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.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page