Add agent-friendly section + simplify support page

- New #agents section between Integrate and Sovereign with three cards:
  OpenAPI 3.1 discovery, scoped API keys with bounded roles, stable
  error codes + HMAC-signed webhooks. Links to KEYSAT_AGENT_GUIDE.md.
- Top-nav gains 'Agents' anchor.
- support.html: dropped the placeholder on-chain section (no address
  finalized yet) and the speculative 'what funds go toward' paragraph.
  Now three clean sections: Patron license, Lightning, OpenSats.

index.html

@@ -297,6 +297,10 @@ pre.code .p { color:rgba(245,241,232,0.55); }
 .sov .panel .footnote { font-size:13px; color:var(--ink-500); margin:18px 0 0; line-height:1.55; }
 .sov .panel.dark .footnote { color:rgba(245,241,232,0.6); }
 
+/* ---------- Agent-friendly section ---------- */
+.agent-grid { display:grid; grid-template-columns:repeat(3, 1fr); gap:24px; }
+@media (max-width: 880px) { .agent-grid { grid-template-columns:1fr; } }
+
 /* ---------- Install ---------- */
 .install-grid { display:grid; grid-template-columns:1fr 1fr; gap:24px; }
 .install-card { background:var(--cream-50); border:1px solid var(--border-1); border-radius:14px; padding:28px; }
@@ -517,6 +521,7 @@ footer.site .bottom a { color:rgba(245,241,232,0.6); }
       <a href="#creators">Creators</a>
       <a href="#how">How it works</a>
       <a href="#integrate">Integrate</a>
+      <a href="#agents">Agents</a>
       <a href="#install">Install</a>
       <a href="https://docs.keysat.xyz">Docs</a>
     </nav>
@@ -797,6 +802,36 @@ ok = verifier.<span class="f">verify</span>(license_key_from_user)
   </div>
 </section>
 
+<section class="block tinted" id="agents">
+  <div class="wrap">
+    <div class="section-head">
+      <span class="eyebrow">Agent-friendly</span>
+      <h2>Built so you can hand operations to an AI agent.</h2>
+      <p>Keysat issues, monetizes, and manages licenses through a clean self-service admin UI. It also exposes every operator action through a documented HTTP API with bounded-scope credentials &mdash; so if you'd rather have an agent do the day-to-day work, you can give it the keys safely.</p>
+    </div>
+    <div class="agent-grid">
+      <div class="install-card">
+        <div class="cap">OpenAPI 3.1</div>
+        <h3>Discovery built in</h3>
+        <p><code>GET /v1/openapi.json</code> returns a curated, stable spec. Drop the URL into a Custom GPT, OpenAI Assistant, LangChain, or Claude Code &mdash; the agent learns the endpoints automatically.</p>
+      </div>
+      <div class="install-card">
+        <div class="cap">Scoped API keys</div>
+        <h3>Least-privilege by design</h3>
+        <p>Generate a key, pick a role (read-only, license-issuer, support, or full-admin), hand it to the agent. Revoke in 30 seconds without rotating your master credential. Operator-only actions stay behind the master key.</p>
+      </div>
+      <div class="install-card">
+        <div class="cap">Stable error codes + webhooks</div>
+        <h3>React, don't poll</h3>
+        <p>HMAC-signed event deliveries on every license / invoice / subscription state change. Every error response carries a stable machine-readable code (<code>tier_cap</code>, <code>not_found</code>, <code>license_revoked</code>) so agents branch deterministically.</p>
+      </div>
+    </div>
+    <div style="margin-top:32px; text-align:center">
+      <a class="btn ghost" href="https://github.com/keysat-xyz/keysat/blob/main/KEYSAT_AGENT_GUIDE.md">Agent integration guide &rarr;</a>
+    </div>
+  </div>
+</section>
+
 <section class="block" id="sovereign">
   <div class="wrap">
     <div class="section-head">

support.html

@@ -154,21 +154,12 @@ footer{
     </div>
   </div>
 
-  <h2>3. On-chain Bitcoin</h2>
+  <h2>3. OpenSats</h2>
   <div class="card">
-    <div class="label">For larger contributions</div>
+    <div class="label">Fund Bitcoin FOSS broadly</div>
-    <h3>BTC address</h3>
+    <h3>OpenSats</h3>
-    <p>Best for $50+ contributions where the Lightning channel-balance limit might be a concern.</p>
+    <p>If you&rsquo;d rather fund Bitcoin software development broadly rather than this project specifically, <a href="https://opensats.org" style="color:var(--navy-800); font-weight:500">OpenSats</a> is a 501(c)(3) that grants to dozens of FOSS Bitcoin projects &mdash; including BTCPay, which Keysat depends on.</p>
-    <div class="placeholder-warn" style="margin:14px 0 0">
-      <strong>Coming soon:</strong> on-chain address will be published once finalized. For now, please use Lightning above or the Patron license tier.
-    </div>
   </div>
-
-  <h2>What the funds go toward</h2>
-  <p>Roughly in this order: paying contractors to ship the v0.2 web UI auth hardening, recurring billing primitives, additional language SDKs (Go, Swift, Java, .NET), and the long tail of papercut fixes that operators report. A small slice covers infrastructure &mdash; the marketing site, the docs site, the marketplace registry. We publish quarterly transparency reports of what came in and where it went, signed by the keysat.xyz issuer key.</p>
-
-  <h2>OpenSats</h2>
-  <p>If you&rsquo;d rather fund Bitcoin software development broadly rather than this project specifically, <a href="https://opensats.org" style="color:var(--navy-800); font-weight:500">OpenSats</a> is a 501(c)(3) public charity that grants to dozens of FOSS Bitcoin projects (BTCPay, Fedimint, Cashu, NoStr clients, &hellip;). They take Lightning. Keysat itself relies on BTCPay, which OpenSats supports.</p>
 </div>
 
 <footer>