Versioning Lifecycle

$
export BASE=https://api.smallest.ai/atoms/v1
$
export AUTH="Authorization: Bearer $SMALLEST_API_KEY"
$
export CT="Content-Type: application/json"
$
$
# 1. Create the agent.
$
AGENT_ID=$(curl -s -X POST "$BASE/agent" -H "$AUTH" -H "$CT" \
>
  -d '{"name": "lifecycle-demo", "language": {"switching": {"isEnabled": false}}}' \
>
  | jq -r '.data')
$
echo "agent: $AGENT_ID"
$
$
# 2. Find the Main branch. Each item in .data.branches is a BranchSummary
$
#    wrapper: {branch, isLive, hasOpenDraft, revisionsCount, headRevisionNumber}.
$
#    isDefault sits on the inner .branch, along with the branch _id.
$
MAIN_BRANCH_ID=$(curl -s "$BASE/agent/$AGENT_ID/branches" -H "$AUTH" \
>
  | jq -r '.data.branches[] | select(.branch.isDefault==true) | .branch._id')
$
echo "main branch: $MAIN_BRANCH_ID"
$
$
# 3. Write to the branch's draft. This upserts the open draft; if there is no
>
#    open draft, one is created. You can call this multiple times to build up
>
#    the draft before publishing.
>
#
>
# The body uses the same camelCase field names you see on GET /agent
>
# (globalPrompt, firstMessage, synthesizer, language, etc.). The server maps
>
# these into internal config-block sections (workflow_prompt, llm, voice, ...)
>
# for you; you don't send those section names directly.
$
curl -s -X PUT "$BASE/agent/$AGENT_ID/branches/$MAIN_BRANCH_ID/draft" \
>
  -H "$AUTH" -H "$CT" \
>
  -d '{
>
        "globalPrompt": "You are a friendly receptionist. Book appointments and answer questions.",
>
        "firstMessage": "Hi, how can I help?"
>
      }' | jq
$
$
# 4. Publish the draft. Optional label shows in the UI as the revision name.
$
#    The publish response carries only `state` (scanning or committed); it does
$
#    not include the new revision ID. Fetch the newest revision on the branch
$
#    to get its ID.
$
PUBLISH_RESP=$(curl -s -X POST "$BASE/agent/$AGENT_ID/branches/$MAIN_BRANCH_ID/draft/publish" \
>
  -H "$AUTH" -H "$CT" \
>
  -d '{"label": "Initial config"}')
$
$
STATE=$(echo "$PUBLISH_RESP" | jq -r '.data.state')
$
REVISION_ID=$(curl -s "$BASE/agent/$AGENT_ID/branches/$MAIN_BRANCH_ID/revisions?limit=1" \
>
  -H "$AUTH" | jq -r '.data.revisions[0]._id')
$
echo "publish state: $STATE, revision: $REVISION_ID"
$
$
# On the revision doc, the lifecycle field is `status` (published / draft /
>
# archived) and the scan lifecycle is on `securityCheck.status` (queued /
>
# passed / failed). Poll until the revision transitions to published.
$
while true; do
$
  REV_STATUS=$(curl -s "$BASE/agent/$AGENT_ID/branches/$MAIN_BRANCH_ID/revisions/$REVISION_ID" \
>
    -H "$AUTH" | jq -r '.data.revision.status')
$
  [ "$REV_STATUS" = "published" ] && break
$
  sleep 2
$
done
$
echo "revision is committed"
$
$
# 5. Start a test call against the newly-published revision.
$
curl -s -X POST "$BASE/agent/$AGENT_ID/branches/$MAIN_BRANCH_ID/test-call" \
>
  -H "$AUTH" -H "$CT" \
>
  -d "{\"revisionId\": \"$REVISION_ID\", \"mode\": \"webcall\"}" | jq
$
$
# 6. Main is already live for a new agent, so no /live call is needed here.
$
#    If you had published on a non-live branch, the corresponding call is:
$
#    curl -X POST "$BASE/agent/$AGENT_ID/branches/$BRANCH_ID/live" -H "$AUTH"
$
$
# 7. Place a real outbound call.
$
curl -s -X POST "$BASE/conversation/outbound" -H "$AUTH" -H "$CT" \
>
  -d "{\"agentId\": \"$AGENT_ID\", \"toPhone\": \"+15551234567\"}" | jq

$
# Fork Main into a staging branch.
$
STAGING_ID=$(curl -s -X POST "$BASE/agent/$AGENT_ID/branches" \
>
  -H "$AUTH" -H "$CT" \
>
  -d "{\"sourceBranchId\": \"$MAIN_BRANCH_ID\", \"name\": \"staging\"}" \
>
  | jq -r '.data._id')
$
$
# Edit and publish on staging. Real traffic keeps hitting Main.
$
curl -s -X PUT "$BASE/agent/$AGENT_ID/branches/$STAGING_ID/draft" \
>
  -H "$AUTH" -H "$CT" \
>
  -d '{"globalPrompt": "New experimental prompt."}' | jq
$
$
curl -s -X POST "$BASE/agent/$AGENT_ID/branches/$STAGING_ID/draft/publish" \
>
  -H "$AUTH" -H "$CT" -d '{"label": "Experimental v1"}' | jq
$
$
# Once you are happy, make staging live. Main becomes not-live automatically.
$
curl -s -X POST "$BASE/agent/$AGENT_ID/branches/$STAGING_ID/live" -H "$AUTH" | jq

$
# Find the revision you want to restore.
$
curl -s "$BASE/agent/$AGENT_ID/branches/$MAIN_BRANCH_ID/revisions?limit=20" -H "$AUTH" | jq
$
$
# Restore it.
$
curl -s -X POST \
>
  "$BASE/agent/$AGENT_ID/branches/$MAIN_BRANCH_ID/revisions/<REVISION_ID>/restore" \
>
  -H "$AUTH" | jq