Stream key
local-businesses:salons-spas:madrid
First proof stream for Madrid salons/spas.
SignalKit v1
SignalKitrecurring signal streams for AgentLed agents.
SignalKit packages recurring signal streams that AgentLed agents can search, preview, subscribe to, receive, and mark inside governed workflows.
Unit
SignalSubscription
Delivery
review queue rows
Proof
Madrid salons/spas
Signal stream contract
local-businesses:salons-spas:madrid
SignalSubscription
Agent flow
01
search
Find a reusable stream
AgentLed agents ask for a known signal shape instead of starting from raw sourcing every run.
02
preview
Inspect evidence and fields
SignalKit shows sample rows, freshness, source coverage, and verifier status before a subscription exists.
03
subscribe
Set the recurring rule
A SignalSubscription defines stream key, cadence, row caps, workspace, and the review destination.
04
receive
Project rows into AgentLed
Agents receive workspace-scoped rows with evidence summaries, state, and enough context to route review.
05
mark
Record the outcome
Accepted, rejected, stale, duplicate, or needs-human-check decisions feed the next run without mixing customer rules into sourcing.
Projected row
AgentLed agent inbox
review-ready
Workspace
agentled-internal-signalkit-smoke
Stream
local-businesses:salons-spas:madrid
Projected rows
1 new salon/spa candidate
Review state
ready for AgentLed agent review
Next mark
accepted / rejected / stale / duplicate / needs-human-check
SignalKit keeps source runs, verifier state, and raw signal events server-side. AgentLed agents work from projected rows with evidence and review state.
01Stream contract
The product shape is a recurring stream, not a generic lead database.
An agent should know what it can request, what evidence comes back, how often the stream recurs, and where review state is stored.
Agent-readable stream API
SignalKit v1 stays narrow: define a stream, preview sample rows, subscribe with caps, receive projected rows, and mark outcomes after review.
02Boundary
AgentLed / SignalKit / Apify-source-provider boundary.
The split keeps AgentLed customer work, SignalKit stream state, and provider collection policy in their own lanes.
Commercial wrapper
AgentLed
Owns the customer workspace, agents, review queues, approval rules, and the contact path for teams that want recurring signal work run for them.
- AgentLed agents consume projected rows
- Human review stays in the operating loop
- Customer-specific fit logic lives here
Signal runtime
SignalKit
Owns recurring signal streams, subscriptions, verifier outcomes, freshness windows, and normalized signal rows for agent workflows.
- Searchable stream catalog
- SignalSubscription contract
- Evidence and state projection
Source provider boundary
Apify-source-provider
Runs source-specific collectors under server-side policy. Raw source work stays behind SignalKit before AgentLed sees projected rows.
- Source policies and run metadata
- Provider cost and freshness controls
- No customer-facing action from source runs
03First proof stream
Start with Madrid salons/spas, then prove recurrence before broadening.
The first proof stream is local-businesses:salons-spas:madrid. It gives AgentLed a concrete stream to validate with one workspace, one row shape, and reviewable outcomes.
Consumer
AgentLed Concierge
Receives reviewable business rows for an AgentLed workspace.
Evidence
Name, place source, category, freshness, verifier state
Enough for an agent to route review without exposing raw provider internals.
Action state
new, accepted, rejected, stale, duplicate, needs-human-check
Outcome marks improve the next recurrence and keep audit state visible.
AgentLed contact