qerexa (Python, preview)
Python clients for Qerexa:
QerexaGateMiddlewareputs a Qerexa check in front of any Python function: AutoGen functions, CrewAI or LangChain tools, or your own code.QerexaVCClientissues and verifies credentials, federation tokens and trust relationships between organizations.
Install
pip install qerexa
Gate a function
import os
from qerexa import (
ExecutionAuthorizationRequiredError,
GateBlockedError,
QerexaGateMiddleware,
)
gate = QerexaGateMiddleware(api_key=os.environ["QEREXA_API_KEY"])
@gate.gate_check(action="report.export", reasoning="Monthly compliance export")
def export_report(report_id: str) -> str:
...
try:
export_report("rpt_123")
except ExecutionAuthorizationRequiredError as e:
# Human review was requested (flow e.flow_id). Approval of that review does
# not authorize this call; stop here or use an action-bound execution flow.
...
except GateBlockedError as e:
...
Your function runs only when Qerexa gives a clear, current yes: an allowed
decision with its own ID and an expiry still in the future. Anything else
raises before your code starts, whether that's a block, a pending review, an
expired or garbled answer, a redirect, or a network failure. Every one of those
errors derives from QerexaError.
Your function's arguments never leave your process. Qerexa sees the action,
the actor, the reasoning you pass (the function name by default) and any
metadata, so keep credentials and customer data out of those.
With CrewAI, decorate the function behind the tool before handing it over. The check then runs on every call, whatever CrewAI's callbacks do.
Verifiable credentials
from qerexa import VCClientConfig, create_vc_client
vc = create_vc_client(VCClientConfig(org_id="org_123", api_key=os.environ["QEREXA_API_KEY"]))
relationships = vc.list_trust_relationships(limit=10)
Requests time out after 10 seconds by default (VCClientConfig(timeout=...)).
Preview limits
This is a preview, not a certified execution control. It doesn't verify receipts, wait on review flows, or tie an approval to one specific execution, so keep payments, deployments and other high-impact actions behind the documented API proof flow and an execution contract you've reviewed independently.
Development
python -m pip install -e "./packages/sdk-python[dev]"
ruff check packages/sdk-python
pytest packages/sdk-python
Releases follow the SDK release runbook.
Metadata
Release files for qerexa 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 | Provenance | Actions |
|---|---|---|---|---|
| qerexa-0.1.1.tar.gz | 9.3 kB | With provenance | Details for qerexa-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| qerexa-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for qerexa-0.1.1-py3-none-any.whl |
Total release size: 18.8 kB
Release files / qerexa-0.1.1.tar.gz
| Download URL | qerexa-0.1.1.tar.gz |
|---|---|
| Size | 9.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b5f2bb9529b452bcbf37c3b06bd6c93e973fece651a55e7bdc5bb7fe311cde5a
|
|
BLAKE2b-256 checksum How to use checksums |
1633468b59f4457d58f18145869e35e47995906147855ee61ab735360f0eb0f1
|
| 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 19, 2026.
Transparency logRelease files / qerexa-0.1.1-py3-none-any.whl
| Download URL | qerexa-0.1.1-py3-none-any.whl |
|---|---|
| Size | 9.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8f8678116feaec20bd59232155609c6467648df1a08d0e0805e655ee78f2ccac
|
|
BLAKE2b-256 checksum How to use checksums |
9bd5430b66348938ed5e16d9c7c7e726d2785af0ee024196bb46d61c14aacbde
|
| 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 19, 2026.
Transparency logSecurity for qerexa 0.1.1
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 qerexa-0.1.1.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 19, 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.