Korea Public Data

Service overview

What is Korea Public Data?

peaqOS exposes the Korean public data portal through a native adapter — the operator brings their own Data.go.kr portal key and sends it request-scoped as `providerCredentials.dataGoKr.serviceKey`; no Data.go.kr credential is configured inside peaqOS. A paired Machine Agent then orders any of four location reads using the machine’s own coordinates: EV charger availability from the Korea Environment Corporation, the KEPCO station directory, the KMA next-hour precipitation forecast, and PM2.5 from the nearest AirKorea monitor. Data.go.kr itself is South Korea’s official open-data portal, publishing public OpenAPIs from government bodies and state utilities. Each dataset is approved separately on the operator’s key, the portal bills nothing per call beyond its request quota, and peaqOS records the order, execution, outcome, and audit trail.

How it works

1. Step 1

   Get portal access

   Create a Data.go.kr account and apply for each OpenAPI you plan to call — approval is granted per resource on the key.

2. Step 2

   Send scoped credentials

   Pass serviceKey under providerCredentials.dataGoKr when searching, ordering, or executing through peaqOS.

3. Step 3

   Run the read

   Call the operation with the machine’s own coordinates; peaqOS routes the request and stores the run, outcome, and audit trail.

Adapter operations

Behind peaqOS — the machine sends its coordinates, peaqOS calls the matching Data.go.kr gateway with the request-scoped portal key and records the run.

• GETsearch-nearby-ev-chargers

  Find chargers the provider reports idle around the machine within one Korean district; returns them nearest first.

• GETget-next-hour-weather

  Read the KMA ultra-short forecast for the machine’s grid cell; returns next-hour precipitation type, amount, and issue time.

• GETget-nearby-pm25

  Read PM2.5 from the nearest AirKorea monitor; returns the station, value, grade, and availability. Needs deployment enablement.

• GETlist-ev-charging-stations

  List a page of the pinned KEPCO station directory; returns locations and access hours, not live availability.

Integration fields

Wire Korea Public Data into peaqOS

providerKey

data-go-kr

serviceType

data.location

credential path

providerCredentials.dataGoKr.serviceKey

chargers skill

data-go-kr-ev-chargers → search-nearby-ev-chargers

weather skill

data-go-kr-weather → get-next-hour-weather

air-quality skill

data-go-kr-air-quality → get-nearby-pm25

directory skill

data-go-kr-ev-charging-stations → list-ev-charging-stations

required input

latitude, longitude

extra input

regionCode, districtCode (charger search only)

dataset approval

granted per API resource on the portal key

air-quality gate

DATA_GO_KR_AIR_QUALITY_ENABLED=true

payment

not-required in peaqOS; portal request quota applies

FAQ

Questions agents ask about Korea Public Data

• Does it require an API key?+

  Yes — one Data.go.kr portal key, approved separately for each dataset you call. Send it request-scoped as providerCredentials.dataGoKr.serviceKey; peaqOS configures no Data.go.kr credential of its own and keeps the key out of catalog metadata, receipts, logs, and errors.

• Can my robot call all four reads today?+

  Three of them, once the matching dataset is approved on your key: charger status, the station directory, and the weather forecast. Nearby PM2.5 also needs AirKorea production approval and a coordinate-validation step before the deployment operator sets DATA_GO_KR_AIR_QUALITY_ENABLED=true — until then it is listed for discovery and pre-wiring.

• How does payment work?+

  It does not. The portal charges nothing for these reads and peaqOS runs no market payment on this path — the only ceiling is the request quota Data.go.kr sets on your key. peaqOS still records the order, execution, and audit receipt.

• Where does the location come from?+

  The machine. A portal key carries no location, so every request sends the machine’s own WGS84 coordinates — plus the Korean region and district codes for charger search, which the provider requires instead of a radius.

• How deterministic are responses?+

  It depends on the read. The KEPCO station directory is a pinned 2025-12-31 snapshot and returns the same records every time. The weather forecast is stable per KMA issue time and describes a five-kilometre grid cell, not a point sensor. Charger status and PM2.5 change as the provider publishes — an idle charger is the provider’s claim at read time, and a missing, flagged, or over-two-hours-old PM2.5 reading comes back as unavailable rather than as a stale number.

• What happens if a request fails?+

  Data.go.kr result codes are mapped to explicit errors — key rejected or expired, dataset not approved for the key, rate limited, source IP blocked, provider timeout — and returned to the agent, then stored on the failed order run.