Turn a market idea into a rule. See what actually happened.

Junto puts market research, trading connections and rule-driven agents in one workspace. You can browse the public market interface without connecting a wallet. A wallet and a valid session are required before using private account, trading or agent actions.

A chart, a quote and an order are different things. The interface labels where data comes from and does not replace missing venue data with invented candles, fills or P&L.

Prediction markets, News, Plaza and Rotation are not available in the current release. Their absence does not affect the markets above.

The US-stock trading view uses Hyperliquid xyz perpetual market data where available. It is not a feed of NYSE or Nasdaq share trades. Yahoo cash-stock daily history is not part of this release; do not interpret an xyz candle as a stock-market spot candle.

Crypto and pool charts depend on their connected upstream sources. Some new or thinly traded tokens have too little verifiable history for a candle chart. In that case Junto shows an unavailable state rather than drawing synthetic history. A quote can be available even when candles are not.

A quote may be delayed or unavailable. Check its venue, network and timestamp before making a decision. When an upstream request fails, the interface should say so; it must not silently substitute a demonstration price.

Write a Markdown specification with a fenced agent-policy YAML block. Compile and check it, review the parsed market, symbol, signal conditions, order size, schedule and risk limits, then save it. Prose outside that block is kept for context or audit; it is not executed as code or silently converted into an order.

Agents are stored by the backend and scoped to the connected wallet. A wallet can have at most five running agents. The agent screen shows activity, source data used for a run, logs, orders and paper fills when those records actually exist.

An agent runs on a server-side schedule, not because a browser tab remains open. If required market data is missing or a check fails, it must not invent a signal or fill. Pause and inspect the recorded reason before changing a policy.

Connecting a wallet does not by itself authorize an agent to trade. Main wallet approval, restricted Agent Wallet authorization, the selected network and order checks are separate steps. Never share a seed phrase or private key with the site.

Order size, maximum position, stop loss, take profit, open-order limit and slippage limit are fields in the executable policy. Junto checks them before execution; a displayed suggestion is not a guarantee of execution or a substitute for venue-side controls. Review the actual limits in each compiled policy instead of assuming one universal percentage.

Wallet-scoped sessions protect private agent, connection, order and fill endpoints. Account balances, positions and open orders come from backend and venue reads rather than browser-created local fills. A missing value is shown as unavailable, not as zero unless the source really reports zero.

1. Open US stocks or crypto. Select a symbol and inspect its source, network, price and available chart history.
2. If you want an agent, connect a supported wallet and complete sign-in. Open Agents and write or edit a Markdown policy.
3. Compile and check the policy. Review its symbol, schedule, signal and risk fields before saving.
4. Start with paper mode to inspect decisions and fills. Testnet and Mainnet are separate choices requiring the appropriate Agent Wallet authorization.
5. Use the agent activity, run log, orders and fills to confirm what actually happened. Pause the agent if the observed behavior differs from the policy.