Create Agent

Creates an agent. The agent is created enabled, but it has no recurring schedule and will not run on its own. Trigger a run yourself with Launch Signal Run, or set a recurring schedule from the Sillage app.

Credit usage

champion_tracking agents are not charged per tracked champion; they are metered only for the Discovery moves they find, the same way as other Discovery agents. Keyword agents (keyword_detection, keyword_post_search, job_posting_keyword_detection) are metered under keyword_signal for the keyword signals they detect. Track consumption with GET /v2/partner/usage.

Ten agent types are supported: keyword_detection, keyword_post_search, job_posting_keyword_detection, job_update, champion_tracking, plus five semantic watchlist types.

Note: For the five semantic watchlist types, a watchlist of the matching type is created automatically and bound to the new agent. Pass watchlist_id to bind an existing list instead — its type must equal the chosen agent type, otherwise the request returns 422.

champion_tracking works the same way, but always binds a profile watchlist of type champion — the same list a champion agent can bind to, simultaneously. Pass watchlist_id to bind an existing champion watchlist instead of creating one automatically; it must be of type champion, otherwise the request returns 422.

Minimum setup required

Most agent types need a usable persona and at least one target account before they can start monitoring — otherwise there is nothing to target. Before creating an agent of one of these types, the workspace must have:

• a persona with both a job title and a location set (having a persona on file is not enough on its own) — see Upsert persona, and
• at least one target account — see Add accounts.

job_update, job_posting_keyword_detection, and champion_tracking are exempt and can be created right away, since none of them is tied to a specific persona or account list.

If the workspace does not meet these requirements yet, the request is refused with 422 and a message naming the missing prerequisite.

Create an agent

Path parameters

Request body

Example request — keyword detection

curl -X POST "https://api.getsillage.com/api/v2/partner/workspaces/ws_123/agents" \
  -H "Authorization: Bearer $SILLAGE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Hiring signals",
    "type": "keyword_detection",
    "parameters": { "tracking_keywords": ["hiring", "expansion"] }
  }'

Example request — job posting keyword detection

curl -X POST "https://api.getsillage.com/api/v2/partner/workspaces/ws_123/agents" \
  -H "Authorization: Bearer $SILLAGE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Target accounts hiring platform roles",
    "type": "job_posting_keyword_detection",
    "parameters": {
      "tracking_keywords": ["Platform Engineer", "DevOps Engineer", "Site Reliability Engineer"]
    }
  }'

Example request — competitor watchlist (bound at creation)

curl -X POST "https://api.getsillage.com/api/v2/partner/workspaces/ws_123/agents" \
  -H "Authorization: Bearer $SILLAGE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Competitor tracker",
    "type": "competitor",
    "watchlist_id": 7
  }'

Example request — champion tracking (implicit watchlist)

curl -X POST "https://api.getsillage.com/api/v2/partner/workspaces/ws_123/agents" \
  -H "Authorization: Bearer $SILLAGE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Champion job change tracker",
    "type": "champion_tracking"
  }'

Example response

{
  "data": {
    "id": 42,
    "name": "Hiring signals",
    "type": "keyword_detection",
    "enabled": true,
    "parameters": {
      "tracking_keywords": ["hiring", "expansion"]
    },
    "watchlist_kind": null,
    "watchlist_id": null,
    "created_at": "2026-06-12T09:00:00.000Z",
    "updated_at": "2026-06-12T09:00:00.000Z"
  }
}

Response fields

The type returned in the response is one of keyword_detection, keyword_post_search, job_posting_keyword_detection, job_update, job_posting, competitor_activity, content_engagement, influencer_engagement or champion_tracking, plus the semantic watchlist types customer, competitor, partner, influencer and champion — watchlist-bound agents always return their semantic type, never an internal label.

Create and update accept ten types, each with its own body shape:

job_posting_keyword_detection tells you when one of your target accounts starts hiring for a role you care about: pass the role names as tracking_keywords (for example "Platform Engineer") and Sillage matches them against the title and description of the job postings those accounts publish.

For the watchlist-bound types, pass watchlist_id to attach an existing watchlist. If you omit it, a new empty watchlist of that type is created and bound to the agent — so an already-populated list you created separately would be left unattached. You can rebind afterwards with PUT /agents/{agent_id}.

Errors

Error responses use RFC 9457 problem documents with Content-Type: application/problem+json.