Skip to main content

agno-aer1

Every tool call your Agno agent makes, recorded as an AER-1 verifiable execution receipt. Four lines of code. No new infrastructure.

AER-1 is an open IETF Internet-Draft (draft-zambo-aer1-26) defining a small vocabulary for recording one AI agent tool call as a portable, independently checkable receipt. A receipt proves the recorded result was not changed. It does not prove the tool was correct.

Install

pip install agno-aer1

10-minute quickstart

from agno.agent import Agent
from agno.models.openai import OpenAIChat
from agno_aer1 import AER1Recorder

recorder = AER1Recorder()
agent = Agent(
    model=OpenAIChat(id="gpt-4o-mini"),
    tools=[...],
    tool_hooks=[recorder],
)
agent.run("What is 17 * 24?")

print(f"{len(recorder.receipts)} receipts recorded")
recorder.save("receipts.jsonl")

That is the whole integration. tool_hooks is Agno's native middleware seam for tool execution (the same seam observability integrations use): each hook wraps a tool call, sees the function name and arguments, runs the tool, and observes the result. The recorder sits in that chain and emits one receipt per call, then returns the result untouched.

What a receipt looks like

{
  "id": "3f9a2c1e-7b4d-4f8a-9c2e-1a5b6d7e8f90",
  "receipt_schema_version": "0.3",
  "created_at": "2026-10-05T22:30:00.123456Z",
  "tool": {"name": "calculator", "version": "3.1.1", "scope": "public"},
  "provenance_class": "EXECUTED BY AGNO",
  "canonical_bytes": "eyJpbnB1dHMiOi...",
  "output_hash": "sha256:9f2c...",
  "verification_status": "verified"
}

The canonical bytes are a deterministic JSON payload (tool, inputs, output). Anyone can base64-decode them, recompute SHA-256, and compare with output_hash. That is the entire verification procedure.

Verify a receipt yourself

from agno_aer1 import verify_receipt

failures = verify_receipt(recorder.receipts[0])
assert failures == [], failures
print("receipt checks out")

Honest boundaries

  • A receipt proves the recorded bytes were not changed. It does not prove the tool was correct, or that the model chose the right tool.
  • Tool calls that raise produce no receipt; the error propagates exactly as Agno handles it without the recorder.
  • If you enable Agno's tool-result cache, cache replays also pass through the middleware and emit receipts. Each receipt still commits to the exact bytes the agent observed.
  • The recorder never changes a tool result. If receipt construction itself ever fails, the tool result is still returned untouched.

Where these receipts run live: Zambo

agno-aer1 gives Agno agents a verifiable AER-1 receipt for every tool call, and it has been downloaded 872 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 agno-aer1

Zambo, built by Brennan Zambo, the creator of the AER-1 standard, runs 153 tools in total, 37 on the default surface, behind one MCP endpoint: https://zambo.dev/mcp.

Metadata

Release files for agno-aer1 0.1.4

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for agno-aer1 0.1.4
File Size Uploaded Provenance Actions
agno_aer1-0.1.4.tar.gz 6.3 kB Without provenance Details for agno_aer1-0.1.4.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for agno-aer1 0.1.4
File Interpreter ABI Platform Actions
agno_aer1-0.1.4-py3-none-any.whl Python 3 none any Details for agno_aer1-0.1.4-py3-none-any.whl

Total release size: 12.7 kB

Release files / agno_aer1-0.1.4.tar.gz

Download URL agno_aer1-0.1.4.tar.gz
Size 6.3 kB
Tags Source
SHA-256 checksum
How to use checksums
73471888d1ab3fa8252f6b1f5fc7c07c526a77b465548f9f86651c45107121fe
BLAKE2b-256 checksum
How to use checksums
8ed706fe73c0d19d66363911efd9ac385dc9a2891e99876bb4b9dbb2ef477d25
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via rambo-pypi-grab/0.1.0

Release files / agno_aer1-0.1.4-py3-none-any.whl

Download URL agno_aer1-0.1.4-py3-none-any.whl
Size 6.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
5d4d9738b5d68adc3318c6fcf4af0c3a3d1718afa3141c79aa2c6315c46e6d52
BLAKE2b-256 checksum
How to use checksums
bb9b92ec108ae8ae6b64fe3fc21ac92c839b8cb215a8e91daa6166df809157a4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via rambo-pypi-grab/0.1.0

Security for agno-aer1 0.1.4

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page