Vetted Markets

Why Vetting Matters

On Solana, anyone can create a liquidity pool. This freedom creates a data quality nightmare:

The Problem with Unvetted Data

Without vetting, your charts look like this:

Price ($)
   │     ╱╲  ← Fake wick from $10 trade in tiny pool
   │    ╱  ╲
   │___╱    ╲___╱╲___
   └─────────────────→ Time

With Vybe's vetting:

Price ($)
   │
   │____╱╲___╱╲___
   │
   └─────────────────→ Time
   Real price action from liquid markets

Note: This isn't just about convenience. Bad data leads to bad decisions. Fake wicks trigger stop losses. Manipulated prices distort PnL calculations. Inflated volumes mislead traders. Vybe eliminates these problems at the source.

Vybe's Vetting Criteria

Every market must pass three tests to be included in Vybe's data:

1. Quote Token Requirement

The market must be quoted in a vetted base token:

Why? Tokens quoted against other random tokens can have wildly inaccurate USD valuations.

2. Liquidity Depth Threshold

Pool must have at least 10% of the deepest vetted pool's USD liquidity for that token.

Example: If the deepest SOL/TOKEN pool has $100,000 liquidity, other pools need at least $10,000 to be included.

Why? Pools with tiny liquidity are easily manipulated. A $100 trade shouldn't be able to move prices significantly.

3. Balance Symmetry Check

Each side of the pair must hold at least 5% of the pool's total USD value.

Why? One-sided pools (e.g., 95% Token A, 5% Token B) are structurally broken and produce unreliable price data.

What Vetted Markets Power

The vettedMarketsOnly Parameter

Some endpoints let you toggle vetting (though we recommend keeping it on):

# Vetted markets only (default, recommended)
GET /tokens/{mint}/candles?vettedMarketsOnly=true

# All markets including unvetted (use with caution)
GET /tokens/{mint}/candles?vettedMarketsOnly=false

Endpoint Configuration

When to Disable Vetting

In rare cases, you may want unvetted data:

⚠️ Warning: Unvetted data can include fake prices, wash trading, and manipulated volumes. Always handle with caution and never use for production trading decisions.

Real-World Example

Scenario: MEMECOIN Price Query

Without vetting (other APIs):

Pool A (Raydium CLMM): $50,000 liquidity, Price: $0.001
Pool B (Random DEX):   $50 liquidity,     Price: $0.1    ← 100x higher!
Pool C (Wash trading): $10,000 "liquidity", Price: $0.05

Aggregated price: Somewhere between $0.001 and $0.1
Chart shows: Massive fake wicks from Pool B
PnL shows: Wildly inaccurate profits

With Vybe vetting:

Pool A (Raydium CLMM): $50,000 liquidity, Price: $0.001 ← Only this counts
Pool B: Excluded (liquidity below threshold)
Pool C: Excluded (fails balance symmetry)

Price: $0.001 (accurate)
Chart: Clean, real price action
PnL: Accurate profit/loss

How Vetting Affects Different Features

Price Feeds

• Only prices from vetted pools are aggregated, weighted by liquidity depth. No outliers from manipulated pools.

Candlestick Charts

• OHLCV data comes exclusively from vetted markets. No fake wicks from low-liquidity trades.

PnL Calculations

• Wallet profit/loss uses vetted trade prices for cost basis and current value. Results match reality.

Top Trader Rankings

• Rankings based on trades in vetted markets only. No inflation from wash trading.

Holder Valuations

• Token values in wallet balances use vetted market prices. Portfolio values are accurate.

Next Steps

• Data Quality - How we ensure accuracy across all data types
• Supported DEXs - Which protocols we integrate with