Venue-specific APIs
Different protocols, subscription flows, and operational behavior for each integration.
Financial data infrastructure
Access financial market data across centralized exchanges, decentralized venues, and onchain pools through one consistent API.
Create an account or sign in to Console.
Built for developers, AI agents, and automated systems.
The problem
Every venue brings another connection lifecycle, symbol format, payload schema, and set of edge cases. The integration may launch once; the maintenance never does.
Different protocols, subscription flows, and operational behavior for each integration.
Fields, symbols, timestamps, and market models must be translated before use.
Upstream changes multiply across every adapter, parser, and data pipeline.
Unified market data
Gateway provides a consistent public boundary while Market Hub handles venue connections, subscriptions, and normalization behind it.
Your systems

Market sources
Multi-venue aggregation
Request a canonical symbol and market type. Market Hub combines eligible observations into a consistent, venue-independent view.
Order-book venues provide normalized BBO and Trade data. EVM, Sui, and Solana AMMs provide quantity-dependent quotes and observed Swaps for configured pools.
MarketHub.BBO.Subscribe with consolidated best bid and offer data.
Additional aggregation modes and strategy-oriented derived APIs.
Venue coverage
17 venue integrations, including 16 configured in production.
Coverage reviewed on September 12, 2026.
Normalized top-of-book and public executions, with one-minute Candles derived from Trade data.
| Venue | Spot | Perpetual | Market data | Deployment |
|---|---|---|---|---|
| BBinance | Configured | Configured | BBO, Trade, Candle | Production |
| HHyperliquid | Configured | Configured | BBO, Trade, Candle | Production |
| BTBTSE | Configured | Configured | BBO, Trade, Candle | Production |
| BYBybit | Configured | Configured | BBO, Trade, Candle | Production |
| CCoinbase | Configured | Configured | BBO, Trade, Candle | Production |
| DdYdX | — | Configured | BBO, Trade, Candle | Production |
| OOKX | Configured | Configured | BBO, Trade, Candle | Production |
| LLighter | Supported | Supported | BBO, Trade, Candle | Implemented |
Quantity-dependent executable quotes for configured pools. These are synthetic Spot observations, not order-book BBO.
| Venue | Network family | Market | Market data | Deployment |
|---|---|---|---|---|
| AAerodrome | EVM | Spot | Executable quote, Swap | Production |
| U3Uniswap v3 | EVM | Spot | Executable quote, Swap | Production |
| U4Uniswap v4 | EVM | Spot | Executable quote, Swap | Production |
| BBluefin | Sui | Spot | Executable quote, Swap | Production |
| CCetus | Sui | Spot | Executable quote, Swap | Production |
| MMomentum | Sui | Spot | Executable quote, Swap | Production |
| TTurbos | Sui | Spot | Executable quote, Swap | Production |
| RRaydium | Solana | Spot | Executable quote, Swap | Production |
| MEMeteora | Solana | Spot | Executable quote, Swap | Production |
Production means the venue is configured for Market Hub; it does not guarantee that an upstream connection is currently healthy or that every symbol is available. Implemented integrations are not yet enabled in the production API at the time of review. Supported market types depend on venue configuration. Current runtime status and enabled symbols are discoverable through MarketHub.ListVenues and MarketHub.ListSymbols. Public access focuses on real-time derived aggregation; direct historical dataset access is a future capability.
Developer experience
Use JSON-RPC for consistent operations, WebSocket for real-time subscriptions, the released Agent CLI for interactive onboarding and discovery, or the public MCP server for agent-facing tools.
Connect through Gateway, install k4k3ru-agent from npm, or use the MCP server at mcp.k4k3ru.com.
Choose a market type and normalized symbol.
Receive one venue-independent view calculated across eligible markets.
01 {
02 "jsonrpc": "2.0",
03 "id": 1,
04 "method": "MarketHub.BBO.Subscribe",
05 "params": {
06 "marketType": "perp",
07 "symbol": "BTC/USDC"
08 },
09 "auth": {
10 "apiKey": "<API_KEY>",
11 "timestamp": 1786527553,
12 "nonce": "<NONCE>",
13 "signature": "<SIGNATURE>"
14 }
15 }
01 {
02 "ac": "crypto",
03 "mt": "perp",
04 "s": "BTC/USDC",
05 "b": {"p": "63004.4", "q": "1.2"},
06 "a": {"p": "63004.5", "q": "0.8"},
07 "svc": 3,
08 "v": 42,
09 "ts": 1786775190574419
10 }
Schema example based on the current repository contract. Values are illustrative.
Usage credits
Credits are prepaid API usage. Calls consume ticks from your balance—without monthly subscriptions or recurring plans.
API usage consumes ticks. Consumption rates vary by operation and are documented separately.
Roadmap
Current direction without fixed release-date commitments.
A separate execution component for unified trading operations. Implementation is underway; its public API is not yet available.
Product details and release timing will be announced separately.
Roadmap items may change based on technical findings, venue availability, operational requirements, and user feedback.
Start building
Create an account in Console to explore market data, manage API keys, and view your usage. Use the documentation as you build your integration.