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

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (16) hide show
  1. {zambo_haystack-0.2.0/src/zambo_haystack.egg-info → zambo_haystack-0.2.2}/PKG-INFO +3 -4
  2. {zambo_haystack-0.2.0 → zambo_haystack-0.2.2}/README.md +2 -2
  3. {zambo_haystack-0.2.0 → zambo_haystack-0.2.2}/pyproject.toml +1 -2
  4. {zambo_haystack-0.2.0 → zambo_haystack-0.2.2}/src/zambo_haystack/__init__.py +1 -1
  5. {zambo_haystack-0.2.0 → zambo_haystack-0.2.2}/src/zambo_haystack/client.py +2 -2
  6. {zambo_haystack-0.2.0 → zambo_haystack-0.2.2}/src/zambo_haystack/tools.py +1 -1
  7. {zambo_haystack-0.2.0 → zambo_haystack-0.2.2/src/zambo_haystack.egg-info}/PKG-INFO +3 -4
  8. {zambo_haystack-0.2.0 → zambo_haystack-0.2.2}/src/zambo_haystack.egg-info/SOURCES.txt +1 -0
  9. {zambo_haystack-0.2.0 → zambo_haystack-0.2.2}/LICENSE +0 -0
  10. {zambo_haystack-0.2.0 → zambo_haystack-0.2.2}/setup.cfg +0 -0
  11. {zambo_haystack-0.2.0 → zambo_haystack-0.2.2}/src/zambo_haystack/aer1core.py +0 -0
  12. {zambo_haystack-0.2.0 → zambo_haystack-0.2.2}/src/zambo_haystack/collector.py +0 -0
  13. {zambo_haystack-0.2.0 → zambo_haystack-0.2.2}/src/zambo_haystack.egg-info/dependency_links.txt +0 -0
  14. {zambo_haystack-0.2.0 → zambo_haystack-0.2.2}/src/zambo_haystack.egg-info/requires.txt +0 -0
  15. {zambo_haystack-0.2.0 → zambo_haystack-0.2.2}/src/zambo_haystack.egg-info/top_level.txt +0 -0
  16. {zambo_haystack-0.2.0 → zambo_haystack-0.2.2}/tests/test_aer1_collector.py +0 -0
{zambo_haystack-0.2.0/src/zambo_haystack.egg-info → zambo_haystack-0.2.2}/PKG-INFO RENAMED
@@ -1,12 +1,11 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: zambo-haystack
3
- Version: 0.2.0
3
+ Version: 0.2.2
4
4
  Summary: Verifiable execution receipts for Haystack agents. Every tool call mints a verifiable AER-1 receipt at zambo.dev.
5
5
  Author-email: Zambo <brennanzambo@zambo.dev>
6
6
  License: MIT
7
7
  Project-URL: Homepage, https://zambo.dev
8
8
  Project-URL: Documentation, https://zambo.dev/aer-1/
9
- Project-URL: Repository, https://zambo.dev
10
9
  Keywords: haystack,deepset,agents,ai-agents,zambo,mcp,receipts,verification,verifiable-execution-receipts,execution-receipts,verifiable-receipt
11
10
  Classifier: Development Status :: 4 - Beta
12
11
  Classifier: Intended Audience :: Developers
@@ -24,7 +23,7 @@ Dynamic: license-file
24
23
 
25
24
  # zambo-haystack
26
25
 
27
- 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.
26
+ 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.
28
27
 
29
28
  ```python
30
29
  from haystack.components.agents import Agent
@@ -43,7 +42,7 @@ No account. No API key. Free tier: 20 calls per tool per day.
43
42
 
44
43
  ## What the receipt actually proves
45
44
 
46
- 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.
45
+ 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.
47
46
 
48
47
  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)`:
49
48
 
{zambo_haystack-0.2.0 → zambo_haystack-0.2.2}/README.md RENAMED
@@ -1,6 +1,6 @@
1
1
  # zambo-haystack
2
2
 
3
- 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.
3
+ 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.
4
4
 
5
5
  ```python
6
6
  from haystack.components.agents import Agent
@@ -19,7 +19,7 @@ No account. No API key. Free tier: 20 calls per tool per day.
19
19
 
20
20
  ## What the receipt actually proves
21
21
 
22
- 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.
22
+ 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.
23
23
 
24
24
  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)`:
25
25
 
{zambo_haystack-0.2.0 → zambo_haystack-0.2.2}/pyproject.toml RENAMED
@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
4
4
 
5
5
  [project]
6
6
  name = "zambo-haystack"
7
- version = "0.2.0"
7
+ version = "0.2.2"
8
8
  description = "Verifiable execution receipts for Haystack agents. Every tool call mints a verifiable AER-1 receipt at zambo.dev."
9
9
  readme = "README.md"
10
10
  requires-python = ">=3.10"
