> For the complete documentation index, see [llms.txt](https://docs.askdodo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.askdodo.com/guides.md).

# Guides

Practical guidance for attachments, Credits, request recovery, and privacy.

### Start with the product, not a catalog model picker

Describe your request and provide the required input. AutoRouter chooses the underlying route. Do not assume that every published text, image, or video entry is enabled in the website.

For integration work, read the appropriate live directory and confirm the supported authentication and endpoint contract first. See [Models](https://docs.askdodo.com/models) and [API Reference](https://docs.askdodo.com/api-reference).

### Read privacy claims precisely

Read privacy tier, TEE attestation, E2EE, model-set membership, and recommendation traits separately. `private` does not by itself prove E2EE; HTTPS is not the same as encryption that excludes the processing service. Neither a model name nor a prefix is sufficient evidence.

The gateway receives request content and, for paid Web Auto requests, an Account access JWT. Account cookies stay at the website's same-origin login boundary. The inference contract excludes account identity, payment information, and authentication credentials from upstream model/provider payloads. Do not generalize this into a claim that no service can associate a request with billing or operational records.

Tools such as URL fetching and web search can contact external services. Submit only content you have permission to share, and review the [Privacy Policy](https://docs.askdodo.com/legal/privacy-policy).

### Work with files

Check the supported types and limits shown by the uploader. A text/source file may be processed locally; document parsing can upload the file to the parsing service. Extracted content relevant to your submitted request can be sent to the model.

The parser's temporary-file cleanup does not prove that every service, proxy, log, backup, or third-party provider retains no content. Avoid a universal zero-retention assumption.

### Use Credits safely

Account Credits are maintained by the service. US$1 represents 100 Credits. Card checkout and supported crypto deposits use the account balance; the payment methods, assets, and networks available to you are shown in Get Credits.

For crypto deposits, follow the exact displayed asset, network, address, and amount instructions. If no supported network is available, do not send a transfer to a guessed address or another environment. A local demo or feature preview does not prove that Production payment configuration is enabled there.

Payment arrival, available balance, reserved balance, and settled charges are different states. When a request finishes, unused reservation can be released to available balance. That is not a cash refund.

See the [Refund Policy](https://docs.askdodo.com/legal/refund-policy) for billing review. Never share full card details, passwords, access tokens, or private keys with support.

### Recover before retrying

If a request is still generating, wait or use the status action the product provides. If the result or Credits status is unknown, check the original request before starting another paid generation. A transport error is not proof that execution did not occur, and a UI failure is not by itself proof of a charge or refund.

For integrations, keep the same request identity and idempotency key when recovering the same operation. Status recovery may not restore missing response text. A response-spool/replay feature, where enabled, has its own protocol and retention limits; do not assume availability from a type, flag, or client method alone.

### Protect local conversations

The website uses encrypted local conversation storage. Browser data removal can delete local chats, drafts, and recovery records, without itself deleting the server-managed account Credits balance. Local encryption and server-side account authentication protect different boundaries; neither makes an AI request entirely device-local.

Use product or browser controls carefully. Do not clear site data as a first response to a pending payment or unknown request.

### Verify node attestation

1. Generate a fresh 32-byte base64url nonce.
2. Read `https://gateway.askdodo.com/attestation?nonce={nonce}`.
3. Validate the nonce, TLS-public-key binding, and Intel TDX cryptographic evidence with the documented verifier.
4. Keep the conclusion within the node evidence boundary.

The supported conclusion is **TDX node verified**, not verified application source, workload image, runtime arguments, or exclusion of the operator. Merely receiving an attestation response is not verification.

### Availability is specific to the environment

Production, Beta, and per-feature previews can have different authentication, model, payment, and network configuration. A visible demo state is an interaction reference, not a real backend success. An available public catalog proves publication of metadata, not that every operation is usable in every environment.
