FLAME Hub Python Client
The FLAME Hub Python Client is a client which wraps the endpoints of FLAME Hub API. This repository is part of the PrivateAIM project.
Getting started
To install the client, Python 3.10 or higher is required.
python -m pip install flame-hub-client
Quickstart
The FLAME Hub Python Client offers get, find, update, create and delete methods for the core, storage and auth endpoints. It is capable of authenticating against the API using either password or client authentication. Pick one, provide your credentials and plug them into the class for the service you want to use. Note that the client will automatically reauthenticate if necessary.
import flame_hub
auth = flame_hub.auth.PasswordAuth(
username="admin", password="start123", base_url="http://localhost:3000/auth/"
)
auth_client = flame_hub.AuthClient(base_url="http://localhost:3000/auth/", auth=auth)
Now you're ready to use the library's functions! Start off with getting the so-called master realm by using one of the
find methods and filtering for the name "master".
master_realms = auth_client.find_realms(filter={"name": "master"})
Every find method returns a list of matching resources. Since there is only one realm called "master" in this
example, we simply pop it from the list and print the result.
assert len(master_realms) == 1
master_realm = master_realms.pop()
print(master_realm.model_dump_json(indent=2))
{
"name": "master",
"displayName": null,
"description": null,
"id": "794f2375-f043-4789-bd0c-e5534e8deeaa",
"builtIn": true,
"createdAt": "2025-05-12T09:44:08.284000Z",
"updatedAt": "2025-05-12T09:44:08.284000Z"
}
Next we want to create a new node. Node resources are accessible over endpoints under the core directive. So the first step is to create a new core client and then create a new node.
core_client = flame_hub.CoreClient(base_url="http://localhost:3000/core/", auth=auth)
my_node = core_client.create_node(name="my-node", realm_id=master_realm)
print(my_node.model_dump_json(indent=2))
{
"externalName": null,
"hidden": false,
"name": "my-node",
"realmId": "794f2375-f043-4789-bd0c-e5534e8deeaa",
"registryId": null,
"type": "default",
"id": "03636152-e6a8-4e01-994e-18b2b0c3a935",
"publicKey": null,
"online": false,
"registry": null,
"registryProjectId": null,
"registryProject": null,
"robotId": null,
"clientId": "2d3e19b4-6708-4279-b2a7-34ad42638e4b",
"createdAt": "2025-05-19T15:43:57.859000Z",
"updatedAt": "2025-05-19T15:43:57.859000Z"
}
Maybe making the node public wasn't such a good idea, so let's update it by hiding it. To see if the update was successful, we have to request the updated node from the Hub.
core_client.update_node(my_node, hidden=True)
assert core_client.get_node(my_node.id) is True
To clean up our mess, we delete the node and verify that the node is gone forever.
core_client.delete_node(my_node)
assert core_client.get_node(my_node.id) is None
Note that not all method types are implemented for each resource. Check out the documentation to see which methods are available.
Metadata
Release files for flame-hub-client 1.1.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 |
|---|---|---|---|---|
| flame_hub_client-1.1.0.tar.gz | 28.1 kB | With provenance | Details for flame_hub_client-1.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| flame_hub_client-1.1.0-py3-none-any.whl | Python 3 | none | any | Details for flame_hub_client-1.1.0-py3-none-any.whl |
Total release size: 58.6 kB
Release files / flame_hub_client-1.1.0.tar.gz
| Download URL | flame_hub_client-1.1.0.tar.gz |
|---|---|
| Size | 28.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4eff02b8ff8df01d9a313ef464f30ceb6d62f341e39c5b368385564a914bddeb
|
|
BLAKE2b-256 checksum How to use checksums |
ca273dc4c1197ee0a54d509f93ea734c01fd402be0ed8a98658dd5b487f87281
|
| 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 Oct 16, 2026.
Transparency logRelease files / flame_hub_client-1.1.0-py3-none-any.whl
| Download URL | flame_hub_client-1.1.0-py3-none-any.whl |
|---|---|
| Size | 30.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fa1ce9f764bb832eb512273deb287b8b8846b62f8e79d3a87d67784e334e8d2d
|
|
BLAKE2b-256 checksum How to use checksums |
f2b01cb499cb502d5bfb7ae2aba0b618c169aa61762665487dd6e1471930b135
|
| 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 Oct 16, 2026.
Transparency logSecurity for flame-hub-client 1.1.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 flame_hub_client-1.1.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 Oct 16, 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.