Mask sensitive content in traces

Use Cases

Keeping system prompts out of stored traces while still tracing the request.
Excluding user-submitted content from logs to meet data-handling requirements.
Redacting model output from traces without changing what the caller receives.

The security parameter controls what gets written to stored traces. It does not change the live request or response: the caller always receives the full, unmasked output. Only the copy persisted to trace storage is affected.

Masking input, output, system, or all with security.mask only affects the copy of the request written to stored traces. The full, unmasked payload is still sent to the model provider. To prevent PII from leaving in the live request or response, enable the PII Redaction plugin.

security is set per request. There is no workspace, project, or API-key default. A request sent without a security block is traced in full. To mask consistently, include security.mask on every request, for example by setting it as a default on your SDK client so it is attached automatically.

Quick Start

curl -X POST https://api.orq.ai/v3/router/responses \
  -H "Authorization: Bearer $ORQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "openai/gpt-5.4-mini",
    "input": "Summarize AI trends for 2025",
    "security": { "mask": ["input"] }
  }'

import OpenAI from "openai";

const client = new OpenAI({
  apiKey: process.env.ORQ_API_KEY,
  baseURL: "https://api.orq.ai/v3/router",
});

const response = await client.responses.create({
  model: "openai/gpt-5.4-mini",
  input: "Summarize AI trends for 2025",
  // @ts-ignore - orq.ai extension
  security: { mask: ["input"] },
});

console.log(response.output_text);

from openai import OpenAI
import os

client = OpenAI(
    api_key=os.environ.get("ORQ_API_KEY"),
    base_url="https://api.orq.ai/v3/router",
)

response = client.responses.create(
    model="openai/gpt-5.4-mini",
    input="Summarize AI trends for 2025",
    extra_body={"security": {"mask": ["input"]}},
)

print(response.output_text)

const response = await client.chat.completions.create({
  model: "openai/gpt-5.4-mini",
  messages: [{ role: "user", content: "Summarize AI trends for 2025" }],
  // @ts-ignore - orq.ai extension
  security: { mask: ["input"] },
});

Configuration

Parameter	Type	Required	Description
`mask`	string[]	No	Which message roles to mask in stored traces: `input`, `output`, `system`, or `all`.

An unrecognized value in mask is rejected with a 400 error.

What each value masks

Value	Effect on stored traces
`input`	Blanks user message content, and (on tool spans) the tool-call arguments.
`system`	Blanks system and developer message content, and (on tool spans) the resolved tool variables. Also strips `description` and the parameter schema (`parameters` or `input_schema`) from tool definitions, keeping only name and type.
`output`	Blanks assistant message content, and (on tool spans) the tool-call result.
`all`	Shorthand for `input`, `system`, and `output` together.

Coverage

security is supported across the AI Gateway’s endpoints, including responses, chat/completions, completions, embeddings, images, ocr, rerank, speech, transcriptions, and translations. security is unrelated to the PII Redaction plugin, which rewrites sensitive values in the live request and response, and to Guardrails, which can block a request outright. security only changes what is written to trace storage.

Overview

APIs

Routing

Security & Privacy

Model Capabilities

Analytics & Monitoring

Integrations

Quick Start

Configuration

What each value masks

Coverage

​Quick Start

​Configuration

​What each value masks

​Coverage

Quick Start

Configuration

What each value masks

Coverage