Overview
Kiterunner is an API discovery tool designed to identify routes and endpoints that conventional web content lists may miss. Use it in a controlled environment with explicit authorization, conservative request rates and an approved target list.
Key features
API-focused route discovery; route wordlists; CLI workflow; useful alongside proxy-based manual testing.
Install & first run
# Prebuilt binary from the releases page
# https://github.com/assetnote/kiterunner/releases
# The archive already contains the wordlists/ directory
tar -xzf kiterunner_*_linux_amd64.tar.gz
sudo mv kr /usr/local/bin/
# Or build from source
git clone https://github.com/assetnote/kiterunner.git
cd kiterunner && make build && sudo cp dist/kr /usr/local/bin/
# API route brute force with the bundled kite wordlist
kr scan https://lab.example.com -w routes.kite -x 20 -j 100
kr brute does plain directory brute forcing; kr scan matches wordlist routes against real API endpoints. Docs: https://github.com/assetnote/kiterunner
Real-world example
Test an owned staging API to find undocumented routes, then verify access controls manually using test accounts.
Common questions
Does discovering a route confirm an API vulnerability?
No. It identifies endpoints to inspect for authentication, authorization and input-validation issues.
Why not just ffuf?
Kiterunner matches full REST route shapes (path plus method plus expected response size), so it finds API endpoints that word-for-word directory brute force misses.
Do I need Assetnote wordlists?
The release bundles routes.kite, which is enough to start. The Assetnote API wordlists add coverage if you register for them.
What do the flags mean?
-x is concurrency, -j is the number of requests per second to hold back, and --ignore-length drops the wildcard response size.
Related tools
Schemathesis
Property-based fuzzing for OpenAPI, Swagger and GraphQL APIs: it generates hostile inputs from your own spec. Free, Python CLI.
Keep exploring: browse every assessment phase in the Pentest Hub.
Authorized testing only — only ever test systems you own or have explicit written permission to assess.
