Click the demo to open the MP4. The recording comes from a real ummaya terminal session captured with t-rec; waiting time was trimmed, but prompts, UI, tool calls, and answers were not synthesized.

UMMAYA

Unified Multi-Ministry Agent for Your Administration. 읽으면, 엄마야.

UMMAYA is a terminal agent for Korean public-service workflows. You describe the outcome in natural language, and UMMAYA routes the request through four main tools: find, locate, check, and send.

Read the full documentation at ummaya-docs.pages.dev/ko. Start with the Korean user guide if you want the product purpose first, or use llms.txt when an agent needs machine-readable project context.

npm install -g ummaya

Homebrew:

brew install --cask ummaya

Run ummaya, type /login, and paste your FriendliAI API key. Public CLI users should not need to prepare Kakao, JUSO, SGIS, data.go.kr, or other public API keys.

UMMAYA is an academic and R&D project. It is not an official service of Anthropic, LG AI Research, FriendliAI, the Korean government, or any public agency.

First Run

ummaya

Inside the terminal session:

/login

Then ask in everyday language:

동아대 승학캠퍼스에서 친구가 갑자기 아프면 지금 바로 연락할 응급실 어디가 가까워?

UMMAYA stores sessions locally. When a session can be resumed, the terminal prints a command such as ummaya --resume <session-id>.

Why UMMAYA

Korean public services already exist across government portals, public datasets, address systems, emergency channels, weather services, hospital registries, and identity rails. The hard part for a citizen is not whether those systems exist. The hard part is knowing which one to use, in what order, and what to do next.

People do not usually think like this:

Call the emergency medical institution API after resolving my administrative district code.

They think like this:

다대1동 근처에서 지금 전화해볼 수 있는 병원 어디야?

UMMAYA treats that sentence as the interface. The terminal should show the work as it happens: location resolution, public-service lookup, protected-work checks when needed, compact tool results, and a final answer that a person can act on.

What You Can Ask

These are prompts you can type directly into UMMAYA. They are written as user tasks, not as API names.

| Situation | Prompt | |---|---| | Nearby emergency care | 동아대 승학캠퍼스에서 친구가 갑자기 아프면 지금 바로 연락할 응급실 어디가 가까워? 찾아진 곳만 이름, 주소, 전화번호로 정리해줘. | | Local clinic lookup | 다대1동 근처에서 오늘 전화해볼 수 있는 내과가 있을까? 가까운 곳 위주로 주소랑 전화번호를 알려줘. | | Weather for a walk | 퇴근하고 다대포해수욕장 걸어가도 괜찮을까? 지금 비 오는지랑 체감상 추운지만 알려줘. | | Weather plus road risk | 비 오는 날 다대포에서 김해공항까지 차로 가야 해. 날씨랑 도로 위험 정보를 같이 보고 조심할 점을 알려줘. | | Moving checklist | 이사했어. 전입신고하고 자동차, 건강보험, 학교 관련 주소는 어떤 순서로 확인해야 하는지 알려줘. | | Permissioned workflow | 복지 지원을 신청할 수 있는지 확인하고, 신청 전에 필요한 정보와 공식 경로를 정리해줘. |

Live public-information flows are shown most often in the demo because they can be verified through public APIs. Identity, submission, payment, and correction flows are permissioned; UMMAYA treats them as checked or handed-off workflows instead of pretending to complete protected government actions without official authority.

Main Tools

UMMAYA keeps the model-facing surface small. Instead of exposing dozens of agency-specific APIs directly to the LLM, it gives the agent four durable primitives and lets adapters handle ministry-specific details behind them.

locate

locate turns places, addresses, coordinates, and administrative areas into usable location context. A prompt like "동아대 승학캠퍼스 근처" may need coordinates, district names, and region codes before any public-service lookup can make sense.

Typical use:

동아대학교 승학캠퍼스 근처에서 지금 갈 수 있는 응급실을 알려줘.

The terminal should show location work as its own step, not hide it inside the final answer.

find

find retrieves public information. This is the live-heavy path: weather, emergency rooms, hospitals, road safety, welfare information, and other public-service reads.

Typical use:

다대포에서 김해공항까지 가야 하는데 비랑 도로 위험 정보를 같이 보고 판단해줘.

UMMAYA should only answer from results it actually found. If a live lookup returns one local hospital, the answer should not invent two more from another city.

check

check handles identity, eligibility, and confirmation steps. These workflows can involve personal information, stronger authentication, or legal ordering. The public package uses mock-backed or permissioned checks where official access is not available.

Typical use:

내가 받을 수 있는 복지 지원이 있는지 확인하려면 어떤 정보가 필요해?

The role of check is to make the boundary explicit before UMMAYA moves toward a protected action.

send

send prepares submission, payment, application, receipt, or official handoff flows. It does not claim that a protected civil-service action was completed unless there is a legitimate channel for doing so.

Typical use:

신청 전에 필요한 정보와 제출 경로를 정리하고, 내가 확인해야 할 항목을 체크리스트로 만들어줘.

For now, send is where UMMAYA demonstrates how a terminal agent should stop, summarize, and hand off when the next step requires official identity or submission authority.

Permissioned Work

UMMAYA separates public information from protected action.

| Work type | UMMAYA behavior | |---|---| | Public lookup | Use live public adapters when available. | | Location resolution | Use live geocoding/address/region adapters when available. | | Identity, eligibility, certificates, payment, submission | Ask for the needed boundary, simulate with documented mock flows, or hand off to an official path. | | API failure, zero result, missing authority | Stop clearly instead of inventing a result. |

This is not a separate safety pitch. It is part of how check and send work.

Model And License

UMMAYA currently uses LGAI-EXAONE/K-EXAONE-236B-A23B through FriendliAI Serverless for LLM responses.

• Model: K-EXAONE-236B-A23B
• Thinking channel: UMMAYA_K_EXAONE_THINKING default false; set it to true only for reasoning-channel diagnostics or benchmark runs.
• Model license: K-EXAONE AI Model License Agreement
• Project license: Apache License 2.0

The model license and the UMMAYA source-code license are separate. UMMAYA does not grant rights to LG AI Research, FriendliAI, Hugging Face, Korean government, or public-agency assets.