# api-docs-wasp-drone

The api-docs-wasp-drone subagent helps choose an API docs renderer, add OpenAPI examples, and prepare hosting or SDK generation. It supports Claude Code and Codex.

- subagent · `type=agent` · Claude Code, Codex, Cursor · ★ 96 repo stars
- Author: Legion Code Inc.
- License: AGPL-3.0-or-later · policy=link-only · description only; the file stays with the author
- Source: https://github.com/legioncodeinc/vibe-coding-tools/tree/HEAD/plugins/documentation-tools/agents/api-docs-wasp-drone.md
- Updated: 2026-10-18
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/agents/api-docs-wasp-drone

## What it does

api-docs-wasp-drone handles the API reference layer from an OpenAPI spec through publication. It compares Swagger UI, Redoc, Scalar, Mintlify, Stoplight, and Bump.sh, adds JSON request and response examples, and prepares hosted or self-hosted delivery through GitHub Pages, Netlify, Vercel, or Docker.

It also covers SDK generation for TypeScript, Python, and Go, plus changelog work for API changes with `[BREAKING]` markers. Claude Code installs it through the plugin marketplace; Codex uses `.codex/agents/api-docs-wasp-drone.toml`.

The workflow starts with the spec. Validation errors stop rendering, while a missing spec makes the subagent ask for a file path, URL, or API description. Check that input before choosing a renderer.

## Requirements
- Works with: GitHub, Docker

## Install

### Claude Code (native platform)

1. **Plugin marketplace**
In the agent chat (not a shell):
```text
/plugin marketplace add legioncodeinc/vibe-coding-tools
```
In the agent chat (not a shell):
```text
/plugin install documentation-tools@wasp-nest
```

2. **Manually: put the files in place**
- File: `.claude/agents/api-docs-wasp-drone.md` — For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

### Codex

**Manually: put the files in place**
- File: `.codex/agents/api-docs-wasp-drone.toml` — Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

### Cursor

**Manually: put the files in place**
- File: `.cursor/agents/api-docs-wasp-drone.md` — Cursor also reads .claude/agents/

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/legioncodeinc/vibe-coding-tools/tree/HEAD/plugins/documentation-tools/agents/api-docs-wasp-drone.md

## When to use it
- choose a renderer for an OpenAPI reference
- add JSON request and response examples
- publish API docs through GitHub Pages or Docker
- generate an SDK for TypeScript, Python, or Go
- mark breaking API changes in a changelog

## Example prompts
- Set up API docs for `openapi.yaml` and compare the available renderers.
- Add JSON request and response examples to every endpoint in my OpenAPI spec.
- Generate a TypeScript SDK and prepare a changelog for the API change.

## Similar
- [docker-docs](https://affpapa.org/en/nevibecode/skills/docker-docs.md) — skill · 623 installs
- [neo4j-docker-client-generator](https://affpapa.org/en/nevibecode/agents/neo4j-docker-client-generator.md) — subagent · 183 installs
- [cloudrun-development](https://affpapa.org/en/nevibecode/skills/cloudrun-development.md) — skill · 991 installs
- [api-docs](https://affpapa.org/en/nevibecode/skills/api-docs.md) — skill · 893 installs
- [w-api-docs](https://affpapa.org/en/nevibecode/skills/w-api-docs.md) — skill · 647 installs
- [adding-api-docs](https://affpapa.org/en/nevibecode/skills/adding-api-docs.md) — skill · 455 installs

From the same set: [legioncodeinc/vibe-coding-tools](https://affpapa.org/en/nevibecode/by/legioncodeinc/vibe-coding-tools.md) — 172 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
