Skip to main content
Recipes for building common option structures inside a Strategy. Each recipe shows the two ways pulse lets you resolve the legs:
Resolve each leg yourself from the DataFeed and the resolvers - an expiry via resolver.expiry.relative and a strike via resolver.strike.delta - then build the Option and place the order. Most explicit; you see every strike.
Both paths resolve to the same strikes - the helper is just a thin wrapper over the resolvers. Reach for the helper when a structure exists; drop to manual when you need a leg the helpers don’t cover or want full control.
Shared conventions in these recipes
  • self.underlying_id is a list - recipes use self.underlying_id[0].
  • Strikes are picked by delta (e.g. 0.20 ≈ 20-delta); expiries are the nth monthly with at least min_dte days left. See Resolvers for the full grammar.
  • Orders are sized to whole contracts (is_lots=True) and fill on the next pulse.
  • +quantity buys, -quantity sells.
The recipes on the family pages show just the leg resolution + orders (the part that differs per structure). They assume the imports and helpers below.
In the snippets below, u = self.underlying_id[0] and size = self._size(<a leg>).

Catalogue

The helper resolvers (and exotic variants - condors, iron condors/butterflies, albatross, pterodactyl) are listed in the [structures API reference][pulse.structures].
Last modified on November 4, 2026