# Korea Crypto Exchange Risk Events (Upbit & Bithumb) (`pokt-agent-kr/kr-crypto-risk-events`) Actor

Upbit and Bithumb risk notices as structured English events: trading warning and caution designations, delistings with effective time, deposit and withdrawal suspensions per network, network upgrades and new listings. Schedule it to get only new events.

- **URL**: https://apify.com/pokt-agent-kr/kr-crypto-risk-events.md
- **Developed by:** [Seung-yeop Chun](https://apify.com/pokt-agent-kr) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.00 / 1,000 queries

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Korea Crypto Exchange Risk Events (Upbit & Bithumb)

Korean exchanges flag coins before they delist them or freeze transfers. This Actor turns those notices into structured English events. They come from Upbit and Bithumb notices and market APIs, collected every 10 minutes.

### What you get

| Event type | Meaning |
|---|---|
| `WARNING_SET` / `WARNING_CLEARED` | Trading warning designation (투자유의) set or released |
| `CAUTION_SET` / `CAUTION_CLEARED` | Investment caution flags (price swings, volume spikes, global price gaps) |
| `DELISTING` | Delisting decision, with the effective time |
| `DEPOSIT_SUSPENDED` / `DEPOSIT_RESUMED` | Deposits stopped or resumed, per network |
| `WITHDRAWAL_SUSPENDED` / `WITHDRAWAL_RESUMED` | Withdrawals stopped or resumed, per network |
| `NETWORK_UPGRADE` | Network upgrade or hard fork notice |
| `LISTING` | New listing |

Each row has:

- the exchange, tickers and markets;
- `announced_at` and `effective_at` (UTC);
- an English summary, plus the Korean title;
- a confidence score;
- the source and source URL.

### Modes

- **Risk events feed**: list events by ticker, exchange, type and time. Turn on **Only new events since the last run** and schedule the Actor (for example every 10 minutes or every hour). Each run then outputs only events you have not seen, ready for a webhook, Slack, or your trading bot's blocklist.
- **Current status per ticker**: for each coin, its current state on both exchanges:

  - warning and caution flags;
  - any pending delisting and its date;
  - suspended deposit or withdrawal networks;
  - recent events.

  Check this before you trade a coin or route a transfer to a Korean exchange.

### Example output (events)

```json
{
  "id": "bithumb:...:XAI:WARNING_SET:...",
  "exchange": "bithumb",
  "type": "WARNING_SET",
  "tickers": ["XAI"],
  "announced_at": "2026-10-10T08:00:00Z",
  "effective_at": "2026-10-10T08:00:00Z",
  "summary_en": "Bithumb designated XAI as a trading warning asset",
  "confidence": 0.99,
  "source": "notice",
  "source_url": "https://..."
}
```

### Pricing

Pay per event: **$0.005 per query**.

- A query is one ticker, or the whole feed when no ticker is given.
- Event rows are free.
- Failed upstream calls are not charged.
- A schedule every 10 minutes on the whole feed costs about $21.6 a month. Hourly costs about $3.6.

**Free Apify plan:** at most 10 queries per run.

### Limits and notes

- Events come from public exchange notices and market APIs. They are not investment advice and not a prediction.
- `confidence` below 1 means the event was parsed from notice text rather than a structured API field.
- The same data is also sold per call over x402 (USDC on Base): https://x402.pokt-agent.com/
- Questions or bugs: hello@pokt-agent.com

# Actor input Schema

## `mode` (type: `string`):

events: list risk events (filter by ticker, exchange, type, time). status: current warning, delisting and suspension status for each ticker on Upbit and Bithumb.

## `tickers` (type: `array`):

Coin symbols such as BTC, XRP, ICX. Each ticker is one billed query. Leave empty in events mode to read the whole feed as one query. Required in status mode.

## `exchange` (type: `string`):

Limit events to one exchange.

## `types` (type: `array`):

Leave empty for all types.

## `since` (type: `string`):

Only events announced at or after this time, e.g. 2026-10-01T00:00:00Z.

## `onlyNewSinceLastRun` (type: `boolean`):

For scheduled runs: remember what earlier runs with the same filters returned and output only new events.

## `limit` (type: `integer`):

1 to 500.

## Actor input object example

```json
{
  "mode": "events",
  "tickers": [
    "ICX"
  ],
  "exchange": "all",
  "onlyNewSinceLastRun": false,
  "limit": 100
}
```

# Actor output Schema

## `results` (type: `string`):

One row per risk event (events mode) or per ticker (status mode), with source and times.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "tickers": [
        "ICX"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("pokt-agent-kr/kr-crypto-risk-events").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "tickers": ["ICX"] }

# Run the Actor and wait for it to finish
run = client.actor("pokt-agent-kr/kr-crypto-risk-events").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "tickers": [
    "ICX"
  ]
}' |
apify call pokt-agent-kr/kr-crypto-risk-events --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,pokt-agent-kr/kr-crypto-risk-events"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/JVV7g4YXsyVaWKc78/builds/UbEWd1DJj6FdOHijQ/openapi.json