Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.guardway.ai/llms.txt

Use this file to discover all available pages before exploring further.

​
What this is for

Playground is an in-dashboard chat UI that sends real requests through your activated gateway. Use it to smoke-test a provider after connecting it, debug guardrails, validate routing rules, or compare models side-by-side without writing any client code. Every playground request flows through the gateway exactly like a production call, so it’s also the fastest way to verify a change to providers, models, routing, or guardrails.
Playground requests originate from the Guardway platform, not your browser. A Healthy pill in the dashboard only proves the gateway can reach the Guardway control plane outbound — it does not prove the platform can reach the gateway inbound. For Playground to work, the gateway must be published and reachable over the internet at the URL you connected (a public hostname / port, a tunnel, or a reverse proxy with TLS). A gateway running only on a private LAN will register and heartbeat fine, but every Playground request will fail to connect.

​
Options

ControlWhat it does
ProviderFilters the model list to one provider.
ModelAny enabled chat model from the selected provider and gateway.
System promptOptional textarea. Sets the system message.
Temperature0–2. Default 1. Lower is more deterministic.
Max tokensUpper bound on completion length.
Top-PNucleus sampling.
StreamingToggle. When on, tokens arrive incrementally.
The right rail surfaces Request JSON and Response JSON tabs so you can copy the exact payload into your own client.

​
Requirements

  • At least one Healthy gateway — see Activate.
  • At least one provider attached to that gateway with valid credentials — see Providers.
  • At least one enabled model — see Models.
If any of these is missing, the Playground shows an inline empty state with a link to the page that fixes it.

​
How to configure

Playground
1

Open Playground

Open Playground from the dashboard sidebar.
2

Pick a provider and model

Use the Provider dropdown to filter, then pick an enabled Model.
3

Set sampling parameters

Adjust Temperature, Max tokens, and Top-P as needed. Toggle Streaming on to see tokens arrive incrementally.
4

Send a prompt

Type into the chat box and press Send. The response renders in the chat pane and the Request / Response JSON tabs populate on the right.
5

Verify in Logs

Open Logs — the request appears with its trace ID, latency, and cost. Click the trace to see every step the gateway took.

​
Tips

Enable a PII rule under Configuration → Security, then paste a prompt containing a fake SSN into the Playground. The gateway should block or redact it depending on the rule’s action — and the trigger will show in the Guardrails tab of Logs.
Open Playground in two tabs, pick different models, send the same prompt. The Traces view in Logs lets you compare latency and cost after the fact.
The Request JSON tab shows the exact payload sent to the gateway, so you can drop it into your own client unchanged.
  • Logs — every Playground request is logged and traced.
  • Configuration → Routing — rules that decide which provider serves a Playground request.