Orders that wait for a price
Limit and stop orders live server-side and execute when the market crosses your trigger — no babysitting, and no signature per fill.
Updated
The four types
| Type | Triggers when | Use |
|---|---|---|
| limit_buy | Price drops to or below your limit | Buy a dip without watching the chart |
| limit_sell | Price rises to or above your limit | Take profit at a target |
| stop_buy | Price rises to or above your stop | Enter on a breakout |
| stop_sell | Price drops to or below your stop | Cut a position on a breakdown |
- limit_buy
- Triggers when
- Price drops to or below your limit
- Use
- Buy a dip without watching the chart
- limit_sell
- Triggers when
- Price rises to or above your limit
- Use
- Take profit at a target
- stop_buy
- Triggers when
- Price rises to or above your stop
- Use
- Enter on a breakout
- stop_sell
- Triggers when
- Price drops to or below your stop
- Use
- Cut a position on a breakdown
Creating one
vectr agent "set a limit buy on 0x… at 20% below the current price, 0.05 ETH"Or directly — the orders API is session-authenticated:
- POST /orders
- Create — body: wallet, tokenAddress, curveAddress, tokenSymbol, tokenName, type, side, plus the type's params
- GET /orders
- All your orders, newest first
- PATCH /orders/:id
- Reprice an open limit/stop
- DELETE /orders/:id
- Cancel
- GET /orders/history?tokenAddress=
- Your trades on that token
wallet must be present to pass validation but is ignored: an order always belongs to the session wallet. GET /orders returns orders in any status: open, pending_execution, filled, cancelled or expired. PATCH takes {limitPrice}. History lists every trade you made on the token, not only order fills (?limit, default 20).
Parameters and bounds
| Param | Bound | Notes |
|---|---|---|
| limitPrice | positive | The trigger, in the token's quote asset |
| slippage | 0–50% | Tolerance around the trigger at execution |
| expiresAt | ISO date | Optional — dead orders don't sit forever |
| taoAmount | positive | How much to spend on buys, in the pairing asset (the field name predates Robinhood Chain) |
| tokenAmount | positive | How much to sell on sells |
- limitPrice
- Bound
- positive
- Notes
- The trigger, in the token's quote asset
- slippage
- Bound
- 0–50%
- Notes
- Tolerance around the trigger at execution
- expiresAt
- Bound
- ISO date
- Notes
- Optional — dead orders don't sit forever
- taoAmount
- Bound
- positive
- Notes
- How much to spend on buys, in the pairing asset (the field name predates Robinhood Chain)
- tokenAmount
- Bound
- positive
- Notes
- How much to sell on sells
Orders execute from your own custodial wallet when the trigger hits — there is no separate oracle signing your fills. Creating the order is the consent; execution is the consequence.
A trigger is not a guaranteed fill
Price can gap through a limit on a thin curve — the order fires at the trigger, the trade executes at whatever the curve gives within your slippage bound. Size accordingly.