Verified.Tools seals your documents with a cryptographic fingerprint tied to your verified identity — so anyone can prove, instantly, that what they received is exactly what you certified.
Over 25 years working with engineers and tens of thousands of engineering documents, Verified.Tools founder Ashley Gale saw the same pattern repeat: documents with valid digital signatures were being edited after signing. Customers were modifying engineering certificates, structural assessments, and compliance documents before submitting them for approval — and no one could tell.
A digital signature tells you a document was signed. Verified.Tools tells you it has not changed since. Any recipient can verify authenticity in seconds — no account, no software, no trust required.
Add a DNS TXT record to prove you own your domain (Level 1), then optionally add your ABN, NZBN, or other business ID (Level 2).
Upload any file. We compute a SHA-256 hash and bind it cryptographically to your verified identity.
Every certified document gets a permanent public URL. Send it with the document — to clients, councils, certifiers, anyone.
Recipients open the link, upload the file they received, and instantly see whether it matches the original. No account. No software.
The free tier is permanent — 2 documents a month, forever. Paid plans unlock volume, team seats, Level 2 verification, API access, webhooks, and more.
See full pricing →Distribute your documents confidently. Built in Australia by engineers who lived the problem firsthand.
SHA-256 hash bound to your verified company identity via HMAC. If a single byte changes, the verification URL immediately shows a mismatch.
Every document gets a tamper-evident public URL that never expires. Share alongside your document — councils, clients, and certifiers can verify in seconds without an account.
Create signature envelopes, send to multiple signers in sequence or in parallel, and track every event. Full audit trail on every signature action.
Level 1: DNS TXT record proves domain ownership. Level 2: ABN, NZBN, or equivalent cross-checked against government registries for the highest trust badge.
Subscribe to document.certified, document.revoked, signer.completed, and more. HMAC-signed payloads. Automatic retries with exponential backoff.
Every upload, share, sign, and revoke is appended to a tamper-evident audit log. Exportable at any time to support legal, regulatory, or insurance requests.
Invite team members as Admin or Certifier. Manage API keys, sessions, and MFA per user. Role-based permissions on every action.
Send a certified document to hundreds of recipients at once. Each gets a personalised verification link and email notification.
Connect any MCP-capable AI assistant to Verified.Tools. Upload, verify, list, revoke, and audit documents directly from Claude, GPT-4, or your own agent.
Full REST API with API key auth, rate limiting, sandbox mode, and detailed documentation covering every endpoint, error code, and webhook event.
Prices shown in AUD for Australian customers and NZD for New Zealand customers.
For individuals and sole traders who need occasional certification
Get started freeSmall engineering firms and consultancies
Start 14-day free trialMid-size firms, agencies, and high-volume certifiers
Start 14-day free trialFor enterprises with volume, custom SLA, and integration requirements
Contact salesAll paid plans include a 14-day free trial. Prices exclude GST.
Structural assessments, engineering certificates, compliance sign-offs, stamped drawings — these documents carry engineering liability and are routinely submitted to councils, builders, and certifiers. When a client modifies a document after it leaves an engineer's hands, the engineer may not know until something goes wrong. Verified.Tools makes every certified document self-evidently authentic.
Contracts, affidavits, deeds, statutory declarations. Verified.Tools gives law firms an auditable proof that the document a counterparty received is unaltered.
Building reports, pest inspections, section 32s, disclosure statements. Verify the report a buyer received is the one the inspector signed.
DA submissions, council reports, compliance certificates, planning documents. Provide certifiers and councils with an instantly verifiable record of the document as submitted.
Financial statements, audit reports, loan valuations, insurance assessments. Provide counterparties with cryptographic proof that the document matches the original.
Safety cases, equipment certifications, site hazard assessments. Safety-critical documents where tampering could have catastrophic consequences.
TGA conformity documents, medical device certifications, clinical reports. Regulatory compliance relies on the integrity of submitted documentation.
Full HTTPS REST API. API key auth, sandbox mode, rate limiting, and consistent error shapes across every endpoint.
Connect any MCP-capable AI assistant. Claude, GPT-4, or your own agent can upload, verify, list, and revoke documents via natural language.
Full documentation: authentication, every endpoint, error codes, webhook events, rate limits, sandbox guide, and going-live checklist.
Use vt_test_... API keys to test the full document lifecycle without touching production data. Auto-sign envelopes, advance the sandbox clock, and list sandbox emails — purpose-built for automated testing.
Verified.Tools was founded by Ashley Gale after more than 25 years working with engineers and technology across tens of thousands of engineering documents. In that time, Ashley saw the same problem repeat: documents bearing valid digital signatures were being quietly edited after they left the certifying engineer's hands.
Clients would alter structural assessments, compliance certificates, and engineering sign-offs before submitting them to councils, builders, and other parties. By the time the problem surfaced, there was no reliable way to prove what the original document said — only that it had been signed.
"A digital signature proves a document was signed. It does not prove it hasn't been changed since. We built Verified.Tools to close that gap."
Verified.Tools is based in Australia, built by Australians, and purpose-designed for the legal, regulatory, and professional certification landscape of Australia and New Zealand — with broader international expansion to follow.
Coming soon — research and case studies on engineering document tampering in Australia: what happens when certified documents are modified, who bears liability, and how to protect your professional certification from misuse.
To make document authenticity as simple as sharing a link — so professionals who stake their reputation on what they certify can be certain their work speaks for itself.
Australia