Classify a batch
Return a Firewall verdict for each independent event in input order.
texts. For conversation-aware checks, use ordered single-event requests with the same metadata.conversationId. Batch classification neither reads nor updates conversation history.
Use your provisioned SILMARIL_API_URL as the full request URL. Inspect prediction and optional governance.action for every item in predictions before consuming it.
Choose cURL, TypeScript, JavaScript, Python, Go, or Java in the request examples. They use standard HTTP libraries; the Java example requires Java 17 or later.
BENIGN. See confidence scores for interpretation and threshold behavior.
Handle the verdict
HTTP200 returns a classification. In Block mode, stop an event when prediction is MALICIOUS or governance.action is block. In Warn or Shadow mode, record the would-block decision and continue.
Handle request failures with your application’s error policy. See modes and enforcement for the full decision model.
Optional review depth
The optional top-levelreview field accepts standard or deep. See review depth for requirements, selection behavior, and acknowledgement rules.
Review selection applies to the entire batch and is acknowledged on the batch envelope.Body
Independent events. Batch and input-size limits depend on your deployment.
11One metadata object or null per text. Length must match texts.
JSON metadata for this event. SDKs add request identity under silmaril. A conversationId connects ordered single-event calls when conversation history is supported. Batch metadata does not connect events into a sequence.
Optional request-wide review selection. standard selects standard review. deep requests an additional review of eligible potentially harmful events when available on your deployment. An event may complete without additional review. Omit review to inherit the deployment default. Review depth is independent of enforcement mode.
standard, deep "deep"
Response
One verdict per text in the predictions array, in input order. Malicious or governance-blocked items still return HTTP 200.
Authoritative batch-envelope acknowledgement present only when the request explicitly selected review. It applies to the entire request; prediction-item fields do not acknowledge the batch selection. It confirms the applied setting. An event may complete without additional review.
standard, deep "deep"