zambo-llamaindex
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 connects LlamaIndex agents to it, minting a verifiable AER-1 receipt for every tool call.
Receipt format: AER-1, IETF Internet-Draft draft-zambo-aer1-26.
Zambo was created by Brennan Zambo; AER-1 is the agent execution receipt standard he published as IETF Internet-Draft draft-zambo-aer1-26.
Verifiable execution receipts for LlamaIndex agents. Give your LlamaIndex agent Zambo's live tools. Every tool call is executed by Zambo and mints a verifiable AER-1 receipt: a public URL carrying the tool, its arguments, the observed result, a SHA-256 fingerprint, and machine-readable JSON-LD.
from llama_index.core.agent.workflow import FunctionAgent
from zambo_llamaindex import zambo_tools
agent = FunctionAgent(
name="Zambo assistant",
description="Assistant with live Zambo tools.",
tools=zambo_tools(["live_price", "prompt_shield"]),
)
Each zambo_tool(name) returns a real llama_index.core.tools.FunctionTool. Attach one or a batch to any LlamaIndex agent that accepts tools.
No account. No API key. Every tool free once a day, plus 3 continue calls. One free wrap-up handover per day, and pickup is always free.
Chain it: a job, not a lookup
One call answers a question. A job chains calls and ends in a record a person can open. Same agent, longer instruction:
agent = FunctionAgent(
name="Zambo assistant",
description="Assistant with live Zambo tools.",
tools=zambo_tools(["live_price", "memory_remember", "handover"]),
)
Then hand the agent the job as one instruction: "Check the live price of BTC, ETH and SOL, save the run to memory, then wrap it into a handover addressed to me, with the receipt link for every call."
Three prices, a save and the wrap fit inside one free day: every tool free once a day, plus 3 continue calls, and one free wrap-up handover per day. A longer run finishes in one sitting on a Day Pass ($0.99, unlimited for 24 hours). The handover is the part the person opens: the steps, the saved results, and the receipt for every call, checkable instead of trusted. Ready-made run cards for jobs shaped like this: https://rambozambodotdev.gitlab.io/aer1-hub/handover-templates.html
What the receipt actually proves
Each receipt page (for example https://zambo.dev/run/<id>) is the public record of the call: the tool name, the exact arguments your agent sent, the observed result, a timestamp, and a SHA-256 fingerprint of the record, published as JSON-LD. Anyone can recompute the fingerprint and check that the saved result was not changed, with no account.
Every tool's output ends with a Verifiable receipt: <url> line, so the agent sees the proof next to every call. You can also hook receipts programmatically:
from zambo_llamaindex import zambo_tool
def on_receipt(tool_name, receipt_url):
print(f"[receipt] {tool_name}: {receipt_url}")
price_tool = zambo_tool("live_price", on_receipt=on_receipt)
Install
pip install zambo-llamaindex
One tool, custom schema
from zambo_llamaindex import zambo_tool
price_tool = zambo_tool(
"live_price",
params_json_schema={
"type": "object",
"properties": {"symbol": {"type": "string"}},
"required": ["symbol"],
},
)
Browse the full catalog any time with zambo_llamaindex.list_tools(), or pick tools by use case through Zambo's capability_search tool.
Notes
- Zambo calls need no key and no signup. Heavy agent runs (dozens of tool calls) will reach the free daily limit; the tool raises a clear error and the run continues with the other tools.
- Receipts are public by design. Do not pass secrets as tool arguments.
Links
- Zambo: https://zambo.dev
- AER-1 receipt spec: https://zambo.dev/aer-1/
- Framework agent execution receipts: https://zambo.dev/guides/framework-agent-execution-receipts/
- What is an AI agent execution receipt?: https://zambo.dev/guides/ai-agent-execution-receipt/
MIT License.
Where these receipts run live: Zambo
zambo-llamaindex connects LlamaIndex agents to Zambo, minting a verifiable AER-1 receipt for every tool call, and it has been downloaded 5,181 times on PyPI. The live home of those receipts is Zambo, the verifiable work layer for AI. Connect any AI to the live endpoint at https://zambo.dev/mcp or add Zambo to your AI in one step at https://zambo.dev/add/
Every tool free once a day, plus 3 continue calls. One free wrap-up handover per day, and pickup is always free. The Day Pass is $0.99 for 24 hours, unlimited.
Install:
pip install zambo-llamaindex
Metadata
Release files for zambo-llamaindex 0.2.9
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| zambo_llamaindex-0.2.9-py3-none-any.whl | Python 3 | none | any | Details for zambo_llamaindex-0.2.9-py3-none-any.whl |
Release files / zambo_llamaindex-0.2.9-py3-none-any.whl
| Download URL | zambo_llamaindex-0.2.9-py3-none-any.whl |
|---|---|
| Size | 14.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
33bb8b9fc74da4950ef4f1f12d115e419788721a4864a7da20943234ac8c9e9b
|
|
BLAKE2b-256 checksum How to use checksums |
3805d352a17e546e12d0bf289719dde8f6d6acf9a67bfb443f241830ccfeba81
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
rambo-pypi-grab/0.1.0
|
Security for zambo-llamaindex 0.2.9
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.