zambo-haystack 0.2.1__tar.gz → 0.2.2__tar.gz

{zambo_haystack-0.2.1/src/zambo_haystack.egg-info → zambo_haystack-0.2.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: zambo-haystack
-Version: 0.2.1
+Version: 0.2.2
 Summary: Verifiable execution receipts for Haystack agents. Every tool call mints a verifiable AER-1 receipt at zambo.dev.
 Author-email: Zambo <brennanzambo@zambo.dev>
 License: MIT
@@ -23,7 +23,7 @@ Dynamic: license-file
 
 # zambo-haystack
 
-Verifiable execution receipts for Haystack agents. Give your Haystack agent Zambo's 100+ 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.
+Verifiable execution receipts for Haystack agents. Give your Haystack agent Zambo's 153 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.
 
 ```python
 from haystack.components.agents import Agent
@@ -42,7 +42,7 @@ No account. No API key. Free tier: 20 calls per tool per day.
 
 ## What the receipt actually proves
 
-Each receipt page (for example `https://zambo.dev/run/<id>`) is Zambo's tamper-evident record that **Zambo executed the tool call itself**: 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 re-verify it with no account.
+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 Haystack tool returned by `zambo_tool` appends the minted receipt URL to its result text, and records it in a registry you can query with `lookup_receipt(tool_name, arguments_json)`:
 

{zambo_haystack-0.2.1 → zambo_haystack-0.2.2}/README.md

@@ -1,6 +1,6 @@
 # zambo-haystack
 
-Verifiable execution receipts for Haystack agents. Give your Haystack agent Zambo's 100+ 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.
+Verifiable execution receipts for Haystack agents. Give your Haystack agent Zambo's 153 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.
 
 ```python
 from haystack.components.agents import Agent
@@ -19,7 +19,7 @@ No account. No API key. Free tier: 20 calls per tool per day.
 
 ## What the receipt actually proves
 
-Each receipt page (for example `https://zambo.dev/run/<id>`) is Zambo's tamper-evident record that **Zambo executed the tool call itself**: 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 re-verify it with no account.
+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 Haystack tool returned by `zambo_tool` appends the minted receipt URL to its result text, and records it in a registry you can query with `lookup_receipt(tool_name, arguments_json)`:
 

{zambo_haystack-0.2.1 → zambo_haystack-0.2.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "zambo-haystack"
-version = "0.2.1"
+version = "0.2.2"
 description = "Verifiable execution receipts for Haystack agents. Every tool call mints a verifiable AER-1 receipt at zambo.dev."
 readme = "README.md"
 requires-python = ">=3.10"

{zambo_haystack-0.2.1 → zambo_haystack-0.2.2/src/zambo_haystack.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: zambo-haystack
-Version: 0.2.1
+Version: 0.2.2
 Summary: Verifiable execution receipts for Haystack agents. Every tool call mints a verifiable AER-1 receipt at zambo.dev.
 Author-email: Zambo <brennanzambo@zambo.dev>
 License: MIT
@@ -23,7 +23,7 @@ Dynamic: license-file
 
 # zambo-haystack
 
-Verifiable execution receipts for Haystack agents. Give your Haystack agent Zambo's 100+ 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.
+Verifiable execution receipts for Haystack agents. Give your Haystack agent Zambo's 153 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.
 
 ```python
 from haystack.components.agents import Agent
@@ -42,7 +42,7 @@ No account. No API key. Free tier: 20 calls per tool per day.
 
 ## What the receipt actually proves
 
-Each receipt page (for example `https://zambo.dev/run/<id>`) is Zambo's tamper-evident record that **Zambo executed the tool call itself**: 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 re-verify it with no account.
+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 Haystack tool returned by `zambo_tool` appends the minted receipt URL to its result text, and records it in a registry you can query with `lookup_receipt(tool_name, arguments_json)`:
 

{zambo_haystack-0.2.1 → zambo_haystack-0.2.2}/src/zambo_haystack.egg-info/SOURCES.txt

@@ -1,6 +1,7 @@
 LICENSE
 README.md
 pyproject.toml
+setup.cfg
 src/zambo_haystack/__init__.py
 src/zambo_haystack/aer1core.py
 src/zambo_haystack/client.py