# Crypto Signal Radar

Liquidity, Leverage & On-chain Reflexivity

Site: https://crypto.signal-radar.com/
Site ID: crypto-signal-radar
Profile: crypto
Generated: 2026-07-24T17:56:30.000Z

## First Read
1. Read /.well-known/signal-radar.json for canonical discovery.
2. Read /api/v1/agent-runtime before interpreting the current market snapshot.
3. Call get_crypto_market_regime before interpreting any asset move.
4. Read snapshot.releaseReadiness.selectedDerivativeVenue, coreReady, criticalGroups and optionalFailures before using derivatives context.
5. Read Source Health and Evidence before relying on degraded, Last Known Good or proxy-backed values.
6. Treat selected derivatives values as a venue-scoped proxy, never as a market-wide liquidation map.
7. Keep all outputs in read-only market-context mode.

## Static Endpoints
- /.well-known/agent-gateway.json (application/json): Same-origin read-only static agent surface manifest.
- /.well-known/agent-policy.json (application/json): Read-only policy and runtime boundaries.
- /.well-known/signal-radar.json (application/json): Signal Radar well-known discovery metadata.
- /agent.json (application/json): Top-level agent-readable manifest and endpoint map.
- /assets/crypto-tools.mjs (text/javascript): Client WebMCP handler module for get_crypto_market_regime
- /data/v1/agent-index.json (application/json): Machine-readable endpoint index.
- /data/v1/agent-routes.json (application/json): Static Agent Markdown page route index.
- /data/v1/public-safety.json (application/json): Public-safe use and content guard metadata.
- /llms.txt (text/plain): Plain text discovery summary for AI crawlers and humans.

## Read-only Tools
- get_crypto_market_regime: Return the current market regime, four axes, selected derivatives venue, release readiness, freshness and source-backed Evidence. (/assets/crypto-tools.mjs)
- explain_asset_move: Explain whether a BTC, ETH or SOL move is spot, liquidity, leverage or network led, separating the analysis window from 24h context. (/assets/crypto-tools.mjs)
- get_leverage_pressure: Rank BTC, ETH and SOL leverage pressure for the dynamically selected venue-scoped proxy; never a market-wide liquidation map. (/assets/crypto-tools.mjs)
- rank_capital_rotation: Rank source-backed capital-pressure nodes. Sector mode is limited to BTC, ETH and SOL major themes, not a market-wide sector universe. (/assets/crypto-tools.mjs)
- get_stablecoin_liquidity_state: Return stablecoin liquidity, unambiguous provider and Gecko identity, peg assessment, observed price, target and source-backed Evidence. (/assets/crypto-tools.mjs)
- get_source_health: Return critical and optional source freshness, last success, next due, circuit state, Last Known Good use, selected venue and release readiness. (/assets/crypto-tools.mjs)
- get_signal_evidence: Return one Evidence item from the latest coherent snapshot in the normalized public Evidence format. (/assets/crypto-tools.mjs)
- list_active_crypto_signals: List current persistent, root-cause-deduplicated, non-stale crypto signals with windows, selected source and normalized Evidence. (/assets/crypto-tools.mjs)

## Agent-readable pages

- [Agent surface manifest](/.well-known/agent-gateway.json)
- [Agent route index](/data/v1/agent-routes.json)

Canonical JSON feeds should be preferred over generated Markdown pages.

## Runtime Boundary
- Static read-only files only.
- Agent Markdown is generated from local build artifacts; no runtime fetch is required.
- No MCP server, app runtime, authentication, or external execution is provided by this package.

## Public Safety
- Read only: true
- Public safe: true

## Live runtime API

- snapshot: /api/v1/snapshot
- agent_runtime: /api/v1/agent-runtime
- signals: /api/v1/signals
- rotation: /api/v1/rotation
- health: /api/v1/health
- evidence: /api/v1/evidence/{evidenceId}
- asset: /api/v1/assets/{assetId}
- export_signals: /api/v1/export/signals