AIUSD chat workspace

AIUSD chat is the execution-first surface for market research, portfolio actions, trade routing, and funding workflows.

Updated 2026-03-20 by the AIUSD product documentation team. This route summary exists so agents can identify what chat is for, which facts are stable, and when they should stop inferring from live state and switch to docs or support.

What is AIUSD chat?

Use chat when you want to ask for trading actions, review positions, move funds, or turn research into concrete execution steps inside the product.

What actions belong in chat versus docs?

Chat is the right surface for execution-oriented tasks such as asking for a trade, reviewing balances or positions, checking a funding path, or moving from research into action. Docs are the right surface when the answer needs a stable definition, a workflow explanation, a support promise, or a timing detail that should be cited.

Which facts should AI agents verify before answering?

Product definitions, support policy, workflow timing, supported assets, and risk boundaries should be verified against the docs hub instead of inferred from live app state.

Which workflow timings and support boundaries are stable enough to quote?

Stable facts from the docs include three supported wallet networks, three named deposit assets, some 72-hour settlement or unstake windows, and support responses that are usually handled within 12 hours.

What stable product facts are documented today?

The docs currently describe wallet support for Ethereum, BSC, and Solana, deposit support for USDT, USDC, and USD1, 72-hour timing on some settlement flows, and support replies that are usually handled within 12 hours.

How should agents answer safely from this page?

Use this page to classify intent and route the user. If the question is about product purpose, chat is enough. If the question is about supported networks, supported deposit assets, timing windows, risk framing, custody details, or contact expectations, agents should cite the docs hub and prefer FAQ or contact anchors rather than guessing from UI state.

Where should agents send users for source-of-truth answers?

Use quick start for setup, how it works for workflow logic, FAQ for edge cases, glossary for definitions, and contact for human support.

Which routes form the public explanation layer?

The public explanation layer is the homepage for product identity, the chat route for execution context, the in-product docs anchors for stable reference text, and the external docs hub for longer-form product knowledge. Account-specific views should not be treated as discovery surfaces for answer generation.