Trace 상세

결정론 trace_id 패턴으로 endpoint 재호출 후 envelope · validator · 근거 표시.

/ask
trace
식별·시나리오·재호출 URL
trace_idhub-navigator-endoscopy-11110
scenario
S1_PREP
endpoint/api/v1/hub/navigator/context
replay: https://hira-data-lbt6j7618-plomus.vercel.app/api/v1/hub/navigator/context?query=%EC%9C%84%EB%82%B4%EC%8B%9C%EA%B2%BD&region_code=11110
envelope (replayed)
basis_date 2026-04-24
OK
2 sources
2 cautions

hira_demo_hub_api

service

libsql_ingestion

libsql
cautions (2)
  • 준비 지원용 참고 정보입니다.
  • 응급 상황에서는 즉시 기관 안내를 확인하세요.
validator (envelope contract)
ok — 모든 envelope 규약 통과
  • ✓has "status"
  • ✓has "trace_id"
  • ✓has "as_of"
  • ✓has "sources"
  • ✓has "cautions"
  • ✓has "data"
  • ✓status is ok|no_match|error
  • ✓sources is non-empty array
  • ✓cautions is array
  • ✓trace_id is string
API 직접 호출
curl 명령 (replay URL)
GET https://hira-data-lbt6j7618-plomus.vercel.app/api/v1/hub/navigator/context?query=%EC%9C%84%EB%82%B4%EC%8B%9C%EA%B2%BD&region_code=11110
curl -sS "https://hira-data-lbt6j7618-plomus.vercel.app/api/v1/hub/navigator/context?query=%EC%9C%84%EB%82%B4%EC%8B%9C%EA%B2%BD&region_code=11110" | jq

동일 trace_id 패턴은 결정론적 — 언제든 같은 결과 재현 가능. KOGL Type 1.

response_json
full envelope