Platform · InspectionEvery prompt, response, and tool-call — inspected in real time

18ms. Every call.
No exceptions,
no blind spots.

Obiguard's inspection pipeline sits in the critical path between your application and the model. Every token in and every token out is evaluated against the Criteria in your active Policy Sets before the call completes.

01 / How inspection works

Synchronous. In-path. Stateful.

Unlike async log-based tools, Obiguard evaluates policy before the response is returned. A blocked call never reaches the model — or the user.
01 — PROMPT

Prompt inspection

Every user prompt and system message is scanned for injection attempts, policy violations, PII, and off-scope content before the request reaches the model.

11 detectors · prompt & system
02 — RESPONSE

Response inspection

Model completions are inspected before delivery. Obiguard can redact, block, or flag content — with the original preserved in the audit ledger.

Redact · Block · Flag
03 — TOOL CALLS

Tool-call validation

Agent tool invocations are validated against your registered allow-list. Calls to out-of-scope tools are blocked — logged with full context.

~5ms added latency
02 / Detectors

11 detectors. Four kinds of criteria.

ML guard detectors cover jailbreak and prompt injection, PII, NSFW content, toxic language, gibberish, profanity, ban lists, and competitor mentions. Alongside them, a Criterion can be a keyword blocklist, a regular expression, or an LLM judge you write yourself.
11
ML guard detectors

Jailbreak/injection, PII, NSFW, toxicity, gibberish, profanity, ban list, competitor mentions, and format guards.

18ms
p50 added latency

Synchronous, in-path inspection — not a background log processor.

18
PII & SPI entity types

Email, phone, IP, location, person, URL — plus SSN, credit card, passport, IBAN, bank and driver licence numbers.

5
Frameworks mapped

Detector and policy activity feeds coverage against NIST AI RMF, ISO/IEC 42001, OWASP LLM Top 10, Malaysia’s AISCF, and Singapore’s MGF for GenAI.