Verify, don’t trust.
Sable sells compute you can prove. So every claim on this page is checkable live, by you, right now. The numbers below are read straight from the running gateway, not a status graphic.
Recorded gateway health, sampled continuously and served at GET /v1/status. Uptime is computed from persisted probes; it is null until enough samples exist, never fabricated. Refreshes every 30 seconds.
The confidential tier is TEE-attested for the sable-confidential-* models. Other tiers are not confidential. Below is the live, DCAP-verified quote the gateway checks before serving any confidential request.
Zero third-party machines serve Sable traffic today: one gateway, honestly labeled. What runs is this gateway process and its configured confidential backends. There is no operator network to overstate.
Every billable response is signed by the key below (secp256k1 / EIP-191). Pin this address and verify any receipt offline against it, or paste one here to check it now. See the receipts docs.
Paste the x-sable-receipt header (or the sable.receipt stream event) and its signature. The check runs against the public POST /v1/receipts/verify endpoint and recovers the signer.
What we do not claim.
Trust is what’s left after the overclaims are removed. These are the limits of what Sable proves, stated plainly, because the honesty is the point.
On these tiers the model host’s servers see the prompt in plaintext. Anonymized routing hides who is asking from the vendor; it does not hide what is asked. Only the confidential tier is TEE-attested.
A counter-signed receipt proves which machine served a request (who to hold responsible), not that the work it returned was correct. We label attribution as attribution.
The double-blind path (planned, and labeled planned everywhere) separates identity from request. It is a privacy property, not a confidentiality guarantee over the payload.
Zero third-party machines serve Sable traffic today. What runs is this gateway and its configured backends. We do not use present-tense network or marketplace language for supply that doesn’t exist yet.
Sable Vault records and proves issuer-declared entries with hash-chained events and public anchoring. Sable does not custody assets, appraise them, or enforce ownership.
Prompts, completions, and submitted code are never persisted or logged. A receipt carries metadata and a content fingerprint: enough to verify what ran, never enough to reconstruct it.