Every finding. Every source cited.

Check any document against the rules it must follow.

The model doesn't decide what's true. You do — a statute, a standard or your own policy, saved as a Source Pack. VERA checks your document against that pack and only reports findings it can tie to a rule in it, with the source text quoted so you can check it yourself.

Start verifying →Build a source pack

Up to 50 pages per check.

UK GDPR privacyWCAG 2.2OWASP Top 10OWASP APISecurity headers
SUPPLIER-AGREEMENT.DOCX● SCANNING
checked against → Example pack: your Procurement Policy
SUPPLIER AGREEMENT — between Acme Ltd
("Client") and the Supplier named in Schedule A.
Payment terms: net 60 days from invoice date.
Late payment interest: 1.5% per month.
Governing law: England and Wales.
Warranty period: 30 days post-delivery.
IP vests in client upon full payment.
Confidentiality survives 3 years post-termination.
0 findings · 0 correctedof 3
VERA

Illustrative example. Your own policy, standard or statute becomes the Source Pack.

Why this beats asking an AI directly

An AI answering from memory can't show you its source. VERA shows the rule behind every finding.

Ask a general AI assistant to review a contract and it reasons from general training data — broad, sometimes outdated, sometimes citing a clause that doesn't exist. VERA reports only what it can tie to a rule in the sources you chose, and shows you that rule.

01

Choose your sources

The actual statute, your own policy, a style guide — the text you would check against yourself.

02

Save it as a Source Pack

Built once, reused for every future document of that type — legal, code, procurement, and more.

03

Every finding is tied to that pack

Findings VERA can't match to a rule in your pack are dropped. Each one that remains shows the rule it breaks and the source text behind it.

The output

Not just findings.
A fixed document.

Not a report you have to re-type from — a document you can send. Download as DOCX with tracked changes visible in Word, or PDF, or plain text. Pick a document type below to see it.

Original document
SUPPLIER AGREEMENT — between Acme Ltd
("Client") and the Supplier named in Schedule A.
Payment terms: net 60 days from invoice date.
Late payment interest: 1.5% per month.
Governing law: England and Wales.
Warranty period: 30 days post-delivery.
IP vests in client upon full payment.
Confidentiality survives 3 years post-termination.
VERA corrected
SUPPLIER AGREEMENT — between Acme Ltd
("Client") and the Supplier named in Schedule A.
Payment terms: net 30 days from invoice date.
↳ Procurement Policy §4.2 — “Supplier invoices must be paid within 30 calendar days.”
Late payment interest: at the rate set out in Schedule C.
↳ Procurement Policy §4.5 — “Late-payment interest must follow the rate in Schedule C.”
Governing law: England and Wales.
Warranty period: 12 months post-delivery.
↳ Procurement Policy §7.1 — “Goods must carry a warranty of at least 12 months.”
IP vests in client upon full payment.
Confidentiality survives 3 years post-termination.
Download asDOCX with track changesPDFTXT· Every finding tied to a rule in your pack

Illustrative example. Your own policy, standard or statute becomes the Source Pack.

New

A live page can drift from what's actually correct.
Catch it before a customer does.

Your agent can already read a live webpage. Connect the same Source Packs via MCP, so it checks what's actually on the page — a price, a clause, a spec — against your real pricing sheet or policy, not its training data.

Connect your AI →
"Check this listing's price against our pricing sheet."
→verify_document(pack: "product-pricing")
Price mismatch — page shows $8.90, pricing sheet says $9.99. Correction ready, cited to the pricing sheet.

Every finding tied to a rule in your pack