Create a signal agent
Create a signal agent: it watches X for the given keywords and scores
the people it finds against icp_description. Matching leads land in
Signals (and GET /v1/signals/leads) over the following minutes and
days; nothing is returned synchronously.
Omit keywords and 1-3 watches are suggested from the ICP (if
suggestion fails, nothing is created and you get 502
upstream_error). Omit destination_list_id and a contact list
named Leads: <agent name> is created for the leads, flagged
destination_list_created: true in the response.
Plan limits apply (403 cap_reached). Supports Idempotency-Key
(max 64 chars): retries with the same key and body replay the
original response with Idempotency-Replayed: true. Main account
only in v1 (optional account_id in the body must be the main
account).
Authorizations
A SuperX API key ("sxk_..."), created in the SuperX app under Account > API / MCP / CLI. Keys are server-side secrets.
Headers
Unique key (max 64 characters) for safe retries. Replays carry the "Idempotency-Replayed" response header set to "true". Keys are retained for 24 hours.
64Body
Agent name shown in SuperX.
80Who the ideal leads are; found people are scored against this.
500high = fewer, stricter matches; discovery = broader net.
high, discovery Plain-language descriptions of what the target customer posts about. Omit to auto-suggest from the ICP. Keywords beyond your plan's per-agent signal limit are dropped; the response lists the signals actually created.
1 - 5 elements180Contact list id (from GET /v1/contact-lists) that receives the leads. Omit to auto-create one.
Optional; must resolve to your main account.
Response
The created agent with its keyword signals, plus whether a destination list was auto-created.