Installation
Quick start
Configuration
Verification methods
verify(query)
Auto-detect and verify any claim.verifyMath(expression)
Verify mathematical expressions.verifyLogic(query)
Verify logical constraints using QWED-Logic DSL.verifyCode(code, options)
Check code for security vulnerabilities.verifyFact(claim, context)
Verify factual claims against a provided context.verifySQL(query, schema)
Validate SQL queries against a schema.verifyProcess(reasoningTrace, options)
New in v4.0.1
verifyRAG(targetDocumentId, retrievedChunks, options)
New in v4.0.1
verifyBatch(items)
Verify multiple items at once. The response is aBatchResponse whose items are per-item records — for math items the verdict is a DiagnosticResult nested under each item’s result, so inspect result.status, result.agent_message, result.developer_fields, and result.proof_ref individually instead of relying on an aggregate success rate.
math items, supply equality claims (e.g., 'x + x = 2*x') to receive proof results. Expressions without an = return status: 'UNVERIFIABLE' with the simplified form in developer_fields.simplified. The legacy is_valid boolean is preserved inside developer_fields.is_valid for backward compatibility.
Agent verification
New in v4.0.1
registerAgent(registration)
Register an agent and receive credentials for subsequent verification calls.verifyAgent(agentId, agentToken, query, options)
Updated in v5.0.0
getAgentBudget(agentId, agentToken)
Check the remaining budget for a registered agent.IRAC audit fields
All guard-related verification responses include IRAC-compliant audit fields for compliance reporting:Risk codes
Security-related responses may include arisk field indicating the type of threat detected:
TypeScript types
VerificationType enum
VerificationStatus enum
New in v5.0.0
VerificationStatus enum includes all possible status values returned by the verification API. Downstream consumers must handle INCONCLUSIVE, BLOCKED, and UNKNOWN as distinct outcomes.