@curviate/cli 0.47.0 → 0.49.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (48) hide show
  1. package/CHANGELOG.md +231 -1
  2. package/README.md +136 -88
  3. package/dist/{account-RFJ63QYL.js → account-2BH2Q6VG.js} +41 -31
  4. package/dist/chunk-3RCW7URJ.js +41 -0
  5. package/dist/{chunk-UJOTQPL6.js → chunk-5ZGTU4VD.js} +47 -14
  6. package/dist/chunk-D2S5OCYU.js +38 -0
  7. package/dist/{chunk-HOQ7EUHJ.js → chunk-FDJMAF7D.js} +1 -0
  8. package/dist/{chunk-ERBYEC5P.js → chunk-JYKYD57J.js} +1 -1
  9. package/dist/chunk-MGB6FE4A.js +58 -0
  10. package/dist/chunk-NNV2OYEF.js +23 -0
  11. package/dist/{chunk-76SWLAZ6.js → chunk-RXWODUWA.js} +43 -1
  12. package/dist/{chunk-V3MVOVQT.js → chunk-SA2QHAXG.js} +8 -1
  13. package/dist/chunk-TEAWYLPO.js +1493 -0
  14. package/dist/{chunk-PD2I5TYC.js → chunk-V7FJWTZW.js} +3 -3
  15. package/dist/{chunk-TC4ZPUWI.js → chunk-Y7MZZRYR.js} +21 -80
  16. package/dist/{chunk-FXYK2GTO.js → chunk-Z7OQSWBD.js} +38 -33
  17. package/dist/chunk-ZYURL5VK.js +83 -0
  18. package/dist/cli.js +79 -98
  19. package/dist/{comment-MCXE7B7V.js → comment-MRDPDA33.js} +29 -24
  20. package/dist/{company-EUUN372H.js → company-2AEHSGHA.js} +57 -52
  21. package/dist/{config-K4G3VSBA.js → config-NRBKHXES.js} +13 -5
  22. package/dist/{connect-2AL7XVJO.js → connect-4XEBV5V3.js} +42 -38
  23. package/dist/core-RGU2SCBN.js +46 -0
  24. package/dist/{doctor-WPYI7X2T.js → doctor-BZ4DA7DV.js} +9 -5
  25. package/dist/document-RKHRWXNT.js +27 -0
  26. package/dist/{draft-G65DVXT7.js → draft-C5N6EOO5.js} +27 -22
  27. package/dist/enrollment-BNQOUKI7.js +472 -0
  28. package/dist/examples-NIMSIXMV.js +53 -0
  29. package/dist/{exit-codes-AW6KHDDN.js → exit-codes-TLMKTLRI.js} +1 -1
  30. package/dist/{feed-HV24WME4.js → feed-DFUU7SUJ.js} +15 -11
  31. package/dist/{group-HADXNVJW.js → group-CSD2OWOZ.js} +17 -13
  32. package/dist/{inbox-G3EE54OB.js → inbox-SNSPWI7J.js} +23 -19
  33. package/dist/{inboxes-237XOBTP.js → inboxes-RIRHPS4H.js} +18 -14
  34. package/dist/{job-LIN6RWD7.js → job-6PNXXZNF.js} +31 -27
  35. package/dist/{login-OHAHNBRW.js → login-Y7JBAHCW.js} +10 -5
  36. package/dist/{message-U2O2JQSW.js → message-2IK4MBBG.js} +10 -8
  37. package/dist/motion-7ATUXO6R.js +946 -0
  38. package/dist/{notification-3VG32LWM.js → notification-VYK5NDEB.js} +19 -15
  39. package/dist/{post-ECDK2KJL.js → post-AN6T2OJF.js} +35 -30
  40. package/dist/{profile-JOHS6SDW.js → profile-UQY64642.js} +46 -42
  41. package/dist/{recruiter-7VXEIXN3.js → recruiter-OY4RN5HH.js} +122 -119
  42. package/dist/{sales-nav-K4BMBH7R.js → sales-nav-KLODLYMW.js} +36 -30
  43. package/dist/{search-C2UYO6PI.js → search-NWP5S6CF.js} +68 -58
  44. package/dist/{setup-GYEZFDEN.js → setup-YPPFLH2N.js} +14 -9
  45. package/dist/{webhook-KCOQOH7D.js → webhook-OHKBL3YS.js} +51 -55
  46. package/package.json +2 -2
  47. package/dist/chunk-KJ24DIAJ.js +0 -60
  48. package/dist/examples-IJL3A6SZ.js +0 -18
package/README.md CHANGED
@@ -54,7 +54,7 @@ active profile, base URL, which precedence tier the credential came from
54
54
  connected accounts with their status. It exits `0` when every check passes and
55
55
  with the first failing check's code otherwise.
56
56
 
