A research preview,
in plain words.

As-is, no warranty, no SLA.

honesty.tools is a research preview. It is provided as-is, with no warranty of any kind and no service-level or uptime commitment. It may change, break, rate-limit you, or go down for maintenance without notice. We work hard to keep it accurate and available — the whole project is about earned trust — but nothing on this site is a contractual promise of availability or fitness for any particular purpose.

Don’t break it, don’t fake it.

• No abuse. No scraping floods, denial-of-service traffic, or attempts to circumvent rate limits and spend controls.
• No impersonation. Don’t register a certificate that presents itself as another party’s model when it isn’t — a certificate’s model id must honestly describe what was actually calibrated.
• No key theft. Don’t attempt to extract, intercept, or misuse anyone else’s API keys through this site.

We may block, rate-limit, or remove anything that violates these — that’s the whole enforcement mechanism a research project has, and we’ll use it.

What a certificate is — and is not.

• Self-attested certificates are the registrant’s claim: the calibration ran in their browser, on their key, and Aperture did not verify the run. They are labeled self-attested everywhere they appear, for exactly this reason.
• Aperture-verified certificates were run first-party by the project, on the published battery.
• Either kind may be removed if we find it false, manipulated, or impersonating a model its registrant doesn’t represent.
• Battery-bound. Every certificate is bound to the specific battery version (and hash) it was run against. When the battery changes, older certificates remain readable but describe the older battery.
• Not a production guarantee. A certificate’s numbers describe the model’s performance on the published calibration battery at the time it was run. They are not a guarantee of behavior on your production traffic, your domain, or your prompts.

Keys are a courtesy, not a right.

• Project-issued /v1 keys may be rate-limited or revoked at any time, particularly for abuse or cost protection.
• Daily spend ceilings apply — the service fails closed rather than running up an open-ended bill.
• Bring-your-own upstream keys are never stored. If you supply your own upstream API key, it is used to make the request and not retained.

How prompt data is handled is covered in the privacy statement: processed transiently, never used for training, never sold.

Open where marked; certificates are public facts.

Use the license stated in the relevant file, repository or release. The public honesttools repository is Apache-2.0. No general license is granted here for unreleased research code, datasets, models or private packages. Registered certificates remain public according to the existing registration terms. See the privacy statement for takedown terms.

Verify before you rely.

This is a research tool. It reads signals about whether a model’s answer is grounded; it can be wrong, in both directions. Do not treat any reading, verdict, or certificate as a substitute for independent verification — especially for anything high-stakes: medical, legal, financial, safety-critical, or reputation-affecting decisions. If you build on it, build with the assumption that it can fail, because sometimes it will. To the maximum extent the law allows, the project and its operators accept no liability for losses arising from use of this site or its readings.

A research project, on the record.

honesty.tools is operated as a research project by the Aperture project, an independent AI-honesty research effort. There is currently no incorporated legal entity behind it; a formal legal entity statement will replace this page if and when the project incorporates. Until then, this plain-language statement is the honest description of how things stand. Contact, for everything: hello@honesty.tools.