Start here

↑ ↓ to choose · Enter to open · Esc to close

Trust center

Inspect a receipt, check the router’s keys or follow a request from your device to the model.

Verify a receipt

Reading a receipt

The signature identifies the key that signed the record. If the receipt includes a Merkle proof, this check also compares the receipt with its batch root. Confirming publication on Solana requires a separate chain check.

Router records

Unavailable
↗
Unavailable
↗
Unavailable
↗

Request path

Compare who can read and retain your message on each route. Private requires a model with verified attested supply.

  1. 01
    You
    SeesYour message and the answer.
    KeepsNothing, unless you keep it.
  2. 02
    Trellis router
    SeesYour message, in memory, to route it.
    KeepsNo prompt or answer text. A receipt: model, provider, tokens, cost and hashes.
  3. 03
    Provider
    SeesYour message, to run the model.
    KeepsWhat its data policy says. A promise, not a proof.
  4. 04
    Receipt
    SeesNo text: hashes, model, provider, tokens and price.
    KeepsSigned with the router’s published key; public by its ID.
  5. 05
    Solana
    SeesOne 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.

Receipt and hardware labels

Verified

The receipt’s signature checks against the router’s published key.

Anchored

The receipt is in an hourly batch whose root is on Solana, and its inclusion proof checks.

Attested hardware

The provider’s enclave attestation was fresh and verified when it answered.

Pending

Signed, and waiting for its hour to close and be anchored.

Reference