Sniper definition

The JSON body you send as definition to POST /agents. Generated from Rout's own schema, so it can't drift from what the backend accepts.

sniper-definition.schema.json 38b473b8…db1bfb59errors.md 9467f423…bf7b83fbREADME.md cd497d83…cdd114de

Three rules that refuse most first attempts

Amounts are integers in base units (2.5 SOL is 2500000000). Keys that may be "none" are sent as null, never omitted. The backend fills in no defaults: every tip, limit, slippage and nonce choice is yours. What each refusal means.

SniperDefinition

Field	Type	Required	Description
`execution`	ExecutionConfig	required	The tip every transaction this sniper sends — buys and sales — pays to be carried. See `ExecutionConfig`.
`exit_plan`	ExitPlanConfig \| null	optional	A stateful, allocation-aware exit plan. This is an alternative to `sells` and legacy `exits`: one position has exactly one exit owner.
`exits`	ExitsConfig \| null	optional	Deprecated — write `sells`. How what this sniper bought is sold, in the language it was first written in: take-profit, stop-loss, held-for. Accepted for one release and translated into `sells`.
`funding`	FundingConfig \| null	optional	Versioned product funding intent.
`limits`	LimitsConfig	required	How much it may spend, hold and lose. See `LimitsConfig`.
`name`	string	required	What an operator calls it. Carried into logs and onto every filled position, so "which sniper bought this" has an answer.
`order`	OrderConfig	required	What every buy spends: the asset, the amount per buy, and the slippage it tolerates. One order for the whole sniper.
`portfolio`	PortfolioConfig	optional	A sniper-wide guard for distinct token positions. This is separate from each rule's `firing` policy, which still governs same-token re-entry.
`required`	RequiredRules	required	The rules this sniper cannot run without — today, which coin it trades (`target`).
`rules`	RuleConfig[]	required	At least one. A sniper with no rules cannot buy anything and would read as a broken subscription rather than as configuration.
`sells`	SellsConfig \| null	optional	How what this sniper bought is sold: sell rules in the buy side's condition language, plus conditions only a holding has (`gain`, `loss`, `drawdown_from_peak`, `held_for`). The design is `docs/SELLS.md`.
`user_id`	string	required	Who owns the wallets below.
`wallet_policy`	WalletPolicyConfig \| null	optional	How a firing is spread across legacy wallets.
`wallets`	string[]	optional	Wallet ids this sniper may spend from. At least one.

Search

Sniper definition

SniperDefinition

Types (60)