agenticwf-kb-client
The client of the AgenticWF knowledge service: the Python KBClient and the agenticwf kb
command (with agenticwf-auth-client, installed
with it).
pip install agenticwf-kb-client # [hpo] adds the Optuna warm-start helper
agenticwf kb list # your knowledge bases
agenticwf kb search "beam energy" --kb ID # hybrid search
agenticwf kb ask "what changed in run 42?" # agentic search: an answer and its sources
agenticwf kb call GET /knowledge-bases # any KB API call
Only the KB's URL is needed: the KB tells how to sign in, and behind the AgenticWF server
(Caddy, Logto) the server publishes the Logto settings. Sign in once with agenticwf login:
export AGENTICWF_KB_URL=https://host.example.org/app/kb
agenticwf login
Scripts and CI use a personal access token instead (AGENTICWF_TOKEN=pat_…), or a machine
client (AGENTICWF_CLIENT_ID + AGENTICWF_CLIENT_SECRET). AGENTICWF_AUTH_URL,
AGENTICWF_API_URL, AGENTICWF_CLIENT_ID and AGENTICWF_RESOURCE, when set, take precedence
over what the server publishes (an administrator gets them with
docker exec agenticwf cat /var/lib/agenticwf/logto/clients.env).
A standalone KB has its own token instead: use the sign-in link it prints as the URL, or give the token:
export AGENTICWF_KB_URL='http://127.0.0.1:8766/kb/?token=…' # docker exec agenticwf-kb agenticwf-kb token --ensure
export AGENTICWF_KB_TOKEN=$(docker exec agenticwf-kb agenticwf-kb token) # or: the token
From Python (KBClient.from_env() finds the KB and its token as the command does):
from agenticwf.kb.client import KBClient
with KBClient.from_env() as kb:
for hit in kb.search("beam energy"):
print(hit["score"], hit["knowledge_title"])
HPO warm start with Optuna: agenticwf.kb.client.hpo (warm_start, upload_study).
Metadata
Release files for agenticwf-kb-client 0.0.3
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 |
|---|---|---|---|---|
| agenticwf_kb_client-0.0.3.tar.gz | 10.0 kB | Without provenance | Details for agenticwf_kb_client-0.0.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| agenticwf_kb_client-0.0.3-py3-none-any.whl | Python 3 | none | any | Details for agenticwf_kb_client-0.0.3-py3-none-any.whl |
Total release size: 19.2 kB
Release files / agenticwf_kb_client-0.0.3.tar.gz
| Download URL | agenticwf_kb_client-0.0.3.tar.gz |
|---|---|
| Size | 10.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a76d5a6aec6250e6ee5c8718d94cb8e8a461b27775393598aa0866617fa3f1a2
|
|
BLAKE2b-256 checksum How to use checksums |
dfcb3221e127591fbd5e126ec058d845654ba6a0b941d1fcc904aa704870d2f0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.15
|
Release files / agenticwf_kb_client-0.0.3-py3-none-any.whl
| Download URL | agenticwf_kb_client-0.0.3-py3-none-any.whl |
|---|---|
| Size | 9.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e870f5526c7059fa6cefbc91a34fb7c7b0e08690f445226696767f4d9a63aba0
|
|
BLAKE2b-256 checksum How to use checksums |
c4f99faff50e227b3d62ded1046c21acb4075f088235a3703e7cb757ca3b6c4d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.15
|
Security for agenticwf-kb-client 0.0.3
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.