@scrappycoco/cli 0.8.0 → 0.8.2

package/README.md

@@ -73,6 +73,20 @@ Use `--json` for machine-readable responses. Execution commands support
 poll for completion. When `--output` is used, records go to the file and a
 compact execution summary remains on stdout.
 
+Canonical Run request files use `providers` as a top-level array and
+`provider_options` keyed by provider ID:
+
+```json
+{
+  "input": {"query": "unified API for scraping"},
+  "providers": ["exa"],
+  "provider_options": {"exa": {}}
+}
+```
+
+Do not use a singular `provider` field. With flags, use repeatable
+`--provider <id>` instead.
+
 For a long run, add `--detach` to return a job ID immediately, then finish with
 `scrappycoco jobs wait <job-id> --output results.json`. Use
 `scrappycoco jobs get <job-id>` for a single status check or

package/dist/index.js

@@ -1119,6 +1119,12 @@ function splitScraperId(value) {
 }
 async function requestPayload(options, scraperId) {
   const fromFile = options.file ? await readJsonFile(options.file) : {};
+  if ("provider" in fromFile) {
+    throw new CliError(
+      'Run request files use "providers": ["provider_id"] (plural), or pass the repeatable --provider flag.',
+      EXIT.usage
+    );
+  }
   const { source, capability } = splitScraperId(scraperId);
   const input = options.input ? parseJsonObject(options.input, "input JSON") : fromFile.input;
   if (!input) throw new CliError("Provide input through --file or --input.", EXIT.usage);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@scrappycoco/cli",
-  "version": "0.8.0",
+  "version": "0.8.2",
   "description": "CLI for Scrappycoco scraper discovery and execution",
   "type": "module",
   "bin": {