@@ -29,7 +29,6 @@ optional-dependencies = {}
29
29
  [project.urls]
30
30
  Homepage = "https://zambo.dev"
31
31
  Documentation = "https://zambo.dev/aer-1/"
32
- Repository = "https://zambo.dev"
33
32
 
34
33
  [tool.setuptools.packages.find]
35
34
  where = ["src"]
{zambo_haystack-0.2.0 → zambo_haystack-0.2.2}/src/zambo_haystack/__init__.py RENAMED
@@ -1,6 +1,6 @@
1
1
  """zambo-haystack: Zambo's 100+ live tools as Haystack tools.
2
2
 
3
- Every tool call is executed by live Zambo (https://zambo.dev/api/mcp) and
3
+ Every tool call is executed by live Zambo (https://zambo.dev/mcp) and
4
4
  mints a verifiable AER-1 execution receipt. No account, no API key, free
5
5
  tier: 20 calls per tool per day.
6
6
 
{zambo_haystack-0.2.0 → zambo_haystack-0.2.2}/src/zambo_haystack/client.py RENAMED
@@ -1,7 +1,7 @@
1
1
  """Minimal Zambo MCP client over plain JSON-RPC.
2
2
 
3
3
  Pure stdlib (urllib), no third-party dependencies. Talks to the live
4
- https://zambo.dev/api/mcp endpoint: no auth, no account, free tier.
4
+ https://zambo.dev/mcp endpoint: no auth, no account, free tier.
5
5
  """
6
6
 
7
7
  from __future__ import annotations
@@ -13,7 +13,7 @@ import urllib.error
13
13
  import urllib.request
14
14
  from dataclasses import dataclass, field
15
15
 
16
- MCP_URL = "https://zambo.dev/api/mcp"
16
+ MCP_URL = "https://zambo.dev/mcp"
17
17
  _TIMEOUT = 60
18
18
  _MAX_ATTEMPTS = 6
19
19
 
{zambo_haystack-0.2.0 → zambo_haystack-0.2.2}/src/zambo_haystack/tools.py RENAMED
@@ -1,7 +1,7 @@
1
1
  """Haystack tools backed by live Zambo execution.
2
2
 
3
3
  Each tool below is a real Haystack Tool. When the agent invokes it, the
4
- call is executed by Zambo (https://zambo.dev/api/mcp) and mints a
4
+ call is executed by Zambo (https://zambo.dev/mcp) and mints a
5
5
  verifiable AER-1 receipt: public URL, tool, arguments, observed result,
6
6
  SHA-256 fingerprint, machine-readable JSON-LD.
7
7
  """
{zambo_haystack-0.2.0 → zambo_haystack-0.2.2/src/zambo_haystack.egg-info}/PKG-INFO RENAMED
@@ -1,12 +1,11 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: zambo-haystack
3
- Version: 0.2.0
3
+ Version: 0.2.2
4
4
  Summary: Verifiable execution receipts for Haystack agents. Every tool call mints a verifiable AER-1 receipt at zambo.dev.
5
5
  Author-email: Zambo <brennanzambo@zambo.dev>
6
6
  License: MIT
7
7
  Project-URL: Homepage, https://zambo.dev
8
8
  Project-URL: Documentation, https://zambo.dev/aer-1/
9
- Project-URL: Repository, https://zambo.dev
10
9
  Keywords: haystack,deepset,agents,ai-agents,zambo,mcp,receipts,verification,verifiable-execution-receipts,execution-receipts,verifiable-receipt
11
10
  Classifier: Development Status :: 4 - Beta
12
11
  Classifier: Intended Audience :: Developers
@@ -24,7 +23,7 @@ Dynamic: license-file
24
23
 
25
24
  # zambo-haystack
26
25
 
27
- 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.
26
+ 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.
28
27
 
29
28
  ```python
30
29
  from haystack.components.agents import Agent
@@ -43,7 +42,7 @@ No account. No API key. Free tier: 20 calls per tool per day.
43
42
 
44
43
  ## What the receipt actually proves
45
44
 
46
- 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.
45
+ 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.
47
46
 
48
47
  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)`:
49
48
 
{zambo_haystack-0.2.0 → zambo_haystack-0.2.2}/src/zambo_haystack.egg-info/SOURCES.txt RENAMED
@@ -1,6 +1,7 @@
1
1
  LICENSE
2
2
  README.md
3
3
  pyproject.toml
4
+ setup.cfg
4
5
  src/zambo_haystack/__init__.py
5
6
  src/zambo_haystack/aer1core.py
6
7
  src/zambo_haystack/client.py
{zambo_haystack-0.2.0 → zambo_haystack-0.2.2}/LICENSE RENAMED
File without changes
{zambo_haystack-0.2.0 → zambo_haystack-0.2.2}/setup.cfg RENAMED
File without changes