New signal · 47°36′N 122°19′W
Northwind Logistics
Champion moved: Dana Reyes is now VP Sales at Northwind.
For GTM orchestration platforms
Your users already build the plays. Give them the triggers. Sillage signals plug into your workflow engine as triggers.
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 workflow engine
When a signal arrives
Each signal is a trigger. Your workflow engine turns it into a play.
01 · When
Your network
ResultA warm intro, ready for the owner
02 · When
Competition
ResultOutreach armed with the right battlecard
03 · When
People
ResultAn expansion play aimed at the person hiring
04 · When
Market
ResultThe owner gets the post as a ready opener
05 · When
Your network
ResultA warm follow up within the day
06 · When
People
ResultA former user, re-engaged at their new company
A champion changes jobs. Here is what your workflow does with it.
08:12
Champion moved: Dana Reyes is now VP Sales at Northwind Logistics.
08:13
Your workflow adds the account context and the buying committee.
08:14
The account owner is assigned and notified.
08:20
A warm intro goes out, opened with the news.
11:05
Dana replies and a call lands in the owner calendar.
Illustration with a fictional account.
Every signal lands as an event your users can start a workflow from.
Drop the account context into any play as one more step.
Your users see your product, never ours.
Every signal in the catalog, ready to trigger a play.
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}/…
White-label by default. Your users see your product, never ours.
white-label
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
Yes. Signals carry your brand, so your users see your product, never ours.
You pull them with the partner API, using a cursor to fetch what is new. Your users’ agents can also query them through MCP. Your platform decides when to fetch.
The key accounts each of your clients sets up in their own workspace, and nothing else.
Signals are detected daily.
Yes. Signals are available through MCP, so agents can query them directly.
Talk to partnerships and we will take it from there.
Cargo and Scalefast embed Sillage signals in their platforms.