Connect a runtime

Send the first governed decision, confirm it lands in the right workspace, and inspect the resulting approval and proof path.

Use this page when

Use this page for the first successful runtime connection. If you already have governed traffic in Studio, move to Approval flow or Artifacts and fields.

Before you begin

create a workspace API key
choose one runtime to test first
start with one low-risk decision
know which workspace should receive the result

Do this

Set the base URL and workspace key.
Send one governed decision.
Check whether the decision auto-closes or enters review.
Open replay or proof to confirm that the same decision vocabulary survived the full path.

Environment

export OSUITE_BASE_URL="https://studio.osuite.ai"
export OSUITE_API_KEY="<workspace-key>"
export OSUITE_APPROVAL_MODE="workspace"

First decision example

{
  "workspace_id": "ws_live_demo",
  "actor": "openai_agents_sdk",
  "destination_type": "managed_runtime",
  "summary": "Run the first governed decision",
  "requires_approval": true,
  "tool_name": "ticket.create"
}

What success looks like

the request lands in the expected workspace
the same decision vocabulary appears in request, review, and proof
the receipt explains whether the path auto-closed or entered approval
replay or proof can be inspected without custom translation work

Common first-run mistakes

Mistake	What it looks like	Fix
Wrong base URL	The request never lands in the expected workspace	Confirm `OSUITE_BASE_URL` first
Wrong workspace key	The request works, but artifacts are missing from the page you inspect	Re-issue the key from the workspace you are actually testing
Too much risk in the first decision	The review path becomes hard to reason about immediately	Start with one low-risk decision
Unclear destination type	The request reaches the wrong governance boundary	Pick one explicit destination type for the first run

Approval flow
Troubleshooting if the first run fails
PCAA once the path works end to end