Generalizing the implied volatility skew into parameters is a good way to get an overall view of the surface. Comparing the parameters to history, to related stocks or to ETFs is a good way to see what part of the skew might be overpriced. For example, if the slope is steep and other stocks or ETFs are not, the put IV might be overpriced relative to calls.

To drill down to the specific areas on the implied volatility skew, the use of delta buckets to categorize implied volatility can be helpful. ORATS breaks down each expiration into 21 volatility buckets from 100 delta to 0 delta every 5 deltas.

Here's a picture of XLK from 5/22/19 delta bucktest of IVs:


We call this our Monies (short for money-ness) part of the Data API. Trial

Monies are available each trading day back to 2007.

Tracking areas of the volatility surface using delta buckets can help identify areas of over or undervalued parts of the skew.

More reading:

How to Set Up a Pairs Trading Backtest

Term Structure of Implied Volatility

related posts

Python Access to Our API
Data, data api, Python, code example

Python Access to Our API

Python is a popular programming language that lets you work quickly and integrate systems...

Read Post
Futures Prices Implied from Options Prices for Indexes
Data, Index Options, Futures Prices, Options Pricing

Futures Prices Implied from Options Prices for Indexes

Indexes price options off of futures prices for each expiration. Here's how ORATS does handles...

Read Post

We're here, if you need us.

Still curious how we can help you?