The 24/7 assumption
Most crypto perpetual markets trade around the clock, and an agent built on that assumption has no concept of a market being “closed.” Its loop is simple: read the signal, size the position, send the order, repeat. Nothing in that loop asks whether the market is open to accept the order.
Now picture the same agent pointed at a stock perp on a Friday evening. A general-purpose assistant has summarized the day’s earnings coverage, and the agent decides to open a leveraged position. This is a hypothetical, and nothing in it predicts a price. The question is only whether the venue will take the order at that hour, and what happens to a high-leverage position when the underlying stock market closes.
This post is part of a series on agentic trading on perps. It reads LeverUp’s Trading RWA documentation, which I re-opened at write time, and turns its session rules into things a trading agent has to encode. I did not find a documented LeverUp connector for any consumer assistant, and none is implied here. LeverUp’s gasless / 1CT documentation describes a hosted-agent mode for backend-held signing keys. Our tutorial, How to Build a Grok Bot Trading Agent on LeverUp, walks through one setup — it is not a claim that consumer assistants ship a LeverUp connector.
What the docs say about session hours
The Trading RWA page says LeverUp supports perpetual trading on real-world assets, starting with MAG7 equities. For those markets, the page lists:
- Trading hours: Monday to Friday, 9:31 AM to 3:59 PM Eastern Time. A buffer is introduced so that submitted trades can go through (Trading RWA docs).
- Weekends: closed (Trading RWA docs).
- Holidays: the page points to the NYSE market hours and holidays schedule rather than listing dates (Trading RWA docs).
- Opening: new positions can only be opened during market hours (Trading RWA docs).
- Maximum leverage: 100x for RWA pairs (Trading RWA docs).
- Existing positions held off hours: they remain active and are subject to funding rates, which the page describes as reflecting the cost of holding (Trading RWA docs).
Two cautions. The page names MAG7 equities as the starting set, so an agent should not assume the same schedule for any other RWA pair without reading that pair’s rules. And the docs do not describe how irregular sessions such as early closes are handled; the Trading RWA docs refer to the NYSE schedule for holidays. Whether an early close shortens the window here is not stated, so an agent should treat that as an open question to check, not a given.
Leverage tiers and the force-close rule
The same documentation splits RWA positions by leverage:
| Position type | Leverage | Holding rule (per docs) |
|---|---|---|
| Day Trade | above 10x, up to 100x (Trading RWA) | Closed before market close; force-closed at market close if still open |
| Overnight Position | 10x or below (Trading RWA) | Can be held across off hours and weekends; subject to funding rates |
The force-close section adds detail. At market close, the page says LeverUp automatically force-closes every RWA position with leverage greater than 10x, to avoid carrying high-leverage exposure into off hours when the underlying market is closed and prices cannot be hedged. The entire position is closed at the prevailing market-close price, with no partial deleverage. PnL is settled and remaining collateral is returned to the trader’s account. The page says this applies to every RWA pair on every regular trading day (Trading RWA).
To keep a position past the close, the Trading RWA docs say leverage must be brought to 10x or below before the market closes. The simplest way they give is adding collateral, which lowers effective leverage without changing position size. Once at or below 10x, the position is treated as an Overnight Position and is not force-closed.
What the Trading RWA page does not say: it gives no exact clock time for the force-close within the session, and no price source beyond “prevailing market-close price.” An agent should not hard-code a guess. It should read the live page and treat the close as an event that can happen at or near the end of the window.
Adding collateral also changes risk. More margin on the same position means more capital exposed to it, and that tradeoff belongs in the agent’s rules, not just a leverage target. That is my reading, not a documented claim.
Off-hours restrictions
For non-trading hours, the Trading RWA page lists what is allowed and what is not:
- Allowed: add collateral, cancel an open order, edit TP/SL (Trading RWA docs).
- Not allowed: open a new position, close an existing position, create a new order, and liquidation (Trading RWA docs).
Two consequences follow from the documented off-hours restrictions, and both are inference rather than separate documented statements. First, an agent holding an overnight position cannot close it off hours; its only documented levers are adding collateral, cancelling an order and editing TP/SL. A rule like “exit if the news turns” has no off-hours execution path. Second, because the page lists liquidation as disabled off hours, an agent should not infer from a quiet weekend that a thinly margined position is safe. The docs do not describe what happens at the next session, so I will not guess.
A related point: in the overnight drift post, I covered how fees accrue and move a position’s liquidation threshold over time, as reflected in the documented liquidation-price formulas. Holding fees accrue over time, while funding can be paid or earned depending on long/short open-interest imbalance. An agent should refresh accrued fees and risk calculations before the next session rather than reuse Friday’s saved figures.
What an agent must encode
None of this is a LeverUp feature request; these are design ideas for the agent’s own code, extending the pre-trade guardrails post.
- A session check as a hard pre-trade gate. Before any open or close order, compute whether the market is in its documented window, using the America/New_York time zone rather than a fixed UTC offset, since Eastern Time shifts with daylight saving. If the check fails, do not queue the order and do not retry in a loop.
- A calendar source of truth. The Trading RWA docs defer to the NYSE schedule for holidays. The agent should read a maintained calendar, and fail closed when the calendar is missing or ambiguous.
- A per-position leverage tier. Tag every open RWA position using the documented day-trade and overnight leverage tiers, and re-tag it when margin is added or the position changes.
- A pre-close decision, made in advance. Define before the session what happens at the end of the window: accept the documented market-close force-close, or reduce leverage to 10x or below. If it chooses to add collateral, the agent needs a spending limit for that, as described in the scoped-keys post (Trading RWA docs).
- An off-hours behavior spec. Treat “close disabled” as a known state, not an error to retry. Limit the agent to the three documented off-hours actions: add collateral, cancel orders, edit TP/SL.
- A margin-asset check. If the margin is a volatile collateral token, the agent must monitor both the position and the collateral’s price: the liquidation documentation calculates margin value from the margin amount and the margin asset’s price. Read the AnyCollateral docs for the collateral rules, and confirm the current supported-token list in the trading UI before assuming a token can be used as margin.
- A fresh read of the rules. Protocol risk-control parameters can change. Re-open the page on a schedule rather than trusting a cached copy, including the numbers quoted in this post.
Closing
An agent built for 24/7 crypto logic can run into a different rulebook on stock perps: session windows, a leverage threshold at 10x, an automatic close of the whole position for anything above it, and a short list of actions allowed off hours. None of this makes stock perps unsuitable for an agent, but it does mean the agent should read the rules before it places an order, not after. Start with the Trading RWA page, check the current schedule and parameters yourself, and treat everything above as design guidance rather than instruction.
This post is educational and is not financial advice. Trading perpetuals with leverage carries risk, including loss of your entire margin.
LeverUp uses a protocol-managed virtual liquidity system powered by the VMMV, where trades reference oracle pricing while execution, settlement, and risk management are handled at the protocol layer. See the documentation on VMMV and settlement, trading RWA, oracle pricing and order execution, liquidation, holding and funding fees, opening a position, closing a position, and risk controls.