Auto-revise safety
Auto-revise is useful. It is not magic.
Set auto_revise:true when you want VeracityAPI to clean up generic text. The safety contract is deliberately conservative: the revision pass may improve specificity and remove filler, but protected facts are checked deterministically before revised_text is returned. This is not guaranteed hallucination-free; it is guardrailed, auditable, and designed to fail closed.
Deterministic fact preservation checks
- Numbers and units.
- Money amounts and percentages.
- Dates.
- URLs, domains, and email addresses.
- Version/SKU-like tokens.
Fail-closed behavior
If the revision changes protected facts, VeracityAPI omits revised_text and returns revision_safety.status="failed" with concise failure categories. Your workflow should then route to a human editor or ask the generator to revise without changing protected facts.
What this does not guarantee
- It does not prove all factual claims are true.
- It does not catch every semantic shift or subtle implication change.
- It does not replace review for legal, medical, financial, or policy-sensitive content.
- It does not permit the model to invent prices, features, citations, customers, dates, or locations.
Response contract
{
"recommended_action": "revise",
"revision_safety": {
"status": "passed | failed",
"checks": ["numbers preserved", "URLs preserved", "email addresses preserved"],
"failure_reasons": []
},
"revised_text": "Only present when revision_safety.status=passed"
}