Request history
Primary Router investigation path: decisions, conversations, answers, thinking and masking receipts.
Primary Router investigation path: decisions, conversations, answers, thinking and masking receipts.
This screen belongs to the Router deployment operator, not an ordinary hosted customer. Hosted customers have a separate account page with their own keys and limits; policy and service settings are not exposed there. Contact the operator to change protection. In the operator console, open the route listed above; a report tenant filter does not automatically scope a global setting.
Examples use educational data. Use your own authorized tenant in real integrations. Each screenshot shows the actual frontend, with the source and educational/demo mode stated below it.
Step-by-step actions
- Open Request history → Router requests.
- Enter your request ID or select tenant and period.
- Open the record and compare action, perimeter, reason, model and detected classes.
- Expand Input, Output and Thinking; review raw JSON and masking receipt when available.
- Choose the desired window before downloading CSV.
Every control and its meaning
| Control / parameter | Values, units and effect |
|---|---|
| Запросы Router / Задачи клиентов | The first mode investigates gateway calls; the second covers asynchronous worker jobs. Select it before filtering. |
| Поиск, tenant, Request ID | Use a request ID for an exact investigation; the record tenant must match the integration key. |
| Период, действие, периметр, класс, tier | Narrow the selection; model, injection, cache and error filters are also available. Dates use UTC. |
| Input / Output / Thinking | Open these in a record when content was captured. Thinking depends on the provider and reasoning_effort; an absent panel does not mean no processing. |
| Настройки IAM.Secure | Masking mode, floor and content capture are separate settings; the tenant filter does not make them tenant-specific. |
Verify the result
A blocked record should include a reason; a routed record should identify its upstream. Repeat a synthetic request after changing a setting and locate its new request ID.
Errors, disabling and reverting changes
Content cannot be recovered from SHA-256 alone. If capture was disabled or retention expired, use metadata and a new synthetic request. Resetting filters changes the display, not policy.
2026-10-15 · Actual staging application. Synthetic client, public definitions or aggregate test-stand metrics only; not customer statistics or a benchmark. Original pixels are unmodified; personal profile and private data excluded. Auto is shown without changing global protection. This screenshot does not establish mode durability.
- Full-text search
- Search
- Masking mode
- Router floor
Detailed security settings · Traffic analysis · FAQ · All application sections
Unicode and mask coordinates
Inspection detects sensitive values even when hidden characters split them. Mask highlighting and response restoration use the original request positions and values: whitespace, line breaks and Unicode outside masked spans stay unchanged. This also applies to long requests. If mask consistency cannot be verified, Router stops forwarding rather than sending partially hidden data.