> 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/readme.md).

# askDodo Docs

Using askDodo, Account Credits, AutoRouter, and the current privacy boundaries.

askDodo brings text, image, and video generation into one workspace. Describe what you want to make; AutoRouter chooses the underlying route. The website does not offer a manual model picker.

[Open askDodo](https://askdodo.com/agent/) or start with [Getting Started](https://docs.askdodo.com/getting-started).

### What you can do

* Chat and work with supported attachments.
* Generate images and videos through the product's Auto flow.
* Buy Account Credits with the payment methods shown in Get Credits. Card checkout and supported crypto deposits share the account balance.
* Keep encrypted conversation history in your browser. Local history is separate from your server-managed Credits balance.

Availability depends on your account, the request, the enabled routes, and current service conditions. A listed model or payment integration does not mean every offer, network, or operation is available to every user.

### Credits

1 Credit represents US$0.01 of service value: US$1 = 100 Credits. Your current Credits balance is maintained by the service, not by device-held spending proofs. Clearing browser data can remove local conversations and preferences; it does not itself erase the server-managed account balance.

Requests can reserve Credits before settlement. A released reservation returns available account balance; it is not a refund to your card, bank account, or crypto wallet. See [Guides](https://docs.askdodo.com/guides) and the [Refund Policy](https://docs.askdodo.com/legal/refund-policy).

### Privacy boundaries

Your request content reaches the gateway and the model or tool services needed to complete it. The website's Account cookies stay at its same-origin login boundary. Paid Auto requests use an Account access JWT at gateway ingress for authentication and billing; that JWT is not a model prompt.

The inference contract separates account identity, payment information, and authentication credentials from upstream model/provider payloads. This does not mean the gateway never receives an Account token, nor that all operational or billing records are unlinked.

Privacy tier, TEE attestation, and end-to-end encryption are different properties. A `private` label or HTTPS connection alone is not proof of E2EE. Read the live route metadata and the [Privacy Policy](https://docs.askdodo.com/legal/privacy-policy) before relying on a privacy claim.

### Public catalogs and technical reference

The gateway publishes separate directories for different request schemas:

* [Text catalog](https://gateway.askdodo.com/v2/models)
* [Image catalog](https://gateway.askdodo.com/v1/images/models)
* [Video catalog](https://gateway.askdodo.com/v1/videos/models?shape=grouped-v1)
* [Built-in tools](https://gateway.askdodo.com/v1/tools)

These are published catalog records, not a list of every model currently reachable through the website's AutoRouter. See [Models](https://docs.askdodo.com/models) for the distinction and [API Reference](https://docs.askdodo.com/api-reference) for the current metadata format and authentication boundary.

Node attestation provides a separate, bounded check of Intel TDX node evidence. It is not proof of the workload image, source code, runtime arguments, or operator exclusion.

### Documentation scope

This documentation describes the current website and verified public metadata interfaces. It does not promise general availability of every internal endpoint, SDK, CLI, response-replay feature, or roadmap item. Beta and feature previews validate specific revisions; they do not establish Production availability.

Questions: <hi@askdodo.com>.
