Not probably.Provably.
Right before a critical operation, such as approving a payment or changing someone's access, the user signs once with their passkey. What remains is a record of who agreed to what, and when, that can be checked later.
Sample · Northwind Expenses · Approve transfer · To Harbor Supply Co. · USD 3,200.00 · Oct 12
This is a sample. No passkey is used, but the hash is computed for real.
A login record
can't show consent.
Most business systems let critical operations through on the assumption that whoever is signed in must be the right person. All that's left is which session sent the request. Who agreed to what is recorded nowhere.
Session record
This record can't tell you who pressed the button, or what they saw when they did.
Signature record
What gets signed is a hash of the operation. Change a single character and the signature no longer verifies.
One signature,
right before the operation.
Request
Your service asks for a signature and sends the hash of the operation.
Confirm
The user sees which service is asking, what the operation is, and what signing will do.
Sign
Whoever made the request, only the user's passkey can sign.
Return
The signature file goes back to your service and into the user's own signature history.
The same operation carries the same seal everywhere: in your service, on the confirmation screen, in the user's history, and on the verification page.
Go ahead,
change it.
Change one character after signing and both the hash and the seal become something else. This doesn't stop tampering. It makes tampering visible.
The sample hash is the SHA-256 of the JSON below, encoded as UTF-8. In the product, whether a signature is valid is decided by verifying it. The seal only helps people notice a difference.
Anyone can ask.
Only a person signs.
Let an AI agent prepare the operation and request the signature. Only the user's passkey can sign, so anything that needs a signature waits until a person signs it.
“I didn't do that”
can be shown, too.
Every signature also lands in the user's own signature history. For an operation that requires a signature, the absence of one supports the claim that they never agreed.
Clavis keeps the signature record.
Nothing more.
Clavis receives the hash of the operation and the one line shown to the user. The operation itself and your business data never leave your service.
Clavis
- Identifiers
- Passkey public keys
- Signature records: who, which hash, when
Your service
- Business data
- The operation the hash is computed from
- Screens, notifications, and what happens after signing
One dollar a signature.
Signature — USD 1 / per completion
- The first 30 each month are not billed.
- You set the billing cap. It starts at USD 0, so signing stops at the 31st until you raise it.
- For steady use, a USD 100 monthly plan includes 200.
Ledger — USD 50 / per month
- Includes 2,000 appends. USD 0.05 each after that.
- Show that a record was final at a point in time, without handing over the business data.
Enterprise
- DeepDive takes on rollout, app development, OEM, and operations.
Prices in US dollars. Polar is the merchant of record. Pricing details
Start with one operation.
Create an Org, declare what you'll use it for, and verify the host it returns to. The first 30 signatures each month are not billed.
Want us to handle the rollout? Enterprise