Verification capacity, without hiring for it
If you already have the clients and a recurring verification obligation, we can be the engine underneath. Three ways to work together. And no price list, because every partnership differs in scope, branding, volume and hosting.
Run the falsifier as your own verification backend. Your brand, your client relationship, our engine behind it: API and SDK access, your portal.
Joint verification engagements where the receipt carries both names. Useful when the client needs to see an independent third party in the chain.
We absorb peak verification load under your engagement model, to your specification and your reporting format.
What sets the terms
We do not publish a rate card, for the same reason the accredited auditors and insurers do not: a single number would misrepresent every deal except one. These are the five things that shape a partnership.
What you would be reselling
10 signed catches across 6 public repositories: a frontier model claiming success while wrong, on real code. Every receipt is Ed25519-signed, content-addressed, and re-verifiable in a browser with only the public key.
The part your clients cannot get elsewhere: we publish what we rejected. The methodology page carries every candidate we threw away and why. A vendor inflating a record does not show you that.
