Connect your wallet
Use WalletConnect or an injected browser wallet, then switch to Robinhood Chain.
HOODFLOW DOCUMENTATION
Understand every step
before you sign.
Connect a self-custody wallet, inspect a protected quote and trade execution-enabled Stock Tokens on Robinhood Chain. Start with Direct Buy or Sell; automation remains a separate beta feature.
01 / START HERE
What you need
HoodFlow is a wallet-first interface. There is no HoodFlow account and HoodFlow never asks for a seed phrase or private key.
NETWORKRobinhood ChainChain ID 4663
PAY WITHUSDGUsed for supported buy routes
NETWORK GASETHKeep a small balance for fees
Never share recovery words.
Wallet connection only exposes your public address. Every permission and transaction must still be confirmed inside your wallet.
02 / DIRECT BUY
Buy a Stock Token with USDG
Choose an execution-enabled market
A green full-fill status means HoodFlow has a reviewed route for the complete input amount. Watch-only assets cannot be submitted.
Enter the USDG amount
HoodFlow checks your balance and requests a fresh route quote for that exact input.
Review the protection
Confirm the route, estimated output, minimum received, slippage setting and quote age before signing.
Approve and execute
The wallet signs a short-lived Permit2 permission, then the router transaction. The received token settles directly to your wallet.
03 / SELL
Sell a Stock Token back to USDG
Open an execution-enabled market, choose Sell to USDG, enter the token amount and request a fresh quote. The same output floor and expiry rules apply. Selling is unavailable when the route, oracle or token state fails a safety check.
IMPORTANT
The displayed oracle value is not a guaranteed exit price. The wallet confirmation uses the executable DEX quote and its protected minimum.
04 / PRICING
Reference price versus execution quote
Market context
Chainlink rounds provide the onchain reference shown on market pages. References may remain unchanged while the underlying market is closed.
What the router can fill
HoodFlow requests a fresh Uniswap V3 or V4 quote for your exact amount. This quote, not the chart price, determines estimated and minimum output.
05 / PERMISSIONS
What your wallet signs
HoodFlow uses Permit2 for an exact token amount with a short expiry. Always verify the token, spender, amount and deadline in the wallet. The interface does not need custody of your assets or access to your recovery phrase.
06 / STATUS GLOSSARY
Why a trade may be disabled
A reviewed route is configured and a fresh executable quote can be requested.
The canonical token is indexed, but no route has passed HoodFlow's complete-input checks.
The reference feed is paused, stale or invalid. Trading remains blocked until verification recovers.
The requested amount cannot currently receive a valid complete fill within the configured route policy.
07 / DEPTHMAP
Stress-test the route before opening an order
DepthMap requests five separate, wallet-free Buy preflights for the selected reviewed market: 10, 25, 100, 250 and 1,000 USDG. Each sample uses the same 0.50% slippage setting, current oracle corridor and live DEX route checks as HoodFlow's agent preflight.
The exact input returned a locally verified, unexpired indicative preflight. It is a point-in-time signal, not a guaranteed fill.
No guarded result was promoted for that input. HoodFlow does not interpolate between missing points or guess the cause.
Every DepthMap result expires quickly. An expired point loses its pass state and cannot open a prepared order.
The highest sampled pass is not a maximum trade size, liquidity promise or recommendation. Larger untested values remain unknown.
Five fixed points, two at a time
The scanner runs only after a user click, checks at most two samples concurrently and applies a cooldown between scans. It never fans out across every market in the background.
Carry the amount, then verify again
Opening an order carries only the selected asset and amount. The trade screen requests a new executable quote and runs ActionLock before any wallet signature.
READ IT CORRECTLY
Route-reviewed means HoodFlow has a configured, tested route. It does not mean every amount is executable at every moment. DepthMap keeps unavailable samples visible instead of turning old or partial data into a green signal.
07B / DEPTH MEMORY
Compare only what HoodFlow actually observed
After a complete DepthMap scan, HoodFlow saves a sanitized historical observation in this browser. Repeating the same fixed ladder later unlocks an exact-input comparison: which sampled passes appeared or were not reobserved, how the observed DEX-to-oracle distance changed and whether the reviewed venue changed.
Up to five observations per market and twenty total are kept in browser storage. Wallet addresses, transaction hashes, calldata, approvals and signatures are never included.
A historical pass describes an expired point-in-time observation. It is never restored into the live scanner and can never enable an order.
A missing historical result stays unresolved. HoodFlow does not relabel it as failed liquidity or infer a cause that the response did not prove.
Opening Depth Memory makes no network request. Only an explicit fresh scan calls the same bounded five-point preflight flow.
Same market, same input
Output and oracle-distance changes are calculated only when both selected observations passed at the identical USDG sample. Values between ladder points are never interpolated.
History cannot become authority
The “Run fresh comparison” action always creates five new preflights under the existing two-worker limit and cooldown. Opening an order still requires an unexpired current point, a fresh execution quote and ActionLock.
PRIVACY + CONTROL
Depth Memory works without a wallet and can be exported or cleared per market. If local storage is blocked, live DepthMap remains available and no historical notebook is created.
08 / ACTIONLOCK
Inspect event risk before you trust a route
ActionLock is a read-only preflight for route-reviewed Stock Tokens. Send the same asset, side, amount and slippage fields accepted by POST /api/agents/quote to POST /api/action-lock. It does not connect to a wallet, request approval, sign a message or submit a transaction.
Confirms that the requested ticker resolves to HoodFlow's reviewed token address instead of trusting a symbol or display name alone.
Surfaces known split, merger, conversion or distribution risk. Missing official event data stays explicit rather than being treated as a clean result.
Checks the configured economic multiplier and flags a mismatch that could make the displayed unit value misleading after an event.
Combines available market-halt context with onchain token and oracle pause signals. Unknown or stale state is never silently presented as open.
Keep the inspection record
The response can be downloaded as an ActionLock passport containing the request, observed checks, timestamps and a SHA-256 content checksum. The checksum supports byte-for-byte comparison; it is not a HoodFlow signature or proof of authenticity.
Inspection is not execution
A passport is not proof that a swap executed, settled or remained safe after it was generated. HoodFlow must still request a fresh quote and the user must confirm every wallet action.
OFFICIAL-DATA LIMIT
Corporate-action and exchange-halt information can be incomplete, delayed or unavailable from public sources. ActionLock reports those gaps as unknown; it does not certify issuer disclosures or replace official exchange and issuer notices.
08B / FLOWRIGHTS
Classify the event before previewing the increment
Payday Radar is a public, read-only corporate-action inspector for HoodFlow-indexed Stock Tokens. Call GET /api/payday?asset=AAPL with exactly one ticker. A successful HTTP response wraps the result as { ok: true, data }; eligibility still depends on every evidence gate below.
Only CORPORATE_ACTION_TYPE_CASH_DIVIDEND can qualify. Splits, conversions, name changes, unknown types and ambiguous active events are never relabeled as yield.
The official asset, corporate action and HoodFlow registry must bind the same stable UID and the exact canonical Robinhood Chain deployment address.
The official processDate is date-only scheduling evidence. Separately, the canonical token's uid(), uiMultiplier(), newUIMultiplier() and effectiveAt() must match official state before any arithmetic preview appears.
Missing sources, a completed event without a trustworthy pre-event baseline, mismatched state or an incomplete transition returns pending, blocked or unavailable—not an inferred amount.
One-token illustration, not a balance
When every gate passes with code CONCURRENT_MULTIPLIER_TRANSITION_READY, Payday shows the raw amount that preserves the pre-event economic exposure after a positive multiplier change. The cash-dividend record and transition are concurrent evidence only. The endpoint reads no wallet balance and provides no USDG execution quote.
No permission and no entitlement
The endpoint cannot connect a wallet, request an approval, sign, submit, create a claim token, control funds, create an entitlement or return an execution handoff. Compound, Cash to USDG and Redirect remain instructions for a future audited release.
STOCK TOKENS ARE NOT SHARES
Open Payday Radar →The preview describes token arithmetic and source evidence only. It is not a shareholder right, dividend claim, investment recommendation, transaction instruction or execution promise.
08C / BELLLOCK
Watch the opening bell without giving an agent your wallet
BellLock is a user-armed reopening policy for Stock Tokens. It records the exact USDG intent and hard limits for opening gap, spread, oracle-to-DEX deviation and stress-size route drift. The watcher can inspect evidence; it cannot approve a token, sign a message or submit a transaction.
The policy is saved in this browser and waits for its target regular session. Keeping the page open is required in the current preview; there is no hidden background trader.
A reopening needs two fresh, distinct and sufficiently spaced observations. One print is never promoted into a signature window.
Unknown session evidence, a halt, corporate-action conflict, stale report or breached limit fails closed. BellLock records the reason and exposes no execution handoff.
A future production handoff requires verifier-bound session reports, previous-close evidence and fresh exact plus stress quotes. The wallet still makes the final decision.
Closed to open, then converge
The strict evaluator binds a closed-to-regular-session transition, two unique report digests, compatible feed units, a verified previous close and every evidence expiry into one short signature window.
No signed stream, no green light
The current public preview can show official unsigned Robinhood observations and onchain reads, but it cannot call them a cryptographic session proof. Until verified Data Streams collection is configured, it returns an armed, warming, refused or unavailable receipt and never enables a trade.
CHECKSUM ≠ SIGNATURE
Open BellLock →A BellLock receipt includes a deterministic SHA-256 integrity digest so the JSON can be compared byte for byte. That digest does not authenticate HoodFlow or the upstream publisher. Only a verifier receipt bound to the raw report can satisfy the strict proof tier.
09 / FILLPROOF
Reconstruct what actually settled
Every new reviewed Stock Token Buy or Sell can open a FillProof. HoodFlow reads the confirmed transaction, decodes the supported Universal Router command, verifies the sender and canonical token addresses, totals matching settlement transfers, and compares the actual raw output with the protected minimum encoded in calldata.
Public facts, checked together
The transaction hash, block, sender, router, route, raw input, minimum output, actual token transfer and native gas cost come from Robinhood Chain. A public receipt link works without connecting a wallet.
Expected versus actual
New trades also keep the quoted output and ActionLock reference in wallet-scoped browser storage. Those local fields enable an expected-versus-actual comparison, but they are not presented as onchain facts or a HoodFlow signature.
Public verification endpoint
GET /api/fill-proof?txHash=0x... returns the wallet-free onchain reconstruction used by the receipt view. It accepts only confirmed, reviewed HoodFlow router settlements on chain 4663.
CHECKSUM LIMIT
The downloaded JSON includes a SHA-256 checksum over the reconstructed onchain fields. It detects document changes; it is not an audit, a platform signature or proof that HoodFlow originated the transaction.
10 / AGENT API
Connect once, keep execution human-controlled
HoodFlow exposes the same bounded capabilities through REST, OpenAPI 3.1.2 and a stateless Streamable HTTP MCP endpoint. A successful preflight verifies the configured DEX route, current Chainlink reference, oracle-pause state and maximum DEX-to-oracle deviation. It remains indicative: HoodFlow requotes before every wallet signature.
Drop HoodFlow into an agent
POST /api/mcp exposes market discovery, quote preflight and basket planning as tools. GET /openapi.json publishes the equivalent REST contract. Neither connector receives a signer, private key or transaction permission.
One budget, explicit legs
POST /api/agents/basket allocates one USDG budget across two to six unique markets and checks every leg. A basket is non-atomic: each accepted leg gets a fresh quote and a separate trade confirmation; token approval and Permit2 signing can add wallet prompts.
Discover reviewed routes
GET /api/agents/markets returns the currently exposed route-reviewed Stock Token markets, addresses, settlement asset and execution policy.
Carry intent, then requote
POST /api/agents/quote accepts the asset, side, exact amount and slippage. The handoff preserves those inputs, then requests a fresh execution-bound quote for final wallet confirmation.
BASKET FAILURE POLICY
all-or-nothing returns no plan if any leg cannot pass. Explicit omit-unsafe can keep the safe legs without redistributing rejected budget; the user must acknowledge the partial plan before opening an order.
EconomyOS resource status
Open the live JSON manifest →HoodFlow is registered on EconomyOS with two public, read-only ACP resources: the Agent Manifest and Reviewed Markets. Quote, ActionLock and basket preflights remain direct HoodFlow API actions; no EconomyOS signer or transaction permission is configured.
11 / MEME + CRYPTO
Discover tokens by contract address
The Token Terminal combines Virtuals' official Robinhood Chain launch feed, top-volume, trending and newest DEX pools, and HoodFlow's canonical RWA registry. Rank the indexed markets by volume, 24-hour change, liquidity or age. Provider-derived categories remain discovery metadata; interactive category filters are not live yet.
Paste any standard ERC-20 contract address on Robinhood Chain. HoodFlow reads bytecode and metadata, detects the token's lifecycle and quote asset, then probes Uniswap V2, V3 and hookless V4 liquidity only when a DEX route should exist. You can pay or receive USDG, VIRTUAL or WETH; when a direct pair is unavailable, an eligible V2 order can route through the market's native quote token in the same transaction.
Trade at the source
The token has not graduated. HoodFlow shows official Virtuals metadata and links to its source market instead of treating an empty pre-created DEX pair as executable.
Verify live liquidity
HoodFlow probes the active token and quote asset onchain. Embedded execution appears only after a fresh route returns non-zero output.
UNREVIEWED MODE
Contract discovery is not an endorsement or safety review. Trading is enabled only when a fresh executable route exists, but route availability does not rule out malicious transfer logic, issuer risk or liquidity withdrawal.
12 / REWARDS
How HF Points qualify
A wallet creates a shareable referral link with one message signature. The invited wallet receives 100 HF Points and its referrer receives 500 only after the invited wallet's first eligible Universal Router trade is confirmed on Robinhood Chain. Clicks, repeat trades and raw volume earn no points. Verified points are recorded now; the public Season 0 leaderboard remains Coming Soon until rankings open.
No guaranteed token allocation.
HF Points are planned to inform future $HFLOW eligibility, but have no present monetary value. Conversion rate, launch, eligibility, jurisdiction and anti-sybil terms remain subject to a future announcement.
13 / AUTOMATION BETA
DCA is separate from Direct Buy
The recurring engine is an advanced beta feature. Only prepare a schedule when the application reports that the deployed engine and keeper are live. A DCA defines its asset, amount, cadence, total budget, expiry and slippage boundary; keepers cannot execute outside those limits.
View recurring engine contract →14 / TROUBLESHOOTING
Common messages
Wallet is on the wrong network
Approve the network switch to Robinhood Chain. If your wallet does not add it automatically, use chain ID 4663 and the official network configuration.
Waiting for oracle
The reference feed is unavailable, stale or still being verified. Trading stays disabled rather than using an unverified value.
No live full-fill route
Liquidity for the selected asset or amount cannot pass the current route policy. Reduce the amount or try again later; never bypass the warning with a blind transaction.
Why does a Virtuals token open an external market?
The token is still on the Virtuals bonding curve. The official public SDK does not currently publish Robinhood Chain write constants, so HoodFlow fails closed instead of asking your wallet to trust an inferred upgradeable router.
Transaction reverted
The executable output may have moved below your protected minimum, the permission may have expired or the wallet balance may be insufficient. Request a new quote before retrying.
Chart history is unavailable
The historical oracle endpoint may not have enough valid rounds. This does not create an execution price; a fresh DEX quote is still required.
READY TO START?
Begin with a quote.
Signing comes later.
They may be restricted in your jurisdiction and do not provide shareholder rights.