# Korea Bidder & Competitor Intelligence (KONEPS) (`bahc19/korea-bidder-competitor-intel`) Actor

Per-company bid and contract intelligence from the official KONEPS open-data hub (data.g2b.go.kr). Anonymous access; deduplicated bid records with bidder RRN, amounts, rank, winner flag, disqualification, contract link; descriptive analytics (win rates, competitor overlap, concentration).

- **URL**: https://apify.com/bahc19/korea-bidder-competitor-intel.md
- **Developed by:** [Benjamin](https://apify.com/bahc19) (community)
- **Categories:** Automation, Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.50 / 1,000 enriched bid records

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 Bidder & Competitor Intelligence (KONEPS)

Per-company bid and contract intelligence for the Korean Public Procurement Service
(KONEPS / 조달청) — from the official open-data hub **data.g2b.go.kr** (report
UI-ADOFAA-011R, 입찰공고 기업별 투찰 및 계약내역).

Anonymous access — no API key, no login, no CAPTCHA. Descriptive analytics only;
no winner predictions.

### What you get

One record per bid (deduplicated):

| Field | Meaning |
|---|---|
| `tender_id` | Korean bid notice number (입찰공고번호) |
| `notice_iteration` | Notice iteration (차수) |
| `title` | Tender title (Korean) |
| `buyer` / `buyer_code` | Procuring agency |
| `demand_agency` | Demand agency |
| `bidder` / `bidder_rrn` | Bidding company + business registration number |
| `bid_date` / `bid_amount` / `bid_rate` | Bid date, amount (KRW), rate vs expected price |
| `opening_rank` / `winner_flag` | Opening rank and winner selection |
| `disqualified` / `disqualification_reason` | Disqualification status and reason |
| `contract_id` / `contract_amount_total` | Linked contract id and amounts |
| `estimated_price` / `base_price` / `expected_price` | Tender price references |

Plus per-run analytics (`mode=analysis`): bidder participation, observed win rates,
top competitor pairs, buyer concentration, amount distributions — with period,
observations, source and limitations.

### Example (real data, 2026-07-01..02)

```json
{
  "tender_id": "R26BK01569749",
  "title": "2026년 부산광역시 도로하부 공동탐사용역",
  "buyer": "부산광역시",
  "bidder": "셀파이엔씨(주)",
  "bidder_rrn": "2158609494",
  "bid_amount": 801920000.0,
  "bid_rate": "86.203",
  "opening_rank": "1",
  "winner_flag": true,
  "contract_id": "R26TA02057618",
  "contract_amount_total": 801920000.0
}
```

### Input

| Field | Type | Default | Description |
|---|---|---|---|
| `date_from` / `date_to` | string | last days | Window (YYYY-MM-DD, max 12 months) |
| `winner_only` | boolean | true | Only winner-selected rows |
| `mode` | enum | records | `records` / `analysis` / `all` |
| `max_rows` | number | 500 | Collection cap (page = 50 rows) |

### Pricing (pay-per-event)

Charged per event, platform margin included:

| Event | Price |
|---|---|
| `enriched-record` (one deduplicated bid record) | $0.0005 |
| `analysis` (one analytics set) | $0.05 |

Approximate cost of a records run (plus a few cents of platform compute):

| Records | Cost |
|---|---|
| 100 | ~$0.05 |
| 1,000 | ~$0.50 |
| 10,000 | ~$5.00 |

Run with a small `max_rows` first; a records run with the default (100) costs
about $0.05.

### Limits

- Window capped at 12 months by the source.
- Rows are deduplicated by (tender, iteration, bidder, date, amount); the source
  report repeats rows for multi-item tenders.
- `winner_flag=Y` may differ from the final contract.

# Actor input Schema

## `date_from` (type: `string`):

Start of the window (YYYY-MM-DD). Max 12 months total.

## `date_to` (type: `string`):

End of the window (YYYY-MM-DD).

## `winner_only` (type: `boolean`):

Filter to 낙찰자선정여부=Y (winner-selected) rows.

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

records: bid rows; analysis: descriptive statistics; all: both.

## `max_rows` (type: `integer`):

Collection cap (pages of 50). Default 100 keeps a first run cheap (~$0.05).

## Actor input object example

```json
{
  "date_from": "",
  "date_to": "",
  "winner_only": true,
  "mode": "records",
  "max_rows": 100
}
```

# 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("bahc19/korea-bidder-competitor-intel").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("bahc19/korea-bidder-competitor-intel").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 bahc19/korea-bidder-competitor-intel --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,bahc19/korea-bidder-competitor-intel"
        }
    }
}

```

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/jmolhCyUeMBZ61o0i/builds/9UKaDTek7ihW2EhU7/openapi.json