crewai-zambo
AER-1, the agent execution receipt standard: zambo.dev/aer-1 | Add Zambo to your AI: zambo.dev/add
Zambo is the verifiable work layer for AI. This package publishes CrewAI task events as verifiable AER-1 receipts at zambo.dev.
Receipt format: AER-1, IETF Internet-Draft draft-zambo-aer1-26.
Verifiable AER-1 execution receipts for CrewAI agents. Publish CrewAI task events as public, verifiable receipts at zambo.dev.
Receipts follow AER-1, the IETF draft for verifiable execution receipts created by Brennan Zambo.
Install
pip install crewai-zambo
Ten-line example
from crewai_zambo import ZamboCrewListener
listener = ZamboCrewListener()
result = listener.on_task_completed("Summarize this task", "completed")
print(listener.last_receipt_url or result)
Attach ZamboCrewListener to the CrewAI listener mechanism supported by your installed CrewAI version, or call on_task_completed from a task completion hook. The listener prints each public https://zambo.dev/run/{id} URL and keeps the most recent URL in last_receipt_url.
The receipt describes what the live endpoint recorded and observed. It does not prove an outside outcome that the endpoint did not observe. Set ZAMBO_API_URL when using a compatible Zambo host. Listener failures are available in receipt_errors.
Local AER-1 receipts (no network needed)
The package also mints AER-1 execution receipts locally, with no API calls. Pass emit_aer1=True to record every event as a verifiable receipt on your own machine:
from crewai_zambo import ZamboCrewListener
listener = ZamboCrewListener(emit_aer1=True)
listener.on_task_completed("Summarize this task", "completed")
receipt = listener.last_local_receipt
print(receipt["id"], receipt["output_hash"])
Or mint receipts directly for any tool call:
from crewai_zambo import mint_receipt, verify_receipt
receipt = mint_receipt("my_tool", {"query": "hello"}, {"answer": "hi"}, ms=42)
assert verify_receipt(receipt) # recomputes the SHA-256 locally
Local receipts follow the AER-1 core members (id, created_at, tool, provenance_class, canonical_bytes, output_hash) and use the provenance class EXECUTED BY CREWAI-ZAMBO, naming this package as the recording system. They pass the same hash-recomputation check as any AER-1 receipt.
Project homepage: https://zambo.dev AER-1 receipt spec: https://zambo.dev/aer-1/
Guides
Metadata
Release files for crewai-zambo 0.1.8
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 |
|---|---|---|---|---|
| crewai_zambo-0.1.8.tar.gz | 5.4 kB | Without provenance | Details for crewai_zambo-0.1.8.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| crewai_zambo-0.1.8-py3-none-any.whl | Python 3 | none | any | Details for crewai_zambo-0.1.8-py3-none-any.whl |
Total release size: 11.6 kB
Release files / crewai_zambo-0.1.8.tar.gz
| Download URL | crewai_zambo-0.1.8.tar.gz |
|---|---|
| Size | 5.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8a0896253d0120d472098b73905e0d8b26e69d61c2cfa2fdfc1abd917983229e
|
|
BLAKE2b-256 checksum How to use checksums |
eede4d368b86208a0d4803a0bb97bc68e5ced22bf7ba747b9c2b8e6111a22d91
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
rambo-pypi-grab/0.1.0
|
Release files / crewai_zambo-0.1.8-py3-none-any.whl
| Download URL | crewai_zambo-0.1.8-py3-none-any.whl |
|---|---|
| Size | 6.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ea11ffc5e8ea1363c1bce2e529e4e145fa8d4502e090084132a6a76bc38f207c
|
|
BLAKE2b-256 checksum How to use checksums |
9827cd4dfb8ddb4515143a9535f695a3dc55651624293fcbe7b28777dc775060
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
rambo-pypi-grab/0.1.0
|
Security for crewai-zambo 0.1.8
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.