@signaliz/cli 1.0.63 → 1.0.65

package/README.md

@@ -1,6 +1,7 @@
 # @signaliz/cli
 
-The Signaliz CLI exposes all five core products:
+The Signaliz CLI exposes all five core products, plus Signal Awareness and
+Signaliz Flow through the same public contract:
 
 ```bash
 npm install -g @signaliz/cli
@@ -12,30 +13,35 @@ signaliz auth login
 # https://api.signaliz.com/functions/v1/api/v1/company-signals
 # https://api.signaliz.com/functions/v1/api/v1/signal-to-copy
 # https://api.signaliz.com/functions/v1/api/v1/signals
+# https://api.signaliz.com/functions/v1/api/v1/signal-awareness
+# https://api.signaliz.com/functions/v1/api/v1/flow
+# The same contracts are available under /api/v2/.
 
 signaliz find-email --company-domain example.com --full-name "Jane Doe"
 # An HTTPS LinkedIn person profile URL (/in/<slug>) is sufficient without a name or company domain
 signaliz find-email --linkedin-url "https://www.linkedin.com/in/jane-doe"
-# Force a fresh-provider quality check instead of reusing cached email or verification data
-signaliz find-email --company-domain example.com --full-name "Jane Doe" --skip-cache
 signaliz verify-email jane@example.com
-# Force a fresh-provider verification instead of reusing cached proof
-signaliz verify-email jane@example.com --skip-cache
 # Preview any single or batch product request without provider calls or credits
 signaliz verify-email jane@example.com --dry-run --json
 # Return early when a provider check runs long, then resume the exact run
-signaliz verify-email jane@example.com --skip-cache --no-wait --json
+signaliz verify-email jane@example.com --no-wait --json
 signaliz verify-email --verification-run-id run_... --json
-signaliz company-signals --domain example.com --research-prompt "expansion priorities"
+signaliz company-signals --domain example.com
 signaliz signal-to-copy \
   --company-domain example.com \
   --person-name "Jane Doe" \
   --title "VP Sales" \
   --campaign-offer "pipeline intelligence"
 
-# Force fresh signals or opt into slower deep research only when needed
+# Reuse the exact Signals First snapshot, fact, or event instead of rediscovering it.
+# Keep company/recipient/offer fields so Signaliz can validate identity and write the copy.
+signaliz signal-to-copy --fact-id <64-character-sha256> \
+  --company-domain example.com --person-name "Jane Doe" \
+  --title "VP Sales" --campaign-offer "pipeline intelligence"
+
+# Opt into slower deep research when needed
 signaliz signal-to-copy --company-domain example.com --person-name "Jane Doe" \
-  --title "VP Sales" --campaign-offer "pipeline intelligence" --skip-cache --deep-search
+  --title "VP Sales" --campaign-offer "pipeline intelligence" --deep-search
 
 # Omit --deep-search for bounded credit-free first-party and Bing grounding.
 
@@ -46,6 +52,16 @@ signaliz signals "companies showing signals they need account-signal automation"
   --icp-context "B2B SaaS with outbound teams and manual account research" \
   --limit 100 --sources web,news
 signaliz signals --signal-search-run-id run_... --wait --json
+
+# Monitor companies and retrieve seven-field verified signal rows
+# reason and replacement pointers forward.
+signaliz awareness list --limit 100 --offset 0 --json
+signaliz awareness signals --monitor-id <uuid> --limit 100 --offset 0 --json
+
+# Flow starts and resumes through the versioned REST contract.
+signaliz flow --signal-query "companies with recent hiring" \
+  --campaign-offer "pipeline intelligence"
+signaliz flow --run-id run_... --json
 ```
 
 Use `--json` with any product command for structured output.
@@ -66,6 +82,14 @@ signaliz signal-to-copy --input copy-requests.jsonl --no-wait --json
 signaliz signal-to-copy --job-id job_... --idempotency-key key_... --json
 ```
 
+Signal to Copy accepts `signal_search_run_id`, `fact_id`, or `event_id` in
+JSON/JSONL rows, and the equivalent `--signal-search-run-id`, `--fact-id`, or
+`--event-id` flags for one request. These references reuse canonical evidence
+in single calls and synchronous batches of at most 25. Durable batches of
+26-5,000 reject canonical references instead of silently rediscovering them.
+JSON output exposes the normalized customer-facing signal fields; human output
+prints the signal type, verified source URL, date, company name, and domain.
+
 Retrieve completed Company/Copy result pages within seven days. If retention
 expires, the CLI returns non-retryable `BATCH_RESULTS_EXPIRED`; do not
 automatically rerun the submission because provider work may already have been
@@ -118,31 +142,27 @@ recoverable REST job for inputs larger than 25; the CLI waits by default or
 returns `job_id`, `idempotency_key`, and an exact resume command with
 `--no-wait`. Find Email, Verify Email, and Company Signal Enrichment use 25-row
 pages; Signal to Copy uses 100-row pages. Large Find Email and Verify Email
-batches honor `--max-wait-ms` and `--poll-interval-ms`. Durable Signal to Copy jobs use
-persisted, eligible company-signal data only and never start live providers or
-deep research. Large Copy inputs with fresh, deep, skip-cache, per-row
-idempotency, or synchronous-only controls fail locally before HTTP; split those
-requests into batches of at most 25. Company Signal `signal_run_id` recovery
+batches honor `--max-wait-ms` and `--poll-interval-ms`. Durable Signal to Copy jobs
+complete missing company-signal research before generating copy and accept
+uniform `--deep-search` controls. Company Signal `signal_run_id` recovery
 rows likewise stay in direct batches of at most 25. Large Company Signal jobs
 persist bounded result pages and exclude rejected candidate-evidence
 diagnostics; use `--include-candidate-evidence` only with batches of at most 25.
 
-Every command uses the authenticated workspace. Find Email and Verify Email
-honor that workspace's configured cache window; eligible hits cost 0 credits,
-while fresh discovery or verification is charged on every plan. Builder, Team,
-Agency, and Pay-As-You-Go include fresh Company Signals. Team and Agency also
-include Unlimited Signal to Copy AI; Signal to Copy remains callable on other
-plans under the standard product contract. These plans still check eligible
-workspace signal data first even when Company Signals is set to No cache.
-`--lookback-days` remains a hard evidence-age bound for both
-cached and fresh Company Signals and Signal to Copy results.
+Every command uses the authenticated workspace. Find Email costs 1 credit per
+returned result and Verify Email costs 0.02 credits per returned terminal result
+on every plan. Signaliz automatically reuses eligible evidence and prevents
+duplicate provider work. Builder, Team, Agency, and Pay-As-You-Go include
+Company Signals. Signal to Copy costs 1 credit per successful result on Free and
+Builder, and is unlimited on Team and Agency. `--lookback-days` remains a hard
+evidence-age bound.
 
 Signals Everything is a query-first company discovery command rather than a
 row batch. It returns only dated, source-linked signals that contain both a
 company name and company domain. The default request is 100 companies and the
 maximum is 1,000. It is included on Builder, Team, and Agency plans, is resumable with
-`signal_search_run_id`, and reports a strict source-cost guardrail: results are
-only returned when source cost is below $0.01 per qualified company. A request
+`signal_search_run_id`, and reports measured source cost plus target warnings
+without rejecting a valid run solely on a projected preflight estimate. A request
 is a ceiling, not a promise: it can return fewer results when public evidence
 cannot verify both a date and company identity. Use `--icp-context` to qualify
 an open-ended signal request against a target market.