Docs/Start

Add runtime safety checks before autonomous AI systems act.

Connect LatentOps at the action boundary, review each proposed action, enforce the decision, and monitor the result in the dashboard.

Hosted APIhttps://api.latentops.space

1. AI system proposes a sensitive action

An agent wants to access private data, update a workflow, send an external message, approve a payment, call a tool, or change a system.

2. LatentOps reviews before execution

Send the prompt, action arguments, context, policy, and model metadata to the runtime review API.

3. Your runtime enforces the decision

Allow and warn can continue. Block and escalate stop the action before side effects happen.

4. Dashboard and audit trail update

Checks, incidents, model analytics, policy evidence, and audit exports update from the same event stream.

Hosted quickstart

Create a tenant API key, store it in a secret manager, and call LatentOps before your agent executes a tool. Send the key as X-API-Key.

bash

LATENTOPS_API_KEY=lo_your_tenant_key_here
LATENTOPS_API_BASE=https://api.latentops.space

curl -X POST "$LATENTOPS_API_BASE/v1/runtime/review" \
  -H "Content-Type: application/json" \
  -H "X-API-Key: $LATENTOPS_API_KEY" \
  -d '{
    "prompt": "Approve a high-value refund and email the customer confirmation",
    "tool_name": "workflow_api",
    "tool_args": {
      "action": "approve_refund",
      "amount_usd": 25000,
      "notify_external_customer": true
    },
    "repo_context": {
      "domain": "finance",
      "production_environment": true,
      "sensitive_data": true,
      "requires_human_approval": true
    },
    "trajectory": [
      {"step": "policy_check", "result": "second_approval_missing"}
    ],
    "policy": "balanced",
    "log_event": true
  }'

Workspace setup

Set up users, environment-specific API keys, policy ownership, alert routes, and one safe plus one risky validation check.

Members

Invite admins, operators, and viewers. Enterprise workspaces can enforce SSO/SAML and RBAC.

API keys

Create separate tenant keys for development, staging, production, CI, and each high-value integration.

Policies

Start with balanced, then add stricter rules for protected resources, private data, infra, secrets, deploys, and destructive actions.

Validation

Run one safe check and one intentionally risky check, then confirm checks, incidents, and audit exports update.

Authentication and keys

Dashboard access uses workspace membership. Agent/API access uses tenant keys. Enterprise workspaces can require SSO/SAML and RBAC.

bash

Settings -> API Keys -> Create key
Name: production-agent-gateway
Store as: LATENTOPS_API_KEY=lo_your_tenant_key_here
Send as: X-API-Key: lo_your_tenant_key_here

Do not expose keys

Use GitHub secrets, Vault, cloud secret managers, or protected environment variables.

Was this helpful?

Home APINext