Skip to main content
Natural-language signals ({ "text": "..." }) are parsed by the same engine used for Telegram and Discord signal groups. Use this reference when authoring text lines or testing in the sandbox.

Entry patterns

Lifecycle patterns

Token resolution

  • Tickers: $SOL, SOL, WIF (after entry verbs)
  • Contract: Solana mint address in structured/legacy payloads
  • Unresolved tickers return token_unresolved skip reason

Multi TP ladders

Custom keywords

Per-agent signalDetectionRule can override buy/sell/TP/SL keyword lists. Test parsing:

Always include idempotency

Always send a stable idempotencyKey with NL text signals. Without it, a retried or replayed signed request can execute twice (bug #391).

Structured alternative

For production bots, prefer structured eventType payloads in Signal envelope to avoid parser ambiguity.