Operations
A request reaches the service desk. Check that the customer ID is present before routing it to the next team.
For business
Add a check before your workflow acts.
Connect a check to the handoff your team already runs. Operations can catch incomplete requests, procurement can compare supplier terms, and an AI agent can check a file before sending it.
Where it fits in your business
Procurement
A purchase request quotes a supplier price. Compare it with the terms your buyer supplies and route differences for review. A condition absent from those inputs is outside the price check.
Agent development
An agent prepares a client attachment. Compare its fingerprint with the approved file before your system sends it.
How it works
- Choose the claim. What must be true before your team or agent takes the next step?
- Supply the reference. Send the record and the rule or value it should match.
- Decide how to handle the result. Your system can proceed, request a correction or ask someone to review.
what's live
Available today
Rule-based checks
Eight check types on /v1/verify-facts, free in public beta, no model. Checks over supplied inputs give the same result for the same inputs; registry lookups depend on the registry at the time. Check types
Signed receipts
Keep a record of what was checked and the result. A result is returned as a signed receipt when signing succeeds.
Anchoring
For receipts with a verified inclusion proof, anchoring on GOAT Network shows the canonical payload existed by the anchoring block’s timestamp—not when it was signed or whether its claim is true. Batches currently run once a day; no anchoring interval is guaranteed, and not every receipt has a proof.
Model-based assessment of factual claims (/evaluate) is experimental: it can be wrong and isn’t suitable for authorizing actions automatically.
pricing
Connect one workflow.
Agree one check, its acceptance tests and a written handover. We confirm the scope and price before work begins.
See pricing →why we are different
Public rules. Checkable signatures.
IETF Internet-Draft — Filed
draft-krausz-verification-state-03
Revision -03 dated 1 October 2026 · individual submission on the IETF datatracker.
View on datatracker →
Public Receipt Spec v0.3
tanilo-receipt-spec
Public receipt format, verification rules and test vectors.
View on GitHub →
Reference Verifier
tanilo-receipt-verify
Python verifier on PyPI, with Node and browser siblings · offline verification against the published keys · MIT licensed.
View on PyPI →
Records your team can inspect
Keep the receipt, the matching public key and a compatible verifier to check its signature offline. This establishes record integrity, not the truth of the claim or regulatory compliance.
What do you need checked?
Tell us what your AI system claims or produces, and what you want to check. Please don’t include confidential documents, passwords or sensitive personal information.
Contact Tanilo →Or email joe@tanilo.io.