57
- `doctor` also names the workspace the credential belongs to, but only when the
57
+ `curviate doctor` also names the workspace the credential belongs to, but only when the
58
58
  key it resolved is one `curviate setup` wrote to a profile. A key from
59
59
  `CURVIATE_API_KEY` or `--api-key` may belong to another workspace entirely, so
60
60
  it is reported as unknown rather than guessed at.
@@ -110,6 +110,15 @@ Global flags available on every command:
110
110
  --timeout Request timeout in milliseconds (default: 30000)
111
111
  ```
112
112
 
113
+ Every LinkedIn action (profiles, companies, jobs, invitations, search, inboxes,
114
+ messages, posts, comments, Sales Navigator, Recruiter, groups, feed, LinkedIn
115
+ notification cards, drafts) is under `curviate core`: one action now, from one
116
+ account. `curviate core` lists them. Setup, accounts and webhooks stay at the top
117
+ level. Pre-0.48.0 paths without `curviate core` exit 2 and send nothing.
118
+
119
+ Documents go in files, never on the command line: `--file <path>`, or `--file -`
120
+ with a heredoc or a pipe.
121
+
113
122
  For full command reference see [docs.curviate.com](https://docs.curviate.com).
114
123
 
115
124
  ## Examples
@@ -119,15 +128,15 @@ These examples show how coding agents compose the CLI in real workflows.
119
128
  ### 1. Find people and send connection requests
120
129
 
121
130
  Search for matching profiles, preview the invitations, then send them once satisfied.
122
- `--location` on `search people` takes location **ids**, not free text; resolve a
123
- human-readable place name to an id first with `curviate search parameters --type LOCATION`:
131
+ `--location` on `curviate core search people` takes location **ids**, not free text; resolve a
132
+ human-readable place name to an id first with `curviate core search parameters --type LOCATION`:
124
133
 
125
134
  ```bash
126
- curviate search parameters --type LOCATION --keywords "Berlin" --account acc_1 --json
135
+ curviate core search parameters --type LOCATION --keywords "Berlin" --account acc_1 --json
127
136
  # {"items":[{"id":"103035651","name":"Berlin, Germany"}, {"id":"106967730","name":"Berlin, Berlin, Germany"}, ...]}
128
137
 
129
138
  # Look first, a search is a read, so it just runs (no --preview on reads)
130
- curviate search people \
139
+ curviate core search people \
131
140
  --keywords "AI engineer" \
132
141
  --location 103035651 \
133
142
  --account acc_1 \
@@ -135,12 +144,12 @@ curviate search people \
135
144
  --json
136
145
 
137
146
  # Preview a single write before sending, then pipe IDs into connect, one request per person
138
- curviate connect "$SOME_ID" --account acc_1 --note "Hi, I'd love to connect." --preview
147
+ curviate core connect "$SOME_ID" --account acc_1 --note "Hi, I'd love to connect." --preview
139
148
 
140
- curviate search people --keywords "AI engineer" --location 103035651 --account acc_1 --all \
149
+ curviate core search people --keywords "AI engineer" --location 103035651 --account acc_1 --all \
141
150
  | jq -r '.id' \
142
151
  | head -5 \
143
- | xargs -I{} curviate connect {} --account acc_1 --note "Hi, I'd love to connect."
152
+ | xargs -I{} curviate core connect {} --account acc_1 --note "Hi, I'd love to connect."
144
153
  ```
145
154
 
146
155
  ### 2. Triage the inbox and extract unread threads
@@ -155,18 +164,18 @@ human-readable sender comes from the chat's own `user.display_name` instead (pre
155
164
  1:1 chats):
156
165
 
157
166
  ```bash
158
- curviate inbox list --json --all --account acc_1 \
167
+ curviate core inbox list --json --all --account acc_1 \
159
168
  | jq -c 'select(.unread_count > 0) | {chat_id: .id, sender: (.user.display_name // .last_message.sender_id), preview: .last_message.text[0:80]}'
160
169
  ```
161
170
 
162
- `inbox list` reads one folder per call, `primary` by default. An archived chat never appears
171
+ `curviate core inbox list` reads one folder per call, `primary` by default. An archived chat never appears
163
172
  in a `primary` walk, no matter the `--limit` or how far `--cursor`/`--all` page through it;
164
- pass `--inbox archived` to reach it. `inmail` and `starred` are alternate views over chats
173
+ pass `--inbox archived` to reach it. `--inbox inmail` and `--inbox starred` are alternate views over chats
165
174
  `primary` already returns, useful as a narrower filter rather than for reachability. All six
166
- values: `primary`, `inmail`, `archived`, `spam`, `jobs`, `starred`.
175
+ values: `--inbox primary|inmail|archived|spam|jobs|starred`.
167
176
 
168
177
  ```bash
