# Stryke API > Market intelligence and execution across 74 chains with live market data — plus holder and security analysis on 29, and non-custodial quotes on 59. Base URL `https://api.stryke.gg`. Auth depends on the endpoint family: the v1 trading & account API (`/v1/*`) uses `Authorization: Bearer `; the v2 market-data API (`/api/v2/*`) uses `X-API-Key: `. Public endpoints need no key. Responses are JSON: `{"success":true,...}` on success, `{"success":false,"error":"..."}` on failure. ## Reference for AI agents - [Full API reference](https://docs.stryke.gg/llms-full.txt): every endpoint, parameter and response in Markdown - [OpenAPI 3.1 spec](https://docs.stryke.gg/openapi.json): machine-readable schema - [Interactive docs](https://docs.stryke.gg): human-facing portal with a live playground ## Use it as tools (MCP) - [stryke-mcp.mjs](https://docs.stryke.gg/stryke-mcp.mjs): a zero-dependency MCP server exposing 16 read-only tools over stdio (Node 18+). - Works with Claude Desktop, Claude Code, Cursor, or any MCP client. Config: `{"mcpServers":{"stryke":{"command":"node","args":["/path/to/stryke-mcp.mjs"],"env":{"STRYKE_API_KEY":"your-key"}}}}` - Tools: list_chains, get_token, get_price, get_price_at, get_ohlcv, get_trades, get_pools, get_token_security, get_holders, screen_tokens, search_tokens, get_wallet_portfolio, get_wallet_pnl, get_wallet_trades, get_swap_quote, get_chain_status. - Every one of those tools is READ-ONLY: the MCP server declares a literal GET path per tool and refuses anything else, so an agent wired to it cannot move funds. - Scope that precisely: it is a statement about the MCP tool surface, NOT about the whole API. The REST API does expose swap, limit-order and DCA endpoints, and they are reachable with a key over HTTP — they are simply not among the tools above. - Setup guide: https://docs.stryke.gg/#/mcp ## Chain coverage - **118 chains recognised** — 74 with a live market tape, 29 with holder and security analysis, 59 quotable. - Every flag is MEASURED, re-probed every six hours (last measured 2026-10-04T04:17:00Z) — never declared. - The catalogue is a public endpoint and takes **no API key**: `GET https://api.stryke.gg/api/v2/chains` - `/api/v2/chains/summary` — the counts alone - `/api/v2/chains/{chain}` — one chain, with its measured evidence - `/api/v2/chains/resolve?q=…` — a name, alias or chain id to a canonical key - Do not hard-code a chain list from this file: read the endpoint. - Human-readable matrix: https://stryke.gg/chains ## Endpoint groups - **Tokens** (17) — Token data endpoints under /api/v2/tokens. - **Wallets** (21) — Wallet data endpoints — the core of the v2 API for portfolio dashboards, tax tools, and wallet explorers. - **Market & Charts** (7) — Macro Solana market data plus every price-history and candle (OHLCV) endpoint. - **Whales** (4) — Smart-money / "whale" intelligence endpoints under /api/v2/whales. - **Trading** (9) — Swap, limit-order, and DCA endpoints backed by Jupiter's lite-api (lite-api.jup.ag). - **Launches** (1) — Recent Solana token launches, proxied through Stryke's on-chain indexer (HTTP GET /v1/indexer/recent-pools on Stryke-trading-api, real-time gRPC-fed). - **RPC** (1) — Generic, read-only Solana JSON-RPC passthrough to Stryke's node layer mainnet, exposed under /api/v2/rpc. - **Streaming** (1) — Realtime WebSocket gateway at wss://api.stryke.gg/api/v2/stream (Stryke's engine), attached to the same HTTP server as the REST API. - **Account & Keys** (10) — Issue and manage API keys via a Solana wallet: register, regenerate, the SIWS sign-in challenge/login, and the developer dashboard (usage, fee-wallet, allowed domains, white-label license).. - **Recovery (v1)** (5) — The v1 token-account recovery API: scan a wallet for closeable/rent-bearing SPL accounts, build a close transaction, confirm it, plus wallet analysis, token info, and aggregate stats.. - **Direct RPC** (3) — Solana RPC passthrough: send a signed transaction, check its status, and simulate before sending.. - **System** (2) — Service health and status. - **Trading API: Trade & Execution** (18) — Auth: send your key as `Authorization: Bearer ` (the trading API uses Bearer, NOT the X-API-Key header used by the data API). - **Trading API: Wallets** (8) — Auth: send your key as `Authorization: Bearer ` (the trading API uses Bearer, NOT the X-API-Key header used by the data API). - **Trading API: Keys & Sessions** (5) — Auth: send your key as `Authorization: Bearer ` (the trading API uses Bearer, NOT the X-API-Key header used by the data API). - **Trading API: Billing & Tiers** (4) — Auth: send your key as `Authorization: Bearer ` (the trading API uses Bearer, NOT the X-API-Key header used by the data API). - **Trading API: Token Verification** (3) — Auth: send your key as `Authorization: Bearer ` (the trading API uses Bearer, NOT the X-API-Key header used by the data API). - **Trading API: Quests** (10) — Auth: send your key as `Authorization: Bearer ` (the trading API uses Bearer, NOT the X-API-Key header used by the data API). - **Trading API: Account & Profile** (23) — Auth: send your key as `Authorization: Bearer ` (the trading API uses Bearer, NOT the X-API-Key header used by the data API). - **Trading API: Fees, PnL & Positions** (11) — Auth: send your key as `Authorization: Bearer ` (the trading API uses Bearer, NOT the X-API-Key header used by the data API). - **Trading API: Indexer** (9) — Auth: send your key as `Authorization: Bearer ` (the trading API uses Bearer, NOT the X-API-Key header used by the data API). - **Trading API: Limit Orders & DCA** (13) — Auth: send your key as `Authorization: Bearer ` (the trading API uses Bearer, NOT the X-API-Key header used by the data API). - **Trading API: Copy Trade** (24) — Auth: send your key as `Authorization: Bearer ` (the trading API uses Bearer, NOT the X-API-Key header used by the data API). - **Trading API: AFK Auto-Buy** (28) — Auth: send your key as `Authorization: Bearer ` (the trading API uses Bearer, NOT the X-API-Key header used by the data API). - **Trading API: Sniper & Auto-Sell** (18) — Auth: send your key as `Authorization: Bearer ` (the trading API uses Bearer, NOT the X-API-Key header used by the data API). - **Trading API: System** (2) — Auth: send your key as `Authorization: Bearer ` (the trading API uses Bearer, NOT the X-API-Key header used by the data API). - **Programs** (1) — On-chain program (smart-contract) intel — account, upgrade state, activity, type mix.. - **Positions** (1) — DeFi position aggregation across Kamino, Drift, MarginFi, Jupiter Perps.. - **Webhooks** (8) — Push delivery the other way round: instead of holding a connection open, you give us an https endpoint and we POST to it when a trade happens. - **Streaming (SSE)** (3) — Push delivery over Server-Sent Events, fed by Stryke's OWN index rather than by a reseller. - **Chain-generic market data** (26) — One set of 26 endpoints that works on every chain in the catalog, under /api/v2/chain/{chain}/*. - **Chains (catalog)** (4) — The public chain catalog. - **Screener (pairs)** (11) — Every DEX pair the index follows, ranked. - **Wallets (first-party)** (3) — What an address has actually traded, read from Stryke’s own tape. - **Tokens (first-party)** (4) — One token across every market it trades in — identity, the price its deepest market sets, cross-pool totals and the market list.