zambo-mcp 1.0.15 → 1.0.17
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.
- package/README.md +16 -0
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -82,6 +82,12 @@ const v = await zambo.verifyReceipt(receipt.id);
|
|
|
82
82
|
console.log(v.verified, v.tool, v.sha256);
|
|
83
83
|
```
|
|
84
84
|
|
|
85
|
+
## Make it a daily loop
|
|
86
|
+
|
|
87
|
+
Give an agent a standing routine and Zambo stops being a one-off call and becomes its daily habit. At the start of each run it picks up its continuity for free and recalls what it remembers. It does the work. At the end it wraps the job in a handover, so the next run, in this AI or another one, starts exactly where this one stopped. The whole loop fits the free tier alone: 20 calls + 1 wrap-up free every day, and picking up in another AI is always free.
|
|
88
|
+
|
|
89
|
+
Proof from a real scheduled run: the [wrap receipt](https://zambo.dev/run/1e97b3a8-8c6d-4eff-8dd9-3671b2dfa2e2). The full recipe: [the scheduled agent heartbeat](https://rambozambodotdev.gitlab.io/aer1-hub/scheduled-agent-heartbeat.html).
|
|
90
|
+
|
|
85
91
|
## What Zambo is
|
|
86
92
|
|
|
87
93
|
[Zambo](https://zambo.dev) is the verifiable work layer for AI: an MCP server with native tools: live crypto prices, site audits, web research, content tools, lead and data tools, and multi-step agent jobs, behind one plain JSON-RPC endpoint (`https://zambo.dev/mcp`). This package is a thin, zero-dependency client for that endpoint.
|
|
@@ -158,3 +164,13 @@ Free tier: 20 calls + 1 wrap-up free every day; picking up in another AI is alwa
|
|
|
158
164
|
Install:
|
|
159
165
|
|
|
160
166
|
npm install zambo-mcp
|
|
167
|
+
|
|
168
|
+
## The Zambo pattern family
|
|
169
|
+
|
|
170
|
+
Five installable packages teach Zambo patterns, each with a real run behind it. The family page: https://rambozambodotdev.gitlab.io/aer1-hub/the-pattern-family.html
|
|
171
|
+
|
|
172
|
+
- **zambo-swarm**: use it when the job is bigger than one agent and several workers must each prove their piece of one shared job. PyPI: https://pypi.org/project/zambo-swarm/ and npm: https://www.npmjs.com/package/zambo-swarm
|
|
173
|
+
- **zambo-loop**: use it when an agent must pick up its own work tomorrow, recall its baseline verbatim, and keep one job alive across sessions. npm: https://www.npmjs.com/package/zambo-loop (PyPI listing pending)
|
|
174
|
+
- **zambo-verify-pass**: use it when someone retells a result and you need to catch the drift against the receipt of record. PyPI: https://pypi.org/project/zambo-verify-pass/ and npm: https://www.npmjs.com/package/zambo-verify-pass
|
|
175
|
+
- **zambo-delivery**: use it when a client must check delivered work step by step and their pickup is the sign-off. PyPI: https://pypi.org/project/zambo-delivery/ and npm: https://www.npmjs.com/package/zambo-delivery
|
|
176
|
+
- **zambo-watch**: use it when one watcher checks the same signal on a schedule and must prove what it saw, quiet days included. PyPI: https://pypi.org/project/zambo-watch/ and npm: https://www.npmjs.com/package/zambo-watch
|
package/package.json
CHANGED