169
- curviate inbox list --json --all --account acc_1 --inbox archived
178
+ curviate core inbox list --json --all --account acc_1 --inbox archived
170
179
  ```
171
180
 
172
181
  ### 3. Warm up a prospect by reacting to their recent posts
@@ -178,9 +187,9 @@ envelope, not a bare array:
178
187
  ```bash
179
188
  PROFILE_URL="https://www.linkedin.com/in/example"
180
189
 
181
- curviate profile "$PROFILE_URL" --posts --fields id --account acc_1 --json \
190
+ curviate core profile "$PROFILE_URL" --posts --fields id --account acc_1 --json \
182
191
  | jq -r '.items[].id' \
183
- | xargs -I{} curviate post react {} --account acc_1 --reaction like
192
+ | xargs -I{} curviate core post react {} --account acc_1 --reaction like
184
193
  ```
185
194
 
186
195
  ### 4. Check entitlement before a Sales Navigator sweep
@@ -192,7 +201,7 @@ Navigator subscription) or `BETA_NOT_ENABLED` (the workspace has not opted into
192
201
  Branch on the exit code for the retry decision and read the code for the remedy:
193
202
 
194
203
  ```bash
195
- curviate sales-nav search people --keywords "VP Engineering" --account acc_1 --json \
204
+ curviate core sales-nav search people --keywords "VP Engineering" --account acc_1 --json \
196
205
  || {
197
206
  code=$?
198
207
  if [ "$code" -eq 5 ]; then
@@ -214,7 +223,7 @@ cat webhook-payload.json \
214
223
  | curviate webhook verify \
215
224
  --secret "$CURVIATE_WEBHOOK_SECRET" \
216
225
  --header "$CURVIATE_SIG_HEADER" \
217
- --body -
226
+ --file -
218
227
  ```
219
228
 
220
229
  Exit `0` means the signature is valid and the parsed event is written to stdout as JSON.
@@ -234,49 +243,49 @@ curviate account list --all --json \
234
243
 
235
244
  ### 7. Search jobs, then fetch full detail on the top result
236
245
 
237
- `job get` accepts either a job URL or the bare numeric id, including the `job_urn` field a
246
+ `curviate core job get` accepts either a job URL or the bare numeric id, including the `job_urn` field a
238
247
  job-search result already returns:
239
248
 
240
249
  ```bash
241
- curviate search jobs --keywords "founding engineer" --location "Berlin" --account acc_1 --json \
250
+ curviate core search jobs --keywords "founding engineer" --location "Berlin" --account acc_1 --json \
242
251
  | jq -r '.items[0].job_urn' \
243
- | xargs -I{} curviate job get {} --account acc_1 --json
252
+ | xargs -I{} curviate core job get {} --account acc_1 --json
244
253
 
245
254
  # A pasted job URL works identically:
246
- curviate job get "https://www.linkedin.com/jobs/view/4428113858" --account acc_1
255
+ curviate core job get "https://www.linkedin.com/jobs/view/4428113858" --account acc_1
247
256
  ```
248
257
 
249
258
  ## Company
250
259
 
251
- Company commands (`curviate company ...`) are Core-tier reads. `company <id>` accepts a public
260
+ Company commands (`curviate core company ...`) are Core-tier reads. `curviate core company <id>` accepts a public
252
261
  handle (the slug in `linkedin.com/company/<handle>`) or a numeric id; the four sub-resource
253
- commands require the company's **numeric provider id**, the `id` field `company <id>` returns.
262
+ commands require the company's **numeric provider id**, the `id` field `curviate core company <id>` returns.
254
263
  `--account` (or a configured default account) is required on all of them, unless exactly one account is connected.
255
264
 
256
265
  ### 1. Retrieve a company, then list its employees
257
266
 
258
267
  ```bash
259
- curviate company t-systems --account acc_1 --json | jq -r '.id' \
260
- | xargs -I{} curviate company employees {} --keywords "engineer" --limit 10 --account acc_1 --json
268
+ curviate core company t-systems --account acc_1 --json | jq -r '.id' \
269
+ | xargs -I{} curviate core company employees {} --keywords "engineer" --limit 10 --account acc_1 --json
261
270
  ```
262
271
 
263
272
  ### 2. Page through a company's posts and jobs
264
273
 
265
274
  ```bash
266
- curviate company posts 112013061 --limit 5 --account acc_1 --json
267
- curviate company jobs 112013061 --all --account acc_1 --json # streams every page
275
+ curviate core company posts 112013061 --limit 5 --account acc_1 --json
276
+ curviate core company jobs 112013061 --all --account acc_1 --json # streams every page
268
277
  ```
269
278
 
270
279
  ## Drafts and scheduled posts
271
280
 
272
- A Draft is a stored, editable, unpublished post. Give it an account and `--schedule-at` and Curviate publishes it at that time. Drafts are tenant-wide: `--account` is optional and is never defaulted from your config, so a Draft you create without it has no account yet. `curviate post create` still publishes immediately and does not schedule.
281
+ A Draft is a stored, editable, unpublished post. Give it an account and `--schedule-at` and Curviate publishes it at that time. Drafts are tenant-wide: `--account` is optional and is never defaulted from your config, so a Draft you create without it has no account yet. `curviate core post create` still publishes immediately and does not schedule.
273
282
 
274
283
  ### 1. Draft a post, schedule it, change your mind
275
284
 
276
285
  ```bash
277
- curviate draft create "Three things we learned shipping our first agent integration." --account acc_1 --schedule-at 2026-10-12T09:00:00+02:00 --json
278
- curviate draft update drf_1 --unschedule --json # back to a plain Draft
279
- curviate draft publish drf_1 --json # or publish now: prints the post id
286
+ curviate core draft create "Three things we learned shipping our first agent integration." --account acc_1 --schedule-at 2026-10-12T09:00:00+02:00 --json
287
+ curviate core draft update drf_1 --unschedule --json # back to a plain Draft
288
+ curviate core draft publish drf_1 --json # or publish now: prints the post id
280
289
  ```
281
290
 
282
291
  `--schedule-at` is an ISO 8601 time with an offset, 5 minutes to 365 days ahead, passed to the API unchanged. Two scheduled Drafts on one account must be at least 5 minutes apart.
@@ -284,8 +293,8 @@ curviate draft publish drf_1 --json # or publish now: pri
284
293
  ### 2. Attach media
285
294
 
286
295
  ```sh
287
- curviate draft create "Launch day." --account acc_1 --attach shot1.png --attach shot2.png --json
288
- curviate draft update drf_1 --attach demo.pdf --json # appends; existing files stay
296
+ curviate core draft create "Launch day." --account acc_1 --attach shot1.png --attach shot2.png --json
297
+ curviate core draft update drf_1 --attach demo.pdf --json # appends; existing files stay
289
298
  ```
290
299
 
291
300
  Up to 20 images (JPEG, PNG, GIF, WEBP, each up to 5 MiB), or one MP4 video, or one PDF (each up to 50 MiB), never mixed. An image over 5 MiB is refused before anything is sent. Files up to 5 MiB go inline in the request; larger ones are uploaded separately, in the order you gave them.
@@ -293,16 +302,50 @@ Up to 20 images (JPEG, PNG, GIF, WEBP, each up to 5 MiB), or one MP4 video, or o
293
302
  ### 3. List what is queued, and what went out
294
303
 
295
304
  ```bash
296
- curviate draft list --status scheduled --account acc_1 --order asc --json
297
- curviate draft list --status published --from 2026-10-01T00:00:00Z --json # publish records, not Drafts
298
- curviate draft list --account none --all --json # Drafts with no account, every page
305
+ curviate core draft list --status scheduled --account acc_1 --order asc --json
306
+ curviate core draft list --status published --from 2026-10-01T00:00:00Z --json # publish records, not Drafts
307
+ curviate core draft list --account none --all --json # Drafts with no account, every page
308
+ ```
309
+
310
+ A scheduled post that fails to publish becomes a `failed` Draft with a `failure` code; any `curviate core draft update` on it clears the failure. Failed `outcome_unknown` means the post may be live: check the account's posts before retrying.
311
+
312
+ ## Motions and Enrollments
313
+
314
+ A Motion runs one Sequence for the Contacts of your Contact lists, from its sending accounts, paced on a schedule. It is created as a draft and does nothing until you start it. An Enrollment is one Contact in one Motion on one account. Both belong to your team: `--account` is never read from your config for them.
315
+
316
+ ### 1. From a template to a running Motion
317
+
318
+ ```bash
319
+ curviate motion init --template connect-and-converse --output motion.json # offline; fill contact_list_ids and account_ids
320
+ curviate motion lint --file motion.json # offline: the rules the API applies
321
+ curviate motion create --file motion.json --json
322
+ curviate motion preview mot_1 --sample 3 --json # rendered messages and the budget projection; spends nothing
323
+ curviate motion start mot_1 --json
324
+ ```
325
+
326
+ `curviate motion lint` prints one line per finding, compiler style, and exits 2 on any error:
327
+
328
+ ```text
329
+ motion.json:7:32 error R12 pause.wait: must be a duration between 1m and 365d: a number then m, h or d, like 30d. Use a duration between 1m and 365d, for example 1d. -> https://docs.curviate.com/reference/sequence-rules#r12
330
+ ```
331
+
332
+ `curviate motion create` and `curviate motion update` check the same way before anything is sent. `curviate motion get mot_1 --json` prints a file `curviate motion update mot_1 --file -` accepts as is; add `--if-revision <n>` to refuse the save when someone changed the Sequence since you read it.
333
+
334
+ ### 2. Find and fix Enrollments
335
+
336
+ ```bash
337
+ curviate enrollment list --motion mot_1 --done-step opener --outcome failed --json
338
+ curviate enrollment retry enr_1 --json # only a failed Step; waits for the re-run and prints its outcome
339
+ curviate enrollment bulk --action retry --motion mot_1 --done-step opener --outcome failed --json
340
+ curviate enrollment pause enr_1 --json
341
+ curviate enrollment resume enr_1 --json # lifts your pause
299
342
  ```
300
343
 
301
- A scheduled post that fails to publish becomes a `failed` Draft with a `failure` code; any `draft update` on it clears the failure. Failed `outcome_unknown` means the post may be live: check the account's posts before retrying.
344
+ `curviate enrollment resume <id> --at <step>` is a jump, not a retry: it re-enters that Step even when it already sent. `curviate enrollment retry` never sends a delivered message again.
302
345
 
303
346
  ## Sales Navigator
304
347
 
305
- Sales Navigator commands (`curviate sales-nav ...`) are **beta**: this surface has not been
348
+ Sales Navigator commands (`curviate core sales-nav ...`) are **beta**: this surface has not been
306
349
  exercised against a real Sales Navigator subscription yet, so its responses may still move.
307
350
 
308
351
  There is no Sales Navigator add-on to buy from Curviate and no tier on a seat: one ordinary
@@ -312,18 +355,18 @@ the JSON body: `NO_ACTIVE_SEAT` (no Curviate seat covers the account, fix it in
312
355
  `LINKEDIN_FEATURE_NOT_SUBSCRIBED` (the LinkedIn account lacks the subscription, fix it on
313
356
  LinkedIn) or `BETA_NOT_ENABLED` (a human enables beta in Settings, or pass `--beta` for this
314
357
  call). Branch on the exit code the same way as example 4 above, and read the code for the
315
- remedy. Write commands (`save-lead`, `save-account`, `message new`) accept `--preview` to
358
+ remedy. Write commands (`curviate core sales-nav save-lead`, `curviate core sales-nav save-account`, `curviate core sales-nav message new`) accept `--preview` to
316
359
  render the request without sending it.
317
360
 
318
361
  ### 1. Search Sales Navigator profiles, then get one full profile
319
362
 
320
363
  ```bash
321
- curviate sales-nav search people \
364
+ curviate core sales-nav search people \
322
365
  --keywords "VP Engineering" \
323
366
  --account acc_1 \
324
367
  --limit 5 \
325
368
  | jq -r '.items[0].id' \
326
- | xargs -I{} curviate sales-nav profile {} --account acc_1
369
+ | xargs -I{} curviate core sales-nav profile {} --account acc_1
327
370
  ```
328
371
 
329
372
  ### 2. Save a lead to a specific lead list
@@ -331,12 +374,12 @@ curviate sales-nav search people \
331
374
  Preview first, then send. `--list` is required; the save always targets a specific list.
332
375
 
333
376
  ```bash
334
- curviate sales-nav save-lead ACwAAA1234567 \
377
+ curviate core sales-nav save-lead ACwAAA1234567 \
335
378
  --account acc_1 \
336
379
  --list 987654 \
337
380
  --preview
338
381
 
339
- curviate sales-nav save-lead ACwAAA1234567 --account acc_1 --list 987654
382
+ curviate core sales-nav save-lead ACwAAA1234567 --account acc_1 --list 987654
340
383
  ```
341
384
 
342
385
  ### 3. Start a new Sales Navigator chat
@@ -344,7 +387,7 @@ curviate sales-nav save-lead ACwAAA1234567 --account acc_1 --list 987654
344
387
  `--subject` is required for Sales Navigator messaging.
345
388
 
346
389
  ```bash
347
- curviate sales-nav message new \
390
+ curviate core sales-nav message new \
348
391
  --to ACwAAA1234567 \
349
392
  --account acc_1 \
350
393
  --subject "An opportunity at our company" \
@@ -354,7 +397,7 @@ curviate sales-nav message new \
354
397
  ### 4. Search Sales Navigator companies
355
398
 
356
399
  ```bash
357
- curviate sales-nav search companies \
400
+ curviate core sales-nav search companies \
358
401
  --keywords "series B fintech" \
359
402
  --account acc_1 \
360
403
  --limit 5 --json \
@@ -364,14 +407,14 @@ curviate sales-nav search companies \
364
407
  ### 5. List saved-account and saved-lead lists
365
408
 
366
409
  ```bash
367
- curviate sales-nav account-lists --account acc_1
368
- curviate sales-nav lead-lists --account acc_1
410
+ curviate core sales-nav account-lists --account acc_1
411
+ curviate core sales-nav lead-lists --account acc_1
369
412
  ```
370
413
 
371
414
  ### 6. Browse a saved-account list, filtered to starred accounts
372
415
 
373
416
  ```bash
374
- curviate sales-nav browse-account-list 987654 \
417
+ curviate core sales-nav browse-account-list 987654 \
375
418
  --account acc_1 \
376
419
  --filter STARRED \
377
420
  --sort-by NAME \
@@ -382,7 +425,7 @@ curviate sales-nav browse-account-list 987654 \
382
425
  ### 7. Browse a saved-lead list, spotlighting recent job changes
383
426
 
384
427
  ```bash
385
- curviate sales-nav browse-lead-list 456789 \
428
+ curviate core sales-nav browse-lead-list 456789 \
386
429
  --account acc_1 \
387
430
  --spotlight RECENT_POSITION_CHANGE \
388
431
  --json \
@@ -392,17 +435,17 @@ curviate sales-nav browse-lead-list 456789 \
392
435
  ### 8. Save a company into an account list
393
436
 
394
437
  ```bash
395
- curviate sales-nav save-account 112013061 \
438
+ curviate core sales-nav save-account 112013061 \
396
439
  --account acc_1 \
397
440
  --list 987654 \
398
441
  --preview
399
442
 
400
- curviate sales-nav save-account 112013061 --account acc_1 --list 987654
443
+ curviate core sales-nav save-account 112013061 --account acc_1 --list 987654
401
444
  ```
402
445
 
403
446
  ## Recruiter
404
447
 
405
- Recruiter commands (`curviate recruiter ...`) are **beta**: this surface has not been exercised
448
+ Recruiter commands (`curviate core recruiter ...`) are **beta**: this surface has not been exercised
406
449
  against a real Recruiter subscription yet, so its responses may still move.
407
450
 
408
451
  There is no Recruiter add-on to buy from Curviate and no tier on a seat: one ordinary paid seat
@@ -412,42 +455,46 @@ subscription. A refusal is **exit code `5`** with one of three codes in the JSON
412
455
  `LINKEDIN_FEATURE_NOT_SUBSCRIBED` (the LinkedIn account lacks the subscription, fix it on
413
456
  LinkedIn) or `BETA_NOT_ENABLED` (a human enables beta in Settings, or pass `--beta` for this
414
457
  call). The surface is project-centric: most
415
- operations are scoped to a hiring project id. Write commands (`save-candidate`, `project update`,
416
- `project-job create`/`update`, `job create`/`publish`/`close`, `message new`) accept `--preview`
458
+ operations are scoped to a hiring project id. Write commands (`curviate core recruiter save-candidate`, `curviate core recruiter project update`,
459
+ `curviate core recruiter project-job create`, `curviate core recruiter project-job update`, `curviate core recruiter job create`,
460
+ `curviate core recruiter job publish`, `curviate core recruiter job close`, `curviate core recruiter message new`) accept `--preview`
417
461
  to render the request without sending it.
418
462
 
419
463
  ### 1. List hiring projects
420
464
 
421
465
  ```bash
422
- curviate recruiter projects --account acc_1 --limit 20 --json \
466
+ curviate core recruiter projects --account acc_1 --limit 20 --json \
423
467
  | jq -r '.items[] | "\(.id)\t\(.name)"'
424
468
  ```
425
469
 
426
470
  ### 2. Inspect a project, its pipeline, and its attached job posting
427
471
 
428
- `recruiter project-job get` returns the single job posting attached to a project (a
472
+ `curviate core recruiter project-job get` returns the single job posting attached to a project (a
429
473
  `RESOURCE_NOT_FOUND` / exit `4` when none is attached).
430
474
 
431
475
  ```bash
432
- curviate recruiter project "$PROJECT_ID" --account acc_1 --json
433
- curviate recruiter pipeline "$PROJECT_ID" --account acc_1 --json
434
- curviate recruiter project-job get "$PROJECT_ID" --account acc_1 --json
476
+ curviate core recruiter project "$PROJECT_ID" --account acc_1 --json
477
+ curviate core recruiter pipeline "$PROJECT_ID" --account acc_1 --json
478
+ curviate core recruiter project-job get "$PROJECT_ID" --account acc_1 --json
435
479
  ```
436
480
 
437
481
  ### 3. Create a job posting draft, then publish it
438
482
 
439
- `recruiter job create` requires `--project-name` (the hiring project the posting opens) plus the
440
- full v2 job body: `--job-title`, `--company-id`/`--company-name`, `--workplace-type`, `--location`,
483
+ `curviate core recruiter job create` requires `--project-name` (the hiring project the posting opens) plus the
484
+ full v2 job body: `--job-title-id` with `--job-title`, `--company-id`/`--company-name`, `--workplace-type`, `--location`,
441
485
  `--employment-status`, `--seniority-level`, `--description` (200 characters minimum), `--industry`,
442
- `--job-function`, and `--apply-method`. `--location`/`--industry`/`--job-function` take resolved
443
- parameter ids, the same `search parameters --type LOCATION`/`--type INDUSTRY`/`--type JOB_FUNCTION`
444
- resolution from example 1 above. `recruiter job publish` is project-scoped and requires `--mode`
486
+ `--job-function`, and `--apply-method` (with `--notification-email` or `--website-url`), from flags or a
487
+ `--file <path|->` JSON document; the CLI checks the merged body against the published schema before
488
+ sending and lists every problem at once. `--location`/`--industry`/`--job-function` take resolved
489
+ parameter ids, the same `curviate core search parameters --type LOCATION`/`--type INDUSTRY`/`--type JOB_FUNCTION`
490
+ resolution from example 1 above. `curviate core recruiter job publish` is project-scoped and requires `--mode`
445
491
  (`FREE | PROMOTED | PROMOTED_PLUS`); the paid modes also require the full `--budget-*` triple.
446
492
 
447
493
  ```bash
448
- curviate recruiter job create \
494
+ curviate core recruiter job create \
449
495
  --account acc_1 \
450
496
  --project-name "Backend Hiring 2026" \
497
+ --job-title-id 9 \
451
498
  --job-title "Senior Backend Engineer" \
452
499
  --company-name "Curviate GmbH" \
453
500
  --workplace-type REMOTE \
@@ -458,32 +505,33 @@ curviate recruiter job create \
458
505
  --industry 96 \
459
506
  --job-function 15 \
460
507
  --apply-method linkedin \
508
+ --notification-email jobs@example.com \
461
509
  --json
462
510
 
463
- curviate recruiter job publish "$PROJECT_ID" "$JOB_ID" --account acc_1 --mode FREE --json
511
+ curviate core recruiter job publish "$PROJECT_ID" "$JOB_ID" --account acc_1 --mode FREE --json
464
512
  ```
465
513
 
466
514
  ### 4. List applicants in a project, then get one applicant's detail
467
515
 
468
- `recruiter applicants` is project-scoped and requires `--channel-id` (the project's own
516
+ `curviate core recruiter applicants` is project-scoped and requires `--channel-id` (the project's own
469
517
  JOB_POSTING talent-pool channel). Applicant detail and résumé are also project-scoped.
470
518
 
471
519
  ```bash
472
- curviate recruiter applicants "$PROJECT_ID" --channel-id "$CHANNEL_ID" --account acc_1 --limit 10 --json \
520
+ curviate core recruiter applicants "$PROJECT_ID" --channel-id "$CHANNEL_ID" --account acc_1 --limit 10 --json \
473
521
  | jq -r '.items[0].id' \
474
- | xargs -I{} curviate recruiter applicant "$PROJECT_ID" {} --account acc_1
522
+ | xargs -I{} curviate core recruiter applicant "$PROJECT_ID" {} --account acc_1
475
523
  ```
476
524
 
477
525
  ### 5. Download an applicant's resume
478
526
 
479
527
  ```bash
480
- curviate recruiter applicant resume "$PROJECT_ID" APPLICANT_ID --account acc_1 -o resume.pdf
528
+ curviate core recruiter applicant resume "$PROJECT_ID" APPLICANT_ID --account acc_1 -o resume.pdf
481
529
  ```
482
530
 
483
531
  ### 6. Save a candidate to a project pipeline stage
484
532
 
485
533
  ```bash
486
- curviate recruiter save-candidate "$PROJECT_ID" \
534
+ curviate core recruiter save-candidate "$PROJECT_ID" \
487
535
  --account acc_1 \
488
536
  --stage-id "$STAGE_ID" \
489
537
  --candidate-id AEM789
@@ -492,24 +540,24 @@ curviate recruiter save-candidate "$PROJECT_ID" \
492
540
  ### 7. Search Recruiter people
493
541
 
494
542
  ```bash
495
- curviate recruiter search people \
543
+ curviate core recruiter search people \
496
544
  --keywords "senior backend engineer" \
497
545
  --account acc_1 \
498
546
  --limit 5 --json \
499
547
  | jq -r '.items[] | "\(.id)\t\(.full_name // .headline)"'
500
548
 
501
549
  # A pasted Recruiter search / talent-pool URL runs directly:
502
- curviate recruiter search "https://www.linkedin.com/talent/search?..." --account acc_1 --json
550
+ curviate core recruiter search "https://www.linkedin.com/talent/search?..." --account acc_1 --json
503
551
  ```
504
552
 
505
553
  ### 8. Get a Recruiter-enriched profile, then start a chat with them
506
554
 
507
- `recruiter message new` is JSON-only and requires `--subject` and `--signature`.
555
+ `curviate core recruiter message new` is JSON-only and requires `--subject` and `--signature`.
508
556
 
509
557
  ```bash
510
- curviate recruiter profile "https://www.linkedin.com/in/example" --account acc_1 --json
558
+ curviate core recruiter profile "https://www.linkedin.com/in/example" --account acc_1 --json
511
559
 
512
- curviate recruiter message new \
560
+ curviate core recruiter message new \
513
561
  --to AEM789 \
514
562
  --account acc_1 \
515
563
  --subject "A role you'd be a great fit for" \
@@ -519,15 +567,15 @@ curviate recruiter message new \
519
567
 
520
568
  ### 9. List your postings, and get any public job posting through the Recruiter lens
521
569
 
522
- Unlike `recruiter jobs` (which lists postings you manage), `recruiter job get` retrieves the full
570
+ Unlike `curviate core recruiter jobs` (which lists postings you manage), `curviate core recruiter job get` retrieves the full
523
571
  detail of *any* public LinkedIn job posting, the Recruiter-seated counterpart to the top-level
524
- `job get` command:
572
+ `curviate core job get` command:
525
573
 
526
574
  ```bash
527
- curviate recruiter jobs --account acc_1 --limit 10 --json \
575
+ curviate core recruiter jobs --account acc_1 --limit 10 --json \
528
576
  | jq -r '.items[] | "\(.id)\t\(.title)\t\(.state)"'
529
577
 
530
- curviate recruiter job get "https://www.linkedin.com/jobs/view/4428113858" --account acc_1 --json
578
+ curviate core recruiter job get "https://www.linkedin.com/jobs/view/4428113858" --account acc_1 --json
531
579
  ```
532
580
 
533
581
  ## Retrieval modes
@@ -550,7 +598,7 @@ threshold: that combination is a usage error (exit `2`) before any request is
550
598
  sent.
551
599
 
552
600
  Available on the four reads that can be served from a stored copy:
553
- `profile <id>`, `profile me`, `inbox get` and `inbox messages`. The activity
601
+ `curviate core profile <id>`, `curviate core profile me`, `curviate core inbox get` and `curviate core inbox messages`. The activity
554
602
  listings on the profile commands (`--posts`, `--comments`, `--reactions`,
555
603
  `--followers`) do not accept them and reject them with exit `2`.
556
604
 
@@ -573,28 +621,28 @@ this API simply holds no copy, so re-checking the id is the wrong move. It is
573
621
  not a failure either. The fix is another mode, and it is never worth retrying
574
622
  as sent, because the answer cannot change until you change the mode.
575
623
 
576
- `inbox messages` is the strictest case. The store answers it only for an
624
+ `curviate core inbox messages` is the strictest case. The store answers it only for an
577
625
  unfiltered, uncursored first page, only after a walk of the whole chat reached
578
626
  its end, and only when the chat's whole message set fits in that one page
579
627
  (`--limit`, at most 25). Any unfiltered page fetched from LinkedIn (such as
580
628
  `--mode live` without `--all`) restarts the walk, and
581
- `inbox messages <chat_id> --all` walks to the end and closes it. A read
629
+ `curviate core inbox messages <chat_id> --all` walks to the end and closes it. A read
582
630
  carrying `--before`, `--after` or `--cursor` is never served from the store and
583
631
  `--all` does not change that, so a chat with more messages than one page holds
584
632
  exits `14` under `--mode cache_only` however it is walked.
585
633
 
586
634
  ```bash
587
635
  # The default: a fresh stored copy if there is one, otherwise fetch
588
- curviate profile me --account acc_1 --json
636
+ curviate core profile me --account acc_1 --json
589
637
 
590
638
  # Serve whatever is stored at any age, and fetch only if nothing is
591
- curviate profile me --account acc_1 --mode refill --json
639
+ curviate core profile me --account acc_1 --mode refill --json
592
640
 
593
641
  # Accept a stored copy up to five minutes old, otherwise fetch
594
- curviate profile me --account acc_1 --max-age 300 --fields first_name,source,observed_at --json
642
+ curviate core profile me --account acc_1 --max-age 300 --fields first_name,source,observed_at --json
595
643
 
596
644
  # A single chat from the store, never LinkedIn. Exit 14 if nothing is stored.
597
- curviate inbox get 2-AbCdEf== --account acc_1 --mode cache_only --json
645
+ curviate core inbox get 2-AbCdEf== --account acc_1 --mode cache_only --json
598
646
  ```
599
647
 
600
648
  ## Exit codes
@@ -606,7 +654,7 @@ curviate inbox get 2-AbCdEf== --account acc_1 --mode cache_only --json
606
654
  | 2 | Usage / argument error |
607
655
  | 3 | Authentication or authorization failure |
608
656
  | 4 | Resource not found |
609
- | 5 | No active seat, the LinkedIn account lacks the subscription, or beta consent is missing |
657
+ | 5 | Someone must act first: no active seat, the LinkedIn account lacks the subscription, beta consent is missing, the plan is below the Tier the action needs, or a teammate with the right role (or the Account's own person) must do it |
610
658
  | 6 | Rate limited |
611
659
  | 7 | Transient platform error (retry likely to succeed) |
612
660
  | 8 | Account or connection state blocks the request |