hold-sdk
Python client for Hold My Agent's Arbiter server — gate an agent action behind a human approval with one call:
from hold_sdk import request_approval
if request_approval("Deploy to prod?", severity="high") != "approved":
raise SystemExit("blocked: not approved")
Fail-closed: any timeout, network error, or unconfigured client returns
"denied", never raises.
Making many requests? ArbiterClient reuses one connection:
from hold_sdk import ArbiterClient
client = ArbiterClient(base_url="http://127.0.0.1:8000", agent_token="<agent_token>")
decision = client.request_approval("Restart api service", severity="medium")
- Homepage: https://holdmyagent.com
- Source / issues: https://github.com/holdmyagent/arbiter
1 maintainer
Metadata
1 maintainer
Release files for hold-sdk 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| hold_sdk-0.4.0.tar.gz | 6.1 kB | With provenance | Details for hold_sdk-0.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| hold_sdk-0.4.0-py3-none-any.whl | Python 3 | none | any | Details for hold_sdk-0.4.0-py3-none-any.whl |
Total release size: 9.8 kB
Release files / hold_sdk-0.4.0.tar.gz
| Download URL | hold_sdk-0.4.0.tar.gz |
|---|---|
| Size | 6.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e7d0b96b1940ae31c961fd387507792871ea233b498f6619e412b77de35630b5
|
|
BLAKE2b-256 checksum How to use checksums |
2e6ce4d5cb5f208bb6f5895ed335c32f25c6bc8a406c59330928f0cf4fea8954
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 Jul 22, 2026.
Transparency logRelease files / hold_sdk-0.4.0-py3-none-any.whl
| Download URL | hold_sdk-0.4.0-py3-none-any.whl |
|---|---|
| Size | 3.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6ea1c0e55b9183ffdcd6c62bd1b0f61aaf513407e09f0a05f81c0038be16b1cd
|
|
BLAKE2b-256 checksum How to use checksums |
67e17cae4c0f5df3f92c78f53ea4291ce45ba24c8ca72222aa60caf10fdbae84
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 Jul 22, 2026.
Transparency logSecurity for hold-sdk 0.4.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for hold_sdk-0.4.0.tar.gz
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 Jul 22, 2026.
Transparency logA 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.
