Clear answers. No guesswork.

No. Public market pages can be viewed without a wallet. Private account, trading and agent actions require a connected wallet and valid session.

No. The current trading instruments are Hyperliquid xyz stock-themed perpetual contracts, not NYSE or Nasdaq shares. Check the venue label before placing an order.

Not in the current release. Prediction markets are marked coming soon; this documentation does not treat them as an available trading route.

No. The current stock-trading chart uses available Hyperliquid xyz venue candles; it should not be presented as Yahoo cash-equity history.

The upstream venue or pool may not provide enough verifiable data, especially for new tokens. Junto shows an unavailable state instead of generating synthetic prices or fills. A quote may exist even if historical candles do not.

No. Only the validated YAML inside the fenced agent-policy block is executable. Other Markdown is retained for context or audit. Compile and inspect the parsed policy before saving.

A running agent is scheduled by the backend rather than by an open browser tab. Its decisions and errors are recorded for inspection when you return.

At most five running agents per wallet. Pause one before starting another if you reach the limit.

There are separate paper, Hyperliquid Testnet and Mainnet paths. Mainnet can use real funds and requires Mainnet Agent Wallet authorization plus an explicit confirmation. Simply connecting a wallet is not permission to trade.

Inspect the agent run log, order state and Fills page. Paper fills are backend records; live order and account state come from the backend and venue. No fill should be invented when a source is unavailable.

Review the executable risk fields in each compiled policy: order size, maximum position, stop loss, take profit, open orders and slippage. Venue and authorization checks still apply. Do not assume one universal percentage for every agent.