unified-broker-api

Integrate KIS, Kiwoom, and Alpaca broker APIs into a unified interface.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/sihu-dev/forge-labs --skill unified-broker-api
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unified-broker-api
Source: https://github.com/sihu-dev/forge-labs/tree/main/apps/hephaitos/.claude/skills/unified-broker-api
Command: npx skills add https://github.com/sihu-dev/forge-labs --skill unified-broker-api

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill demonstrates a unified interface to interact with multiple brokers (KIS, Kiwoom, Alpaca) through a single abstract API, simplifying integration.

Core Features & Use Cases

  • Unified Interface: Connect, query balance, holdings, and place orders across brokers.
  • Adapter Pattern: Separate broker-specific implementations behind a common API.
  • Use Case: Build a UI that can switch between brokers without changing business logic.

Quick Start

Instantiate a broker via BrokerFactory and call connect(...) to begin trading operations.

Frequently Asked Questions about unified-broker-api

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I integrate multiple broker APIs into a single interface?

A unified broker API consolidates multiple broker connections (KIS, Kiwoom, Alpaca) behind one abstract interface. This eliminates duplicate logic by routing connect, balance, holdings, orders, and trading operations through a common API instead of managing separate broker SDKs.

Can I switch between different brokers without changing my trading logic?

Yes. The adapter pattern separates broker-specific implementations from your business logic. Instantiate different broker adapters through a factory, and your code remains unchanged—only the underlying broker connection swaps.

What operations does a unified broker interface support?

A unified broker interface supports connect/disconnect, query balance and holdings, retrieve open orders, place buy and sell orders, cancel orders, and subscribe to real-time price updates across multiple brokers simultaneously.

How do I handle real-time price subscriptions across brokers?

The unified interface exposes subscribePrice and unsubscribe methods that normalize real-time price feeds from each broker. Your subscription code works identically regardless of which broker adapter is active.

What's the best way to manage broker-specific implementation differences?

Use the adapter pattern with a factory. Each broker adapter implements the unified interface, encapsulating protocol differences. The factory instantiates the correct adapter based on your broker selection, hiding complexity from client code.

Do I need to rewrite my application to support multiple brokers?

No. Design your application against the unified interface from the start. Switching brokers requires only changing which adapter the factory returns; your trading and data-access logic stays intact.