Reading a Clay Run from the CLI or REST with the Clay CLI

1. curl POST /routines/{id}/run          -> routine_run_id  -> clay routines runs get <id>
2. clay routines runs start --input      -> routineRunId    -> curl GET /routines/run/{id}/results
3. compare the data arrays from both
4. clay routines runs start --bulk       -> routineRunId    -> curl GET /routines/run-batch/{id}/results

Using the Clay CLI and curl, show that a routine run started by one client can be read by the other.

Requirements:
- Authenticate both with the same Public API key in CLAY_API_KEY, and run the CLI from an empty HOME so a stored login is not used. With only the key, `clay routines runs start` and `clay routines runs get` work.
- Use the "Company Domain" routine, function:t_0tjqm9rUjfGY4MunGDM, input "Company Name", result { "Domain": "<domain>" }, 1 credit per row.
- Inline start over REST: POST /routines/{id}/run with { items: [{ id, inputs }] } returns { routine_run_id, status }. Read it with `clay routines runs get <id>`.
- Inline start with the CLI: `clay routines runs start <id> --input file.json` returns { routineRunId, mode: "inline", status }. Read it with GET /routines/run/{id}/results.
- Bulk start with the CLI: `clay routines runs start <id> --bulk rows.jsonl` returns { routineRunId, mode: "bulk", status, fileId }. Read it with GET /routines/run-batch/{id}/results, which returns routine_run_id, status, total, finished, and result_url once complete.
- Inline results are under data in both clients. Bulk results are in a separate file behind result_url (REST) or resultUrl (CLI). Never print those URLs.
- Poll with `clay routines runs get` every 5 seconds for up to 2 minutes.
- Run the verification step below before finishing.

#!/bin/bash
# Start a run with one client and read it with the other. Needs CLAY_API_KEY; runs the CLI from an empty HOME.
set -u
BASE=https://api.clay.com/public/v0
R=function:t_0tjqm9rUjfGY4MunGDM
CL=${CLAY_BIN:-clay}
EH=$(mktemp -d)
cli() { env -i PATH="$PATH" HOME="$EH" CLAY_API_KEY="$CLAY_API_KEY" "$CL" "$@"; }
rest() { curl -s -H "clay-api-key: $CLAY_API_KEY" -H "content-type: application/json" "$@"; }
wait_cli() { for _ in $(seq 1 24); do s=$(cli routines runs get "$1" | jq -r .status); [ "$s" != in_progress ] && break; sleep 5; done; }
echo '{"items":[{"id":"r1","inputs":{"Company Name":"Notion"}}]}' > one.json
printf '%s\n' '{"id":"b1","inputs":{"Company Name":"Figma"}}' '{"id":"b2","inputs":{"Company Name":"Linear"}}' > two.jsonl

echo "== 1. start over REST, read with the CLI"
start=$(rest -X POST "$BASE/routines/$R/run" -d @one.json); echo "REST start:  $(echo "$start" | jq -c .)"
id=$(echo "$start" | jq -r .routine_run_id); wait_cli "$id"
echo "CLI get:     $(cli routines runs get "$id" | jq -c 'del(.workspace)')"

echo "== 2. start with the CLI, read over REST"
start=$(cli routines runs start $R --input one.json | jq 'del(.workspace)'); echo "CLI start:   $(echo "$start" | jq -c .)"
id=$(echo "$start" | jq -r .routineRunId); wait_cli "$id"
echo "REST result: $(rest "$BASE/routines/run/$id/results" | jq -c .)"

echo "== 3. same run, both views: are the data arrays equal?"
a=$(cli routines runs get "$id" | jq -c .data); b=$(rest "$BASE/routines/run/$id/results" | jq -c .data)
[ "$a" = "$b" ] && echo "data arrays equal" || echo "data arrays differ"

echo "== 4. bulk run started with the CLI, read over REST"
start=$(cli routines runs start $R --bulk two.jsonl | jq 'del(.workspace)'); echo "CLI bulk start: $(echo "$start" | jq -c .)"
id=$(echo "$start" | jq -r .routineRunId); wait_cli "$id"
echo "REST bulk results: $(rest "$BASE/routines/run-batch/$id/results" | jq -c '{routine_run_id, status, total, finished, has_result_url: (.result_url != null)}')"
echo "CLI bulk get keys: $(cli routines runs get "$id" | jq -c 'del(.workspace) | {routineRunId, mode, status, total, finished, has_resultUrl: (.resultUrl != null)}')"

CLAY_BIN=$(command -v clay) bash parity.sh

== 1. start over REST, read with the CLI
REST start:  {"routine_run_id":"run_0tmtmb9CSrKHReWt9bx","status":"in_progress"}
CLI get:     {"routineRunId":"run_0tmtmb9CSrKHReWt9bx","mode":"inline","total":1,"finished":1,"status":"complete","data":[{"id":"r1","status":"complete","result":{"Domain":"notion.com"}}]}
== 2. start with the CLI, read over REST
CLI start:   {"routineRunId":"run_0tmtmbrDa76RUSPoyUG","mode":"inline","status":"in_progress"}
REST result: {"routine_run_id":"run_0tmtmbrDa76RUSPoyUG","status":"complete","total":1,"finished":1,"data":[{"id":"r1","status":"complete","result":{"Domain":"notion.com"}}]}
== 3. same run, both views: are the data arrays equal?
data arrays equal
== 4. bulk run started with the CLI, read over REST
CLI bulk start: {"routineRunId":"run_0tmtmc48DekZmqUQW7w","mode":"bulk","status":"in_progress","fileId":"file_0tmtmc3E2vdaJvzGvQq"}
REST bulk results: {"routine_run_id":"run_0tmtmc48DekZmqUQW7w","status":"complete","total":2,"finished":2,"has_result_url":true}
CLI bulk get keys: {"routineRunId":"run_0tmtmc48DekZmqUQW7w","mode":"bulk","status":"complete","total":2,"finished":2,"has_resultUrl":true}

inline id on bulk endpoint:
{"message":"No inline or bulk run found with id 'run_0tmtmbrDa76RUSPoyUG'"} [404]
bulk id on inline endpoint:
{"message":"Run 'run_0tmtmc48DekZmqUQW7w' is a batch run. Fetch its results from GET /public/v0/routines/run-batch/run_0tmtmc48DekZmqUQW7w/results."} [404]

verification:
  status: verified
  tested_at: "2026-10-12"
  product_version: "clay 1.9"
  command: "CLAY_BIN=$(command -v clay) bash parity.sh"
  expected_result: "Runs started over REST are readable with the CLI and the reverse, data arrays are equal, and the bulk run exposes a result URL through both clients."