> For the complete documentation index, see [llms.txt](https://k4k3ru.gitbook.io/k4k3ru-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://k4k3ru.gitbook.io/k4k3ru-docs/overview.md).

# Overview

K4K3RU is an API-first financial infrastructure service designed for AI agents, automated trading bots, and developers.

It provides unified access to derived financial market data calculated across multiple venues. Instead of building and maintaining a separate integration for every exchange or market-data provider, clients can access a venue-independent market view through K4K3RU's direct API, released Agent CLI, or dedicated MCP interface. Complete first-party SDK clients are under development, while the browser-based Console is a future product.

## What K4K3RU Provides

The core of K4K3RU is the **Market Hub**, which connects to multiple market venues and exposes derived aggregate results through a unified interface. Venue-specific feeds are not part of the public API.

K4K3RU is designed to provide:

* Direct API access through the Gateway API Server at `api.k4k3ru.com`
* Interactive Agent CLI access through the npm package `k4k3ru-agent`
* First-party SDKs that connect to the Gateway API Server at `api.k4k3ru.com` **(under development)**
* Dedicated MCP access through the MCP API Server at `mcp.k4k3ru.com`
* Real-time derived market data through WebSocket subscriptions
* Consistent JSON-RPC request and response formats
* Venue-independent aggregation across normalized internal market states
* API credential and account management
* Usage-based access and credit management
* Payment infrastructure for purchasing service credits

The initial focus is cryptocurrency market data. Market Hub currently supports Binance, Hyperliquid, BTSE, Bybit, Coinbase, dYdX, and OKX order-book integrations. dYdX currently provides Perpetual market data only. Configured AMM integrations include Uniswap v3/v4, Aerodrome, Bluefin, Cetus, Turbos, Momentum, Raydium and Meteora. [AMMPool](https://github.com/k4k3ru-hub/k4k3ru/tree/main/docs/public/api/market-hub/amm-pool.md) exposes pool metadata, observed pool prices and retained-state status separately from public BBO/OrderBook feeds. [Spread](/k4k3ru-docs/api/market-hub/get-spread-snapshot.md) compares AMM pool mids with quantity-specific order-book VWAP.

The platform is also designed to expand beyond cryptocurrency into other financial markets, including FX.

## How It Works

K4K3RU provides four currently available or in-development client access paths.

1. **Direct API path** — users, developers, bots, and other API clients connect directly to the Gateway API Server at `api.k4k3ru.com`.
2. **SDK path (under development)** — applications use K4K3RU SDKs, which connect directly to the Gateway API Server at `api.k4k3ru.com`.
3. **Agent path** — users install `k4k3ru-agent` from npm and use its interactive commands for account onboarding and selected account and Market Hub operations. Agent sends all service operations through Gateway.
4. **MCP path** — AI agents and MCP-compatible clients connect to the MCP API Server at `mcp.k4k3ru.com`. The MCP Application communicates with Gateway to access K4K3RU capabilities.

```mermaid
flowchart LR
    DirectClient[Developer / Bot / API Client]
    SDKClient[Application / SDK User]
    AgentUser[CLI User]
    MCPClient[AI Agent / MCP Client]

    SDK[K4K3RU SDK<br/>Under Development]
    Agent[K4K3RU Agent<br/>Available]
    Gateway[Gateway API Server<br/>api.k4k3ru.com]
    MCP[MCP API Server<br/>mcp.k4k3ru.com]

    CRM[CRM]
    Payment[Payment]
    MarketHub[Market Hub]
    Venues[Market Venues]

    DirectClient <-->|HTTPS / WSS| Gateway
    SDKClient -.->|Uses| SDK
    SDK -.->|HTTPS / WSS| Gateway
    AgentUser -->|Interactive commands| Agent
    Agent -->|HTTPS / JSON-RPC| Gateway
    MCPClient <-->|MCP over HTTPS| MCP
    MCP <-->|K4K3RU API| Gateway

    Gateway <--> CRM
    Gateway <--> Payment
    Gateway <--> MarketHub
    MarketHub <-->|Venue-specific APIs| Venues
```

The **Gateway API Server** is the direct K4K3RU API endpoint and routes authenticated operations to CRM, Payment, and Market Hub. It is used by direct API clients and Agent and, when released, by the browser-based Console and complete K4K3RU SDK clients.

The **Console** is a future browser-based K4K3RU product and is not currently available.

The **SDKs** are public client foundations currently under development. The Go module already provides JSON-RPC models, application errors, and request-signing utilities used by Agent. A complete top-level Gateway client and transports are not yet available.

The **K4K3RU Agent** is an available interactive CLI for macOS and Linux. It supports email-OTP account onboarding, local API credential management, usage and product queries, and Market Hub venue and symbol discovery. It does not connect directly to venues or place trades.

The **MCP API Server** is a separate public server for AI agents and MCP-compatible clients. It handles authenticated MCP requests and communicates with Gateway for the K4K3RU operations required by each tool. MCP does not connect directly to CRM, Payment, or Market Hub. See [MCP](/k4k3ru-docs/mcp.md) for the endpoint, authentication, and available tools.

All four paths preserve the same domain boundaries while allowing clients to use the interface appropriate for their integration.

## Service Architecture

K4K3RU is organized around its core service applications and client interfaces. Agent is available; complete SDK clients and Trade Hub are under development, while Console is a future product:

### Console — Future

The browser-based first-party interface for K4K3RU. Product details and release timing will be announced separately.

Console is not currently available.

### SDKs — Under Development

First-party client libraries for integrating with K4K3RU. The SDKs are currently under development.

The Go SDK foundation provides reusable protocol models, application errors, and signing utilities. General Gateway transport clients remain under development. SDKs do not access CRM, Payment, Market Hub, or Trade Hub directly.

### Agent — Available

The npm-distributed `k4k3ru-agent` application is an interactive Gateway client for account onboarding and selected service operations. Install it with `npm install --global k4k3ru-agent`, then run `k4k3ru-agent` and type `/` to browse commands.

### Gateway

The direct public API server for K4K3RU APIs and WebSocket connections, exposed at `api.k4k3ru.com`.

Gateway authenticates requests, manages client sessions, and routes operations to the application responsible for each capability. It is also the internal K4K3RU API boundary used by the MCP Application.

### MCP

Provides a dedicated public MCP API server for AI agents and MCP-compatible clients at `mcp.k4k3ru.com`.

The MCP Application handles the MCP protocol, translates approved agent-facing tool calls into the required K4K3RU operations, and communicates with Gateway through explicit API contracts. It does not connect directly to CRM, Payment, Market Hub, or Trade Hub.

### CRM

Manages accounts, authentication, API credentials, permissions, subscriptions, usage, and service credits.

### Market Hub

Connects to market venues, maintains their latest internal state, evaluates derived market views, and distributes aggregate updates through Gateway.

### Payment

Manages payment intents, payment processing, payment monitoring, and payment completion.

These applications have separate responsibilities and communicate through explicit internal contracts. This allows each part of the service to evolve independently while preserving a stable public API.

## Who K4K3RU Is For

K4K3RU is initially designed for:

* AI agents and agent developers integrating financial data through the public API or MCP interface
* Automated and algorithmic trading bots
* Developers building financial applications
* Teams integrating data from multiple trading venues
* Systems that require a consistent market-data interface

K4K3RU is API-first. Direct integrations can use the Gateway API Server at `api.k4k3ru.com`, while users can access selected workflows through the released Agent CLI. Complete first-party SDK clients are under development, while Console is a future product.

The MCP API Server at `mcp.k4k3ru.com` provides an additional interface for MCP-compatible agents and clients. APIs remain the primary product surface.

## API-First Design

K4K3RU prioritizes:

* Consistent public contracts
* Explicit authentication
* Real-time data delivery
* Clear application boundaries
* Reliable and idempotent operations
* Venue-independent client integrations
* Separate direct API, Agent, SDK, and MCP access paths
* Long-term extensibility

Venue-specific behavior is isolated behind adapters wherever possible. This allows additional venues and asset classes to be introduced without requiring clients to completely redesign their integrations.

Agent and SDKs follow the same boundary model: they use Gateway for K4K3RU operations rather than accessing domain applications directly. MCP owns the MCP-facing protocol and tool surface, while Gateway remains the API boundary to CRM, Payment, Market Hub, and Trade Hub capabilities.

## Trade Hub — Under Development

K4K3RU is implementing **Trade Hub** as a separate component that extends the hub model to trading operations. Its public API is not yet available.

Market Hub and Trade Hub will remain separate components because market-data distribution and trade execution have different security, reliability, and state-management requirements.

## Current Direction

K4K3RU is being developed incrementally.

The current priorities are:

1. Establish a stable public API and authentication model.
2. Provide reliable derived market-data access through Market Hub.
3. Expand support to additional cryptocurrency venues.
4. Expand Agent workflows and continue development of first-party SDK transports for Gateway API integration.
5. Expand the approved K4K3RU capabilities exposed through the MCP API Server.
6. Improve developer documentation and integration tooling.
7. Extend the platform to FX and other financial markets.
8. Continue implementing unified trading capabilities through Trade Hub.

## Next Steps

Start by learning how K4K3RU requests are structured and how clients authenticate.

* [Getting Started](/k4k3ru-docs/getting-started.md)
* [API Request Authentication](/k4k3ru-docs/api/authentication.md)
* [JSON-RPC Format](/k4k3ru-docs/api/json-rpc.md)
* [Market Hub API](/k4k3ru-docs/api/market-hub.md)
* [MCP](/k4k3ru-docs/mcp.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://k4k3ru.gitbook.io/k4k3ru-docs/overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.