USDF and trust
What the gateway keeps.
A plain-language account of the information required to serve, meter, settle, and verify requests.
On this page
Account and key records
Account identifiers, linked wallet details, key labels, limits, and the hash used to validate each API key.
Usage records
Model, upstream provider, endpoint, token counts, cost, status, timestamps, and settlement references.
Public proofs
Settlement digests, transaction references, price sheets, and inclusion proofs needed to verify charges.
Prompts and completions
Requests are forwarded to the upstream provider that serves the model. What each route does with request content is published per route, as data_policy in GET /v1/pricing. A route with no verified policy is never used for a request that asks for zero retention or no training.
Each request can ask for its own privacy: see Data handling for what is kept and for how long, and Provider preferences for the asks.
Full API keys are shown once and stored only as hashes. Wallet ownership is proved by signature; private wallet keys never leave the wallet.
Attested hardware
Private-tier requests run only inside attested hardware. A request without a matching route is refused before any charge. Archived reports appear here by date and key rotation.
- Attestation
- Checking