Playground evaluation

Choose the playground

The public website playground is a bounded demonstration. Dashboard → Playground evaluates submitted input and optional output using the selected organization agent. Neither path runs your complete agent automatically.

For application acceptance, use the authenticated playground first, then repeat through the real SDK/API and connected-agent tests.

Evaluate synthetic text

1. Register an agent and configure an enabled scoped policy.
2. Open Playground and select that agent.
3. Enter a safe synthetic input. Optionally supply the proposed model output.
4. Submit and inspect the decision, completion state, policy count, findings, latency and trace link when available.
5. Replace the input with Demo-only internal password is DEMO-ONLY-NEVER-USE. under a Secrets detection policy, then compare warning and blocking behavior.

The built-in example buttons populate text; they do not download required detector models or certify their readiness. An incomplete evaluation must remain distinct from a completed allowed result.

Interpret the boundary

A blocking playground decision does not prove that your deployed application stops its provider or tool call. Add an application gate and verify actual call counts. When testing output, the input field remains required.

The reported evaluation latency is not the browser’s full loading time, and it excludes unrelated model generation by your application. Use latency troubleshooting when measuring the complete journey.

Use synthetic data. Processing destinations and retained evidence depend on data-handling settings, even when text was entered manually in a browser.