Actions - Originalis API

Actions run Originalis analysis pipelines on demand: POST /deals/analyze (website, document link, or file upload), POST /founders/analyze, and POST /research. They differ from reads in four deliberate ways:

Write-scoped key required — read-only keys get 403.
Separate budget — charged only when a run actually dispatches.
Always asynchronous — every action returns 202 immediately with a status_url; analysis takes minutes.
One status vocabulary — every action reports queued → running → succeeded | failed, and a succeeded action’s result_url points back into the read API. Results are ordinary resources, never a second schema.

Poll with backoff

DEAL=$(curl -s -X POST -H "X-API-Key: $KEY" -H "Content-Type: application/json" \
  -d '{"website_url": "https://acmerobotics.com"}' \
  "https://api.originalis.ai/api/v1/deals/analyze")
STATUS_URL="https://api.originalis.ai$(echo "$DEAL" | jq -r '.status_url')"
while :; do
  S=$(curl -s -H "X-API-Key: $KEY" "$STATUS_URL" | jq -r '.status')
  [ "$S" = "succeeded" ] || [ "$S" = "failed" ] || { sleep 30; continue; }
  break
done
curl -s -H "X-API-Key: $KEY" "https://api.originalis.ai$(echo "$DEAL" | jq -r '.result_url')"

Duplicate protection

A concurrent submission for the same target (the same company domain in your org; the same document link) returns 409 rather than silently starting a second run. Founder analysis is org-deduped: if your org already assessed the founder, you get the existing analysis back with existing: true — no new run, no spend.

Prefer push over poll? Status reads carry live progress, every analysis resource has an SSE stream, and webhooks fire on terminal states.