JSS is well-positioned for the agentic / LLM-builder / Nostr-native developer audience, and our active work is increasingly on that track. This issue tracks making the positioning visible across the project.

Existing fit

• JSON-LD canonical storage — LLM-readable, structured, semantically addressable
• Single-key NIP-98 → WebID auth (auth: NIP-98 → WebID via verificationMethod lookup (#399) #400) — agents hold one Nostr key, no per-pod credentials
• Tunnel feature — agent-controlled pods reachable on the public internet without third-party services
• Local-first deployment — Termux PoC today, native APK in development; agents run on user devices
• Schnorr / NIP-98 — non-interactive auth, ideal for headless agents
• Git on Solid — version-controlled state for agent runs (branching / diffing agent histories)
• HTTP 402 + sat payments — agents pay for resources natively
• WebSocket notifications — event streams for agents
• Pure-JS, zero native modules — runs anywhere Node runs, including the runtimes agentic stacks already target

Work

• Audit existing features for agentic relevance; document the patterns explicitly
• Demo: an agent operating its own pod end-to-end with a single Nostr key
• Cross-reference integration patterns with the major agentic stacks (claude-code, LangChain, MCP, etc.)
• Tag relevant issues / PRs with the `agentic` label as a forward-tracking signal
• Optional: dedicated `/docs/agentic/` section in the docs site

Why now

The agentic / Nostr-native / payments-native developer community is JSS's primary recruitment audience, and JSS already ships much of what that audience needs. Making the positioning visible aligns the project's external face with the work that's actually happening inside.