<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
        xmlns:news="http://www.google.com/schemas/sitemap-news/0.9">
  <url>
    <loc>https://samtaelabs.com/blog/ai-agent-era-it-agency-real-bottleneck</loc>
    <news:news>
      <news:publication>
        <news:name>삼태연구소</news:name>
        <news:language>ko</news:language>
      </news:publication>
      <news:publication_date>2026-05-08T03:00:28.132Z</news:publication_date>
      <news:title>AI 에이전트 시대, IT 에이전시의 진짜 병목은 코드가 아니다</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://samtaelabs.com/blog/ai-agent-harness-engineering-guide-for-dev-agency</loc>
    <news:news>
      <news:publication>
        <news:name>삼태연구소</news:name>
        <news:language>ko</news:language>
      </news:publication>
      <news:publication_date>2026-05-07T22:30:03.114Z</news:publication_date>
      <news:title>AI 에이전트에게 &quot;부탁&quot;을 그만둬야 하는 이유 — 하네스 엔지니어링 실전 가이드</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://samtaelabs.com/blog/google-cloud-fraud-defense-recaptcha-evolution-ai-agent</loc>
    <news:news>
      <news:publication>
        <news:name>삼태연구소</news:name>
        <news:language>ko</news:language>
      </news:publication>
      <news:publication_date>2026-05-07T12:30:36.141Z</news:publication_date>
      <news:title>reCAPTCHA가 &apos;Google Cloud Fraud Defense&apos;로 진화한다 — AI 에이전트 시대의 사기 탐지</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://samtaelabs.com/blog/google-cloud-fraud-defense-next-evolution-of-recaptcha</loc>
    <news:news>
      <news:publication>
        <news:name>삼태연구소</news:name>
        <news:language>ko</news:language>
      </news:publication>
      <news:publication_date>2026-05-07T12:30:36.101Z</news:publication_date>
      <news:title>reCAPTCHA의 다음 단계, Google Cloud Fraud Defense: AI 에이전트 시대의 보안 플랫폼</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://samtaelabs.com/blog/ai-agent-era-it-agency-honest-talk</loc>
    <news:news>
      <news:publication>
        <news:name>삼태연구소</news:name>
        <news:language>ko</news:language>
      </news:publication>
      <news:publication_date>2026-05-07T12:30:36.041Z</news:publication_date>
      <news:title>AI 에이전트 시대, IT 에이전시가 클라이언트에게 솔직하게 말해야 할 것들</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://samtaelabs.com/blog/ai-coding-agent-dev-agency-reality</loc>
    <news:news>
      <news:publication>
        <news:name>삼태연구소</news:name>
        <news:language>ko</news:language>
      </news:publication>
      <news:publication_date>2026-05-07T12:30:35.981Z</news:publication_date>
      <news:title>AI 코딩 에이전트가 외주 개발 품질을 높여줄까? 에이전시가 직면한 현실</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://samtaelabs.com/blog/ai-agent-harness-engineering-for-dev-agency</loc>
    <news:news>
      <news:publication>
        <news:name>삼태연구소</news:name>
        <news:language>ko</news:language>
      </news:publication>
      <news:publication_date>2026-05-07T03:00:27.910Z</news:publication_date>
      <news:title>AI 에이전트 외주 개발, 프롬프트 말고 시스템으로 통제해야 한다</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://samtaelabs.com/blog/ai-agent-vision-vs-api-cost-comparison-it-agency</loc>
    <news:news>
      <news:publication>
        <news:name>삼태연구소</news:name>
        <news:language>ko</news:language>
      </news:publication>
      <news:publication_date>2026-05-06T22:30:02.885Z</news:publication_date>
      <news:title>AI 에이전트 개발, Vision 방식 vs API 방식: IT 에이전시가 알아야 할 비용의 진실</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://samtaelabs.com/blog/vision-agent-vs-api-agent-ai-automation-cost</loc>
    <news:news>
      <news:publication>
        <news:name>삼태연구소</news:name>
        <news:language>ko</news:language>
      </news:publication>
      <news:publication_date>2026-05-06T12:30:36.049Z</news:publication_date>
      <news:title>비전 에이전트 vs API 에이전트: AI 자동화 비용, 어떤 방식이 맞는가</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://samtaelabs.com/blog/ai-agent-failure-is-a-process-problem</loc>
    <news:news>
      <news:publication>
        <news:name>삼태연구소</news:name>
        <news:language>ko</news:language>
      </news:publication>
      <news:publication_date>2026-05-06T12:30:35.989Z</news:publication_date>
      <news:title>AI가 망한 게 아니라, 프로세스가 없었던 것이다</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://samtaelabs.com/blog/llm-writing-distortion-it-agency-perspective</loc>
    <news:news>
      <news:publication>
        <news:name>삼태연구소</news:name>
        <news:language>ko</news:language>
      </news:publication>
      <news:publication_date>2026-05-06T12:30:35.959Z</news:publication_date>
      <news:title>AI가 내 글을 고쳐준다고? 사실은 &apos;다른 글&apos;로 바꾸고 있다</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://samtaelabs.com/blog/ai-agent-vision-vs-api-cost-comparison</loc>
    <news:news>
      <news:publication>
        <news:name>삼태연구소</news:name>
        <news:language>ko</news:language>
      </news:publication>
      <news:publication_date>2026-05-06T12:30:35.889Z</news:publication_date>
      <news:title>AI 에이전트에게 화면을 보여줄 것인가, API를 줄 것인가 — 비용이 45배 차이 난다</news:title>
    </news:news>
  </url>
</urlset>