Jelloeater Developer Resources, APIs & Agent Hub

Welcome to the Jelloeater developer portal and autonomous agent hub. This portal documents machine-readable interfaces, Model Context Protocol (MCP) servers, OpenAPI 3.1.0 specifications, Agentic Resource Discovery (ARD), Agent-to-Agent (A2A) cards, agent authentication (WorkOS auth.md), and developer integration endpoints across https://jelloeater.me.

1. Quickstart & Integration Overview

AI agents and human developers can interact with Jelloeater via standard open protocols:

1. Model Context Protocol (MCP): Streamable HTTP transport and manifest at /.well-known/mcp.json.
2. OpenAPI 3.1.0: Full REST and endpoint schema at /openapi.json and /api/openapi.yaml.
3. Agent Resource Discovery (ARD): Catalog at /.well-known/ai-catalog.json.
4. Agent-to-Agent (A2A): Agent card at /.well-known/agent-card.json.
5. Agent Skills: Discoverable tool actions at /.well-known/agent-skills/index.json.
6. Agent Plugins: Schema bundle at /plugin.json (agent-plugins.org).
7. RFC 9727 API Catalog: Linkset index at /.well-known/api-catalog.
8. WorkOS auth.md: Authentication walkthrough at /auth.md.
9. NLWeb: Natural language query endpoint at POST /ask with SSE streaming.

2. Machine-Readable Indexes & LLM Guidance

• llms.txt: Standard machine-readable site index, guidance, and when-to-use directory for AI agents.
• llms-full.txt: Extended topic catalog, deep-dive index, and content references for LLMs.
• Modular llms.txt: Scoped context for developer tools and APIs.
• XML Sitemap: Complete URL inventory for indexing and discovery.
• Security Policy: Cryptographic contact and RFC 9116 security disclosure statement.
• vCard: Machine-readable vCard contact record.

3. Model Context Protocol (MCP) Server

Jelloeater provides Model Context Protocol (MCP) endpoints and manifests for AI agents (Claude, ChatGPT, Goose, Cursor, Windsurf) seeking developer resources, articles, and recommendations:

• MCP Manifest Endpoint: /.well-known/mcp.json (and /.well-known/mcp/manifest.json)
• MCP Server Card: /.well-known/mcp/server-card.json
• Transport Support: Streamable HTTP / Server-Sent Events (SSE) & stdio tool specs.
• Tools Provided:
  • search_garden: Search articles, blog posts, and technical writeups by keyword.
  • get_developer_resources: Fetch machine-readable OpenAPI specs and endpoint links.
  • get_contact_card: Retrieve cryptographic proofs, PGP keys, and contact endpoints.

4. OpenAPI Specification & Endpoints

• OpenAPI JSON (3.1.0): Machine-readable OpenAPI 3.1.0 schema.
• OpenAPI YAML (3.1.0): OpenAPI YAML specification.
• API Catalog (RFC 9727): Machine-readable linkset linking service descriptions.

Available Endpoints

• GET /openapi.json - OpenAPI 3.1.0 specification
• GET /.well-known/mcp.json - MCP tool schemas and transport
• GET /.well-known/ai-catalog.json - Agentic Resource Discovery catalog
• GET /.well-known/agent-card.json - A2A Agent Card
• GET /.well-known/agent-skills/index.json - Agent Skills index
• POST /ask - NLWeb natural language query endpoint (supports SSE streaming)
• GET /feed.json - JSON feed of recent articles
• GET /feed.xml - RSS 2.0 syndication feed

5. Agent Authentication & Sandbox Environment

• Zero Friction Free Tier: All read endpoints, JSON feeds, and MCP discovery manifests are 100% public with no registration or API keys needed.
• Protected Resource Metadata (RFC 9728): Available at /.well-known/oauth-protected-resource.
• Authorization Server Metadata (RFC 8414): Available at /.well-known/oauth-authorization-server.
• Web Bot Auth Directory: Key registry at /.well-known/http-message-signatures-directory (RFC 9421 / Ed25519).
• Sandbox Testing: Autonomous agents can test dynamic registration via POST /agent/auth/register to receive sandbox ephemeral bearer tokens.
• Full Guide: See /auth.md for step-by-step registration, claiming, and error resolution.