Batch inspection

Inspect multiple texts with an individual result per item.

Inspect multiple texts with an individual result per item.

This screen belongs to the Secure 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

  1. Batch inspection → Lines; enter clean synthetic text and a separate synthetic email line.
  2. Choose request and docs-demo context.
  3. Run inspection and expand each result.
  4. For JSON use [{“id”:“clean”,“text”:“Hello”},{“id”:“email”,“text”:“docs@example.invalid”,“point”:“request”}].
  5. Export CSV and inspect per-item errors.

Every control and its meaning

Control / parameterValues, units and effect
Строки / JSONLines mode uses one nonempty line per item, maximum 1000. JSON is an array of id/text objects with optional point/context.
Точка инспекции / Pointrequest, response, attachment, tool_input, tool_output, web_content selects inspection point. JSON items supply their own point.
Контекст / AppLines-mode context is copied to each item; X-IAM-Secure-App, when shown, is separate application metadata.
Результаты / CSVPer-item verdicts/decisions/errors, tier, injection and latency. HTTP batch success does not mean every item succeeded.

Verify the result

Compare result count with nonempty items and IDs; batch dry-run does not prove upstream generation/delivery.

Errors, disabling and reverting changes

Invalid JSON, empty arrays or more than 1000 items require correction. Split the corpus and retry; use synthetic data for smoke checks.

Batch inspection form · actual staging
Batch inspection form · actual staging
2026-10-15 · Working staging interface, unretouched original pixels. Metrics and warnings belong to a test stand and are not a benchmark. Protection was not disabled; batch form shown before submission.
  1. Inspection point
  2. Tenant
  3. Text to inspect

Detailed security settings · Traffic analysis · FAQ · All application sections