api-load-tester

# API Load Tester Stress-test HTTP endpoints under increasing load, identify breaking points, and produce a report with actionable recommendations. ## Contents - `references/tool-commands.md` -- tool invocations (hey/wrk/ab/curl), default concurrency stages, per-stage data to capture. - `references/metrics-interpretation.md` -- latency, throughput, error, breaking-point, and bottleneck classification. - `references/output-template.md` -- exact structure for `api-load-report.md`, including ASCII charts and scaling table. - `references/rules-and-examples.md` -- safety rules, error handling, and example invocations. ## Inputs Collect from the user. Ask before proceeding if a required input is missing. **Required**: endpoint URL(s) (with method, headers, body as needed); expected latency thresholds. Default thresholds if unspecified: p50 < 100ms, p95 < 300ms, p99 < 1000ms. **Optional**: concurrent users or range (default ramp 1 to 100); authentication; request payloads; custom headers; test duration (default 10s per stage); ramp pattern (default step ramp, doubling each stage); success criteria (default 2xx); known rate limits; environment label (prod/staging/dev). ## Workflow Follow these steps in order. 1. **Select a tool.** Check in priority order: `which hey`, `which wrk`, `which ab`, `which curl`. If none of hey/wrk/ab exist, install hey (`brew install hey` on macOS, `go install github.com/rakyll/hey@latest` on Linux with Go) or fall back to curl with bash backgrou...