The "kimchi premium" — how much higher a crypto asset trades on Korean exchanges (Upbit, KRW) than its global USD price, as a percent. Computed as (Upbit KRW price / (global USD price × USD/KRW)) − 1. Pass symbol = ticker(s), comma-separated up to 10 (default BTC); supported majors include BTC, ETH, XRP, SOL, DOGE, ADA, TRX and more. Returns per symbol { krwPrice, usdPrice, usdKrw, globalUsdInKrw, premiumPct }. Per-symbol resilient (one unlisted symbol does not fail the rest); unresolved symbols are reported in meta.errors. Live blend of Upbit (KRW price) + CoinGecko (global USD) + ECB/Frankfurter (USD/KRW FX).
/api/crypto/kimchi-premiumPAYMENT-SIGNATURE.The kimchi premium API is a pay-per-call crypto endpoint built for AI agents and autonomous software. The "kimchi premium" — how much higher a crypto asset trades on Korean exchanges (Upbit, KRW) than its global USD price, as a percent.
There is no signup and no API key. An agent (or any HTTP client) hits the endpoint, receives an x402 "402 Payment Required" challenge, signs a sub-cent USDC payment on Base or Solana, and retries — the data comes back on the paid request. That makes it a drop-in kimchi premium data source for an agent tool-use loop, an MCP host, or a backend that needs crypto data on demand without onboarding to yet another vendor portal.
| Name | Type | Description |
|---|---|---|
symbol | Comma-separated ticker symbols, up to 10 (default BTC). E.g. "BTC,ETH,XRP,SOL". |
# 1. Probe with no auth → 402 envelope with PaymentRequirements curl -sS 'https://2s.io/api/crypto/kimchi-premium?symbol=BTC' # 2. Sign + retry with PAYMENT-SIGNATURE: curl -sS 'https://2s.io/api/crypto/kimchi-premium?symbol=BTC' \ -H 'PAYMENT-SIGNATURE: <base64-json-payload>' # Or use the canonical runner (handles probe → sign → retry): # EVM_PRIVATE_KEY=0x... node --env-file=.env.local \ # --experimental-strip-types scripts/x402-pay.ts \ # 'https://2s.io/api/crypto/kimchi-premium?symbol=BTC'
import { TwoS } from '@2sio/sdk'
const client = new TwoS({
privateKey: process.env.EVM_PRIVATE_KEY as `0x${string}`,
})
const result = await client.crypto.kimchiPremium({
"symbol": "BTC"
})
console.log('endpoint:', result.endpoint)
console.log('cost:', result.costUsd, 'USDC')
console.log('tx:', result.settlement?.txHash)
console.log('data:', result.data)import os
from twosio import TwoS
client = TwoS(private_key=os.environ["EVM_PRIVATE_KEY"])
result = client.crypto.kimchi_premium(symbol="BTC")
print("endpoint:", result.endpoint)
print("cost:", result.cost_usd, "USDC")
print("tx:", (result.settlement or {}).get("tx_hash"))
print("data:", result.data)// 1. Add @2sio/mcp to your MCP host config (Claude Desktop example below).
// EVM_PRIVATE_KEY funds x402 payments per call.
// claude_desktop_config.json
{
"mcpServers": {
"2sio": {
"command": "npx",
"args": ["-y", "@2sio/mcp"],
"env": { "EVM_PRIVATE_KEY": "0x..." }
}
}
}
// 2. Once the server is running, agents call this tool via standard MCP:
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "crypto.kimchi-premium",
"arguments": {
"symbol": "BTC"
}
}
}| Field | Type | Description |
|---|---|---|
ok | boolean | one of: true |
items | array | |
total | integer | Total matching rows upstream; null when unknown. |
source | object | |
meta | object |
{
"ok": true,
"items": [
{
"symbol": "example",
"krwPrice": 1,
"usdPrice": 1,
"usdKrw": 1,
"globalUsdInKrw": 1,
"premiumPct": 1
}
],
"total": 1,
"source": {
"provider": "example",
"url": "example",
"license": "example"
},
"meta": {
"usdKrw": 1,
"errors": [
{
"symbol": "example",
"error": "example"
}
],
"asOf": "example"
}
}