<?xml version="1.0" encoding="UTF-8"?>
<!--
  Agent-discovery sitemap — STAGED ONLY, 2026-11-03.
  Nothing here is deployed. Nothing in ~/workspace/deploy/crypt0snews/
  was touched, and nothing in agent-calls-v2/ or the live function was
  touched. This file is a ready-to-deploy companion sitemap, not a
  replacement for sitemap.xml or news-sitemap.xml.

  FINDING (checked 2026-11-03 against the deploy-tree copies on disk;
  sitemap.xml parses, 717 URLs; news-sitemap.xml parses, 6 URLs):
  - sitemap.xml is fresh: homepage lastmod 2026-11-02, Nov 2 articles
    present, only 11 HTML files absent (404, widgets, snippets, and
    pages covered by the root URL or intentionally unlisted).
  - news-sitemap.xml is in-window: 3 Nov 2 + 3 Nov 1 articles, all
    inside the 48-hour news window at check time; no Nov 3 article
    exists yet (articles publish 18:00), so nothing is missing there.
  - GAP: sitemap.xml lists agents.html and api.html, but NONE of the
    machine-readable discovery files an agent actually needs first:
    the x402 discovery document, either OpenAPI contract, or the
    llms files' agent entry points beyond llms.txt/llms-full.txt
    themselves. An agent that only reads the sitemap never learns
    where the paid-call contract lives.

  RESEARCH NOTE (brief, 2026-11-03): sitemaps are a discovery hint,
  not a guarantee; Google ignores priority/changefreq, so accurate
  lastmod is the signal that matters. News sitemaps stay inside 48
  hours and 1,000 URLs. Segmenting by content type is standard
  practice — hence a separate, small agent sitemap rather than
  stuffing JSON discovery files into the main 717-URL file.

  DESIGN: this file lists only static, verified-on-disk discovery
  surfaces. Paid endpoints are deliberately NOT listed here: a
  sitemap entry for a 402-gated URL would mislead crawlers, while
  discovery.json and openapi.json (listed below) already enumerate
  every paid endpoint, its price, and its 402 flow. The sitemap
  points agents at the contract; the contract points at the calls.

  LASTMODS below are the deploy-tree file dates verified 2026-11-03.
  At deploy time, regenerate lastmod from disk rather than trusting
  these staged dates if any file has since changed.

  DEPLOY STEPS (future, on his tap only):
  1. Copy this file to the site root as agent-sitemap.xml.
  2. Add one line to robots.txt: Sitemap: https://crypt0snews.com/agent-sitemap.xml
  3. Do NOT edit sitemap.xml or news-sitemap.xml in this slice.
-->
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://crypt0snews.com/agents.html</loc>
    <lastmod>2026-11-03</lastmod>
  </url>
  <url>
    <loc>https://crypt0snews.com/api.html</loc>
    <lastmod>2026-10-31</lastmod>
  </url>
  <url>
    <loc>https://crypt0snews.com/api/x402/discovery.json</loc>
    <lastmod>2026-10-31</lastmod>
  </url>
  <url>
    <loc>https://crypt0snews.com/api/x402/openapi.json</loc>
    <lastmod>2026-10-31</lastmod>
  </url>
  <url>
    <loc>https://crypt0snews.com/openapi.json</loc>
    <lastmod>2026-09-25</lastmod>
  </url>
  <url>
    <loc>https://crypt0snews.com/.well-known/x402.json</loc>
    <lastmod>2026-11-03</lastmod>
  </url>
  <url>
    <loc>https://crypt0snews.com/llms.txt</loc>
    <lastmod>2026-11-01</lastmod>
  </url>
  <url>
    <loc>https://crypt0snews.com/llms-full.txt</loc>
    <lastmod>2026-11-03</lastmod>
  </url>
</urlset>
