Don’t take our word for it.
Every answer is signed. Every hour of receipts is anchored on Solana. The keys are public. Here is what you need to check Trellis yourself, and an honest list of what it can’t prove.
Live, read from this router now
Follow one request
Who sees your message, and what is kept, at each step. Switch to Private to see what changes.
- 01YouSeesYour message and the answer.KeepsNothing, unless you keep it.
- 02Trellis routerSeesYour message, in memory, to route it.KeepsNo prompt or answer text. A receipt: model, provider, tokens, cost and hashes.
- 03ProviderSeesYour message, to run the model.KeepsWhat its data policy says. A promise, not a proof.
- 04ReceiptSeesNo text: hashes, model, provider, tokens and price.KeepsSigned with the router’s published key; public by its ID.
- 05SolanaSeesOne root per hour: a hash over that hour’s receipts.KeepsPermanently. Anyone can check a receipt against it.
In Standard mode any live provider for the model can answer, and its data policy is shown on the model page.
Check it yourself
Checked in your browser against the published keys. A file you drop here is read on this device and not uploaded.
What you will see
- Whether the signature matches a key the router publishes.
- Whether the receipt is in an anchored hour, and its inclusion proof.
- The model, provider, tokens and price it records.
- What it cannot show, listed plainly.
One set of marks, everywhere
The same marks appear on models, in Chat and on receipts, and each means exactly one thing.
The receipt’s signature checks against the router’s published key.
The receipt is in an hourly batch whose root is on Solana, and its inclusion proof checks.
The provider’s enclave attestation was fresh and verified when it answered.
Signed, and waiting for its hour to close and be anchored.
What a receipt proves
- Which model and provider answered, the tokens and the exact price.
- That the router signed it with the key it publishes, and nobody has changed it since.
- Once anchored, that the hour’s receipts can’t be quietly rewritten.
- With the Attested hardware mark, that the provider’s enclave attestation was fresh when it answered.
What it can’t prove
- That the answer is correct.
- That a provider without the Attested hardware mark didn’t keep your prompt. Its data policy is a promise, not a proof.
- That the router has no bugs. The code is open, and it has not had an independent audit yet.