SQUEEZEOS · METHODOLOGY

How SqueezeOS Generates Trading Signals

Q: How much does a paid SqueezeOS result cost?

Call the exact live resource and read its fresh PAYMENT-REQUIRED challenge. The challenge supplies the current amount and Base-mainnet USDC terms before any caller-authorized payment decision.

SqueezeOS's OracleEngine aggregates connected market engines into a directive per symbol. This page documents the methodology; it does not print a supposedly “live” signal that would immediately become stale.

Quick facts

Directive thresholds: BUY (IGNITION) ≥ 82 confidence, BUY ≥ 60, HOLD ≥ 40, SELL ≥ 20, SHIELD below that.
Regime labels: ALPHA_EXPANSION, MACRO_COLLAPSE, NEUTRAL, SHIELD.
Caching: results are cached 60 seconds per symbol to avoid redundant recomputation.
Access: use the live SqueezeOS API/MCP. For any paid resource, the target resource's fresh PAYMENT-REQUIRED challenge is authoritative for the current amount and terms.
Payment authority: x402 v2 · USDC · Base mainnet eip155:8453. The caller controls spending authorization.
No demo data policy: if required upstream data is unavailable, the service should return an unavailable/error state rather than fabricate a market signal.

Frequently asked questions

What does a SqueezeOS BUY (IGNITION) directive mean?

It means the OracleEngine's aggregated confidence score for that symbol, computed from live data at request time, is 82 or higher — the highest-conviction bucket in its directive scale.

Can I see a current signal on this page?

No. A real signal requires calling the live service against current market data. Static example signals would become stale and are not presented as live evidence.

How much does a paid SqueezeOS result cost?

Do not rely on a cached price from this page. Call the exact live resource and read its fresh PAYMENT-REQUIRED challenge. That challenge supplies the current amount and accepted Base/USDC terms before any caller-authorized payment decision.