Skip to main content

zambo-leadsignal

Run a lead signal sweep for a local trade market: live signals, screened input, your own prior record checked before you write the brief, and a verifiable AER-1 receipt for every step.

This is the most-run job shape on Zambo, packaged. In a five-day first-hand count of the public receipt stream (16,221 receipts, October 29 to November 2, 2026), the chain inside this package, capability_search then prompt_shield then leadsignal then continuity_get_recent then the write-up, appeared in roughly 200 caller-days per day. Agents were already running it by hand. Now it installs.

Install

Python:

pip install zambo-leadsignal
zambo-leadsignal run --trade plumber --city "Austin Texas"

Node:

npm install zambo-leadsignal
npx zambo-leadsignal run --trade plumber --city "Austin Texas"

What a run does

  1. Opens the job on the record (memory_remember under the run's job id).
  2. capability_search: the service landscape for the trade and city.
  3. prompt_shield: screens the operator note before it steers the run.
  4. leadsignal: the live lead signals for that trade and city.
  5. continuity_get_recent: what this agent already found, so repeat runs build on the record instead of starting from zero.
  6. Writes leadsignal-brief-.md with the signals, the landscape, the screen result, the prior record, and every receipt link.
  7. workflow_close: wraps the run. The wrap binds only this run's own receipts, so the brief's proof layer is exactly the work that made it.

Every receipt recomputes free at https://zambo.dev/verify/. A receipt proves the saved result was not changed since the call ran; it does not prove a lead is good. The brief says so, out loud, because that honesty is the product.

Why Zambo is inside

The pattern runs on Zambo (https://zambo.dev/mcp), the verifiable work layer for AI: 153 tools behind one MCP endpoint, memory and continuity across AIs, and a verifiable AER-1 receipt for every job. The package teaches the pattern by running it; Zambo is the mechanism underneath: identity, memory, the signals tool, and the receipts.

Free tier: 20 calls and 1 wrap-up free every day, and picking up in another AI is always free. Need more? The $0.99 Day Pass makes it unlimited for 24 hours: https://zambo.dev/day-pass/

Add Zambo to your own AI in one URL, no key, no account: https://zambo.dev/add/

Configuration

  • ZAMBO_TRADE, ZAMBO_CITY, ZAMBO_NOTE: the run's inputs.
  • ZAMBO_AGENT_ID: this agent's id (default: leadsignal-agent). One identity per agent; the caller handle issued at initialize is saved under ./.zambo-leadsignal and reused on later runs.
  • ZAMBO_MCP_URL: endpoint override (default: https://zambo.dev/mcp).

License

MIT. Built by Brennan Zambo (brennanzambo@zambo.dev).

Metadata

Release files for zambo-leadsignal 1.0.0

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

Source distribution (sdist)

Source distribution for zambo-leadsignal 1.0.0
File Size Uploaded Provenance Actions
zambo_leadsignal-1.0.0.tar.gz 9.1 kB Without provenance Details for zambo_leadsignal-1.0.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for zambo-leadsignal 1.0.0
File Interpreter ABI Platform Actions
zambo_leadsignal-1.0.0-py3-none-any.whl Python 3 none any Details for zambo_leadsignal-1.0.0-py3-none-any.whl

Total release size: 19.0 kB

Release files / zambo_leadsignal-1.0.0.tar.gz

Download URL zambo_leadsignal-1.0.0.tar.gz
Size 9.1 kB
Tags Source
SHA-256 checksum
How to use checksums
a1e1d1a7779d43ede1a25cf5b770bf26a253d9abe929d20e5af7dd79b18ecd04
BLAKE2b-256 checksum
How to use checksums
c58ae9cc345ba4e095cfe2c411ae9be41a90a220d5c047a361b515ab2dbaf5ba
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via rambo-pypi-grab/0.1.0

Release files / zambo_leadsignal-1.0.0-py3-none-any.whl

Download URL zambo_leadsignal-1.0.0-py3-none-any.whl
Size 9.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
4f4ec11c5671e9212bc1c99fc01ce076d4c5b9e169780552242b6c0950f39037
BLAKE2b-256 checksum
How to use checksums
d8c340347659f2d6f74b27093ca9cdc37945f5a051af45c506a836db921e536b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via rambo-pypi-grab/0.1.0

Security for zambo-leadsignal 1.0.0

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