# Multi-Step Tool-Calling over Korean Open Public APIs: A Benchmark and a Data-Synthesis Recipe

Source: [arXiv](https://arxiv.org/abs/2609.05395v1)  
Feed7 permalink: https://feed7.dev/p/2609-05395v1-0qwa6p2  
Published: 2026-09-04T17:44:52.000Z  
Trust: Needs Review (needs_review)

## Why Included

EDGE synthesizes multi-step tool-call training data by retaining only API links verified through live execution. Its 9B model nearly matched an untuned 27B sibling on Korean public-API tasks.

## Source Summary

KOPA-Bench contains **145 real-world tasks** over Korean open public APIs. **EDGE** maps compatible tool outputs and inputs, verifies those links against live APIs, then traverses the retained graph to generate executable multi-step trajectories.

## Practical Implication

For agent training, derive tool chains from observed API behavior instead of schema compatibility alone. The reported **9B model**, fine-tuned with GRPO, nearly matched the untuned **27B model** from the same family and also improved on BFCL.

## Agent-Ready Context

KOPA-Bench contains **145 real-world tasks** over Korean open public APIs. **EDGE** maps compatible tool outputs and inputs, verifies those links against live APIs, then traverses the retained graph to generate executable multi-step trajectories.

For agent training, derive tool chains from observed API behavior instead of schema compatibility alone. The reported **9B model**, fine-tuned with GRPO, nearly matched the untuned **27B model** from the same family and also improved on BFCL.

The benchmark centers on Korean government APIs and on-premise open-source deployment. The abstract reports substantial gains but gives no exact KOPA-Bench or BFCL scores, so portability to other API ecosystems remains open.

## Connected Context

Feed7 judgment across 703 accumulated Signals:

This turns multi-step tool training into a graph grounded in observed API compatibility, not schemas alone, and suggests execution-verified trajectories can let a smaller tuned model approach a larger untuned relative. Against the candidates, it reinforces deterministic validation around tool use while narrowing the evidence to Korean public APIs, one model family, and results reported without exact scores or cross-ecosystem portability.

- [Why Off-the-Shelf AI Doesn't Understand Money — Udi Menkes, Intuit](https://feed7.dev/p/why-off-the-shelf-ai-doesn-t-understand-money-udi-menkes-intuit-0y6w9rk) — Both prioritize observed state-action evidence over descriptive context alone: Intuit learns from verified outcomes, while EDGE verifies tool links against live API behavior before generating trajectories.
- [TurnSight: Turn-Level Hindsight Self-Distillation for Tool-Integrated Reasoning](https://feed7.dev/p/2608-04007v1-0gjxuy2) — EDGE supplies executable multi-step trajectories, while TurnSight offers turn-level credit assignment from execution hindsight; together they address data construction and supervision granularity for tool-agent training.
- [Twin: Playing an Unknown Game with a Test-Time Digital Twin](https://feed7.dev/p/2608-14490v1-0d3xjvt) — Twin continuously validates modeled transitions before acting, reinforcing KOPA-Bench’s premise that executable behavior is stronger evidence than nominal schema compatibility, though Twin’s replayable game setting is much narrower.
- [Healthcare’s Agent Bytecode: X12 as the Harness for AI Agents — Vasant Kearney, Onlay](https://feed7.dev/p/healthcare-s-agent-bytecode-x12-as-the-harness-for-ai-agents-vasant-kear-0zwdwwy) — X12 shows how typed contracts constrain cross-system actions, while KOPA-Bench demonstrates that type compatibility still needs validation against live behavior; protocol conformance alone does not establish executable tool chains.

## Context Map

- Layer: agent
- Domains: data
- Topics: tool-use, harness-engineering, open-models

## Uncertainty

- The benchmark centers on Korean government APIs and on-premise open-source deployment. The abstract reports substantial gains but gives no exact KOPA-Bench or BFCL scores, so portability to other API ecosystems remains open.

## Agent Instruction

Use this item as source-backed context. Do not invent claims beyond the linked source. If this item conflicts with another source, call out the conflict.