Documentation Index
Fetch the complete documentation index at: https://lurkai.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
What Divergent View is
Divergent View is an extension of the Arb Scanner. The Arb Scanner surfaces potential opportunities. Divergent View helps explain why an opportunity may exist, where the disagreement is coming from, and whether the spread deserves deeper review. Instead of only showing that two related markets have different prices, Divergent View gives users a clearer look at the disagreement behind the scan. The goal is to help users separate:- real divergence
- stale pricing
- weak matches
- liquidity noise
- resolution-rule differences
- genuinely interesting market disagreement
How it extends the Arb Scanner
The Arb Scanner answers:What Divergent View is for
Use Divergent View when an Arb Scanner result needs a second look. It helps users understand:- why two markets are pricing differently
- whether the markets are truly comparable
- whether the spread may be caused by stale data
- whether the resolution rules match
- whether one venue is moving faster than another
- whether related markets are reacting unevenly
- whether the opportunity is clean, noisy, or suspicious
Why divergence matters
Not every spread is a clean opportunity. A price gap may exist because the market is inefficient, but it may also exist because something is wrong with the comparison. Divergence can come from:- real market disagreement
- different contract wording
- mismatched settlement criteria
- low liquidity
- stale quotes
- different close times
- delayed venue reactions
- one market pricing in new information faster
- user sentiment diverging from market pricing
What Divergent View may show
Depending on the current version of Lurk, Divergent View may include:- the original Arb Scanner opportunity
- the markets being compared
- the visible spread
- market wording or outcome comparison
- venue differences
- price movement context
- freshness indicators
- liquidity context
- possible mismatch warnings
- supporting Signal Search context
- related market movement
- Track Record or Lurk Score context if relevant
Common divergence types
Cross-venue price divergence
This happens when similar outcomes are priced differently across venues. Example:Resolution divergence
This happens when two markets look similar but may not resolve the same way. Example:Timing divergence
This happens when related markets have different close times, update speeds, or catalyst exposure. Example:Liquidity divergence
This happens when the spread looks good, but one side may be too thin to execute cleanly. Example:Related-market divergence
This happens when connected markets move differently even though they should influence each other. Example:Using Divergent View
A typical workflow:- Open the Arb Scanner.
- Select an opportunity.
- Open Divergent View.
- Review why the scanner surfaced the spread.
- Compare the market terms and outcome structure.
- Check freshness, liquidity, and venue differences.
- Decide whether the spread looks clean, noisy, stale, or worth deeper review.
Best practices
Use Divergent View before trusting a scanner result. Before acting on a spread, check:- whether the outcomes truly match
- whether the markets resolve the same way
- whether close dates or settlement rules differ
- whether both sides have enough liquidity
- whether one price is stale
- whether fees change the return
- whether the spread is still available
- whether the divergence has a real explanation

