API collections
Kevin drafts API requests as collection files you open and fire in your own client. It authors; you send.
you > make me a request to test the activation webhook
you > add the refund calls to my Bruno collection
you > put the checkout flow in Postmanapi-collections writes requests as plain files your API client reads directly, with no export step and no cloud. Bruno and Postman (v12 or later, desktop app) are the shipped adapters. A collection already in the target folder decides which one; otherwise Kevin uses Bruno if it's installed, then Postman. When no client is installed, it writes curl scripts and tells you how to run them.
Where collections live
| Placement | Where | For |
|---|---|---|
| Personal (default) | <HOME>/reports/api/<adapter>/ | Your own experiments, one collection per adapter |
| In a repo | For example <repo>/bruno/, or the repo root for Postman's postman/ folder | Requests shared with a team. Check that repo's .gitignore covers .env before any secret lands |
Kevin always tells you the resolved path, so you can redirect it.
Secrets and sending
Secrets are referenced as placeholders, never written into a request file. Bruno and curl read them from the collection's .env; Postman reads {{vault:KEY}} references from your local Postman Vault, and nothing is pushed to Postman Cloud. Kevin authors and never sends. To check a draft (does it return 201? why the 4xx?), it can fire it once through the curl_run tool, which loads a .env, fills the placeholders, and scrubs every secret out of what comes back.
The skill is part of the API pack; activate it through configure-skills. See Skills.