# Korea Reserve Prices (복수예비가격) — All 15, and Which Were Drawn (`atomo-studio/korea-g2b-reserve-prices`) Actor

The 15 candidate reserve prices behind every Korean government tender, with the draw flag and the resulting predetermined price. From the Public Procurement Service (조달청). No Korean API key needed.

- **URL**: https://apify.com/atomo-studio/korea-g2b-reserve-prices.md
- **Developed by:** [Atomo Studio](https://apify.com/atomo-studio) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 80.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 reserve prices

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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Korea Reserve Prices (복수예비가격) — All 15, and Which Were Drawn

Korean public tenders do not name a price and take the lowest bid. They do this:

```
base price published
   → 15 candidate reserve prices generated within a band around it
   → 4 drawn at random when bids are opened, averaged
   → that average is the predetermined price
   → the lower-limit rate applied to it sets the award threshold
```

Every one of those 15 candidates is public after opening — along with **which four
were drawn**. This Actor returns them, one record per candidate, in English.

About **10,000 candidate prices are generated a day**, and the draw rate comes out
at ~24-27% exactly as 4-of-15 predicts.

```
 #1     52,758,900 KRW    98.892% of base
 #1  3,126,493,300 KRW   101.494% of base   ★ drawn
 #2     52,333,200 KRW    98.094% of base
 #2  3,036,327,900 KRW    98.567% of base   ★ drawn
 #3     52,945,100 KRW    99.241% of base
```

This is the only public route to the actual distribution of reserve prices and the
draw outcomes. If you are modelling what the predetermined price is likely to be on
a comparable tender, this is the raw material.

### What you get

| Group | Fields |
|---|---|
| **The candidate** | `reserve_price_seq` (1-15), `reserve_price_total`, `base_predetermined_price_krw`, **`reserve_vs_base_pct`** (computed) |
| **The draw** | `was_drawn` (boolean), `draw_no` |
| **The outcome** | `predetermined_price_krw`, `predetermined_net_construction_cost_krw` |
| **The anchor** | `base_price_krw`, `base_price_step_no` |
| **Timing** | `reserve_prices_created_at`, `opened_at`, `registered_at` |
| **Link back** | `notice_no`, `notice_seq`, `rebid_no`, `title_ko`, `category`, `url` |

`reserve_vs_base_pct` is computed here — the upstream API gives amounts only, and
the percentage is what you actually want when comparing across tenders of different
sizes.

### Input

Every field is optional. The default is the last 7 days across all four categories.

| Field | Type | Notes |
|---|---|---|
| `startDate` / `endDate` | date | `YYYY-MM-DD`, Korea time |
| `categories` | array | `goods`, `construction`, `service`, `foreign` |
| `keywords` | array | Match on notice title or agency. Korean or English |
| **`drawnOnly`** | boolean | Return only the 4 drawn candidates instead of all 15 |
| `minBasePriceKrw` | integer | Skip tenders below this base price |
| `maxItems` | integer | Stop after N records. Each tender is ~15 records |

`drawnOnly` is the fast path if you are studying **where in the band the draw
lands** rather than the full distribution.

### Who this is for

- **Bidders** modelling the predetermined price before submitting
- **Quantitative analysts** studying the draw distribution across thousands of tenders
- **Bid-support tools** that need the full band, not just the summary
- **AI agents** reasoning about Korean procurement pricing

Join on `notice_no` with **Korea Public Tenders (나라장터)** for the notice,
**Korea Tender Base Prices (기초금액)** for the published band, and
**Korea Tender Award Results (낙찰정보)** for how it actually ended.

### Notes

**Source.** [조달청 나라장터 낙찰정보서비스](https://www.data.go.kr/data/15129397/openapi.do),
published on Korea's national open-data portal under an unrestricted licence
(이용허락범위 제한 없음). Every record carries a `source` field and a `url` back to
the original notice.

**This is an API client, not a scraper.** Data comes from the government's own REST
API with a registered key, so nothing breaks when g2b.go.kr is redesigned.

**No personal data.** Contact details are stripped from free-text fields and are
never emitted.

***

### Development

```bash
export G2B_SERVICE_KEY='...'   # data.go.kr 인증키 (다른 Actor와 같은 키)
python3 probe.py               # 오퍼레이션·필드명 대조
apify push                     # 배포
```

# Actor input Schema

## `startDate` (type: `string`):

Earliest reserve-price creation date, YYYY-MM-DD (Korea time). Defaults to 7 days ago.

## `endDate` (type: `string`):

Latest reserve-price creation date, YYYY-MM-DD (Korea time). Defaults to today.

## `categories` (type: `array`):

Which kinds of tender to include. All four by default.

## `keywords` (type: `array`):

Keep only records whose notice title or agency matches one of these. Korean or English.

## `maxItems` (type: `integer`):

Stop after this many records, spread evenly across categories. Each tender produces about 15 records, and Korea generates roughly 10,000 a day. 0 = no limit.

## `drawnOnly` (type: `boolean`):

Return just the 4 candidates that were actually drawn, instead of all 15. Useful for studying which part of the band gets picked.

## `minBasePriceKrw` (type: `integer`):

Skip records whose tender base price is below this. 0 = no filter.

## Actor input object example

```json
{
  "categories": [
    "goods",
    "construction",
    "service",
    "foreign"
  ],
  "keywords": [],
  "maxItems": 300,
  "drawnOnly": false,
  "minBasePriceKrw": 0
}
```

# Actor output Schema

## `reservePrices` (type: `string`):

One record per candidate reserve price - amount, sequence, draw flag, resulting predetermined price.

## `downloadCsv` (type: `string`):

The same records as a spreadsheet.

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("atomo-studio/korea-g2b-reserve-prices").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("atomo-studio/korea-g2b-reserve-prices").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 '{}' |
apify call atomo-studio/korea-g2b-reserve-prices --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,atomo-studio/korea-g2b-reserve-prices"
        }
    }
}

```

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/KDmjSHcrcXraDzqgI/builds/orYI0H6ptljfMqpAN/openapi.json