vibing agents

Vibing Agents developer resources

Vibing Agents developer resources

Machine-readable endpoints for the Vibing Agents catalog: OpenAPI, llms.txt, Accept markdown, JSON catalog, and a live Streamable HTTP MCP at https://agents.dancingteeth.net/mcp. No API keys.

What you can call

Vibing Agents is a public editorial catalog, not a paid API product. There are no API keys, webhooks, or sandboxes. Agents should read /llms.txt, the OpenAPI document at /openapi.json, and tool pages at /tools/<slug>. The same URLs speak text/markdown when the request sends Accept: text/markdown (see acceptmarkdown.com). JSON errors use { error: { code, message, hint } }.

Predictable URLs

OpenAPI: https://agents.dancingteeth.net/openapi.json. Agent index: https://agents.dancingteeth.net/llms.txt. Catalog JSON: https://agents.dancingteeth.net/api/catalog. One tool: https://agents.dancingteeth.net/api/catalog/{slug}. Streamable HTTP MCP (JSON-RPC 2.0, protocol 2025-03-26): POST https://agents.dancingteeth.net/mcp — initialize, tools/list, and tools/call for list_catalog_tools and get_catalog_tool. MCP handshake: https://agents.dancingteeth.net/.well-known/mcp. Sitemap: https://agents.dancingteeth.net/sitemap.xml. On-site chat (unofficial, no SLA): POST https://agents.dancingteeth.net/api/chat.

When to use this vs the HTML catalog

Use the JSON catalog and OpenAPI when you need structured slugs, types, and canonical tool URLs. Use HTML or markdown pages when you need pros/cons prose. Do not scrape the visual catalog UI. Do not treat chat as a stable programming interface. The Streamable HTTP MCP at https://agents.dancingteeth.net/mcp mirrors the catalog JSON over JSON-RPC for hosts like Claude "Add MCP"; the well-known document points there and keeps OpenAPI and llms.txt as discovery resources.

Quick links