New signal · 47°36′N 122°19′W
Northwind Logistics
Champion moved: Dana Reyes is now VP Sales at Northwind.
For AI SDR and outbound agents
An agent that writes on a real signal gets replies. Sillage feeds yours champion moves, hiring, competitor activity, with the context to open.
Your network01
Northwind Logistics
Champion moved: Dana Reyes is now VP Sales at Northwind.
People02
Tessera Cloud
Job change: a VP Marketing just joined from a competitor.
Competition03
Orbis Payments
Their CTO mentioned a competitor in a public post.
Your agent
When a signal is detected
Each signal is a reason to reach out. Your agent turns it into the first line.
01 · When
Your network
ResultA warm opener aimed at a former champion
02 · When
People
ResultA message that starts from the open role
03 · When
Competition
ResultAn opener that speaks to what they are weighing
04 · When
Market
ResultAn opener that starts from their own words
05 · When
Your network
ResultA follow up on something they already liked
06 · When
People
ResultA reopened conversation at a new company
A champion changes jobs. Here is what your agent does with it.
08:12
Champion moved: Dana Reyes is now VP Sales at Northwind Logistics.
08:13
It pulls the account, the role and the history through MCP.
08:14
A short message that opens with the move, not a pitch.
08:20
The agent sends it from the right sender.
11:05
Dana answers and the agent hands over to a human.
Illustration with a fictional account.
Your agent always has something true and recent to write about.
Who moved, where, and why it matters, ready to drop into the opener.
Add accounts, not people. Your agents keep finding the right moment.
Every signal in the catalog, ready to open a conversation.
Your network
People
Competition
Market
Same signal, same quality. Flip the switch and watch it become yours.
New signal · 47°36′N 122°19′W
Northwind Logistics
Champion moved: Dana Reyes is now VP Sales at Northwind.
You hold one partner key. Each client you serve gets its own workspace, managed through the partner API.
/api/v3/partner/workspaces/{id}/…
Your agent reads signals through MCP or the pull query. You decide when it fetches.
MCP · pull query
Account monitoring is billed per key account per month. Discovery is billed per signal found.
per account · per month / per signal found
Set up
curl -X POST "https://api.getsillage.com/api/v3/partner/workspaces/ws_123/signal-setups" \
-H "Authorization: Bearer $SILLAGE_MASTER_KEY" \
-H "Content-Type: application/json" \
-d '{
"signal_template_id": 3,
"name": "Champion moved"
}'Pull new signals
curl -X POST "https://api.getsillage.com/api/v2/partner/workspaces/ws_123/signals/query" \
-H "Authorization: Bearer $SILLAGE_MASTER_KEY" \
-H "Content-Type: application/json" \
-d '{"limit": 25}'
{
"data": [
{
"id": 301,
"signal_type": "championMoved",
"detected_at": "2026-10-16T08:12:44Z",
"company_id": 456,
"excerpt": "Dana Reyes is now VP Sales at Northwind."
}
],
"meta": { "next_cursor": "eyJ...", "has_more": true }
}$ claude mcp add --transport http sillage https://api.getsillage.com/api/mcp/v2
It queries them through MCP, or you pull them with the partner API using a cursor. Your agent decides when to fetch.
The account, the person or post behind the signal, and a short excerpt your agent can open with.
The key accounts each of your clients sets up in their own workspace, and nothing else.
Signals are detected daily.
Yes. Signals carry your brand, so your users see your agent, never ours.
Talk to partnerships and we will take it from there.
Cargo and Scalefast embed Sillage signals in their platforms.