Add: static-service-manifest-for-agents

[Robocular]

Summary

Adds a new pattern: Static Service Manifest for Agents — the practice of serving convention-based, machine-readable files (llms.txt, agent.json) at well-known URLs so agents can discover API platform capabilities before runtime tool selection.

This is analogous to how robots.txt tells crawlers what they can access, but inverted: manifests tell agents what services are available.

• Category: Tool Use & Environment
• Status: Emerging
• Relationship to existing patterns: Complements Progressive Tool Discovery (static manifests provide the initial catalog; progressive discovery handles runtime detail-loading) and LLM-Friendly API Design (manifests describe the interface; LLM-friendly design governs endpoint behavior).

Why this is a pattern (not a product)

The write-up defines a generalized Problem, Solution, and Trade-offs around convention-based service manifests. References include the llmstxt.org community spec, OpenAI's ai-plugin.json manifest, Anthropic MCP, and RFC 9309 (robots.txt). One production implementation (Agent Gateway) is listed as a known implementation in the References section.

Review checklist

• This is about a reusable pattern, not a launch post
• Problem, Solution, and Trade-offs are present and specific
• No marketing/CTA language in body or references section
• Source links are public and verifiable
• Contributor-owned project reference (Agent Gateway) is disclosed and framed as an example only

---

Continue Tasks: ❌ 1 failed · 🔄 2 running — View all

[vercel]

Someone is attempting to deploy a commit to the nkkko's projects Team on Vercel.

A member of the Team first needs to authorize it.