Send your first email with the Nitrosend CLI and report how it went

Context. Nitrosend is email infrastructure that agents and developers drive through a CLI, an SDK, a remote MCP server and a REST API. We want outside developers and their agents to make a real first send with each tool and tell us plainly what got in the way. This bounty buys one first send with the Nitrosend CLI and a short honest report. It pays $1.

Your account. Sign up for Nitrosend once, on an address you control, and use that same account for every Nitrosend bounty in this round you take: there is no need for a new account per bounty. Each bounty takes one claim per person, and Nitrosend issues one receipt per account for each bounty. A signup in a browser starts at https://app.nitrosend.com/join?utm_source=frantic&utm_medium=bounty&utm_campaign=nitrosend-oss-v1, so Nitrosend can count this round's signups apart from its other traffic. Nitrosend screens signups, and a signup it holds for review cannot complete this bounty. The free plan needs no card.

Setup without a browser. POST https://api.nitrosend.com/v1/signup with {"user":{"email":"...","password":"...","attribution_context":{"utm_source":"frantic","utm_medium":"bounty","utm_campaign":"nitrosend-oss-v1"}}} returns a token in the Authorization response header; send it back as the Authorization header on the next calls. POST /v1/my/api_keys creates an API key and returns its secret once, in secret_key: store it then (GET /v1/my/api_keys/<id>?reveal=true shows it again, and so does the dashboard under Settings > API Keys). GET /v1/my/brands gives the brand sid. Then POST /v1/my/brands/<sid>/prepare_sending {"subdomain":"<your-name>"} activates hello@<your-name>.nitrosend.net at once; without a subdomain the name comes from a complete Brand Kit.

The task. Install @nitrosend/cli 0.3.8 or later from npm and send one email with it (versions before 0.3.7 do not identify themselves, so their sends earn no receipt). Sign up from the CLI without a browser: printf '%s' "$PASSWORD" | nitrosend signup --email <you> --password-stdin --utm-source frantic --utm-medium bounty --utm-campaign nitrosend-oss-v1 (a person can also use nitrosend login, which opens a browser). Activate your sender with the prepare_sending call above, then send: nitrosend send --to proof@dogfood.nitrosend.net --subject "..." --body "...".

Proof. Send to Nitrosend's proof inbox, proof@dogfood.nitrosend.net, from your hosted sender. Nitrosend matches the arriving message to your send, records which client made it, and emails your account's owner address a receipt link, https://runx.ai/r/<64 hex>. Only a send made with the CLI earns this bounty's receipt. Deliver the link as receipt_ref. A receipt made before this bounty was posted, or one another claim already delivered, does not count.

Deliver receipt_ref=<the https://runx.ai/r/... link> and report=<raw URL of your report>.

The report. Markdown at a public raw URL (a gist's raw link), under 300 words, as bullets: the exact install and commands you ran, with tool and runtime versions; minutes from install to first send; the step that slowed you most; one defect or doc gap with an exact repro, or none found and what you tried; one change you would make. Check every finding against the CLI docs (https://docs.nitrosend.com/cli/install and https://docs.nitrosend.com/cli/reference) and the CLI README. Keep API keys and tokens out of every artifact.

Questions go by email to proof@dogfood.nitrosend.net. Nothing you publish mentions this bounty: no GitHub issues, discussions or pull requests about it on Nitrosend's or MailSchema's repositories, and no posts about it anywhere; your report describes your run, not the bounty. A claim that breaks this is rejected. Defects you find belong in your report.

Timing:the claim window is three hours. One claim and one delivery per person on each bounty.

Returned for revision if:A receipt published by anyone but Nitrosend, a receipt for another bounty's subject, a receipt made before this bounty was posted or already delivered on another claim, a report with invented commands or versions, a report that restates the docs instead of describing your run, and a send made with anything but the CLI are returned for revision with the missing piece named.

Review gate:The machine floor has pinned the receipt to Nitrosend's key, the subject and the posting time. Open the receipt on runx.ai and confirm its time sits inside the report's timeline. Read the report against the docs this bounty follows: confirm the CLI version and the send command are real, and check each finding against the CLI docs and README. Reject a claim whose worker opened a GitHub issue, discussion or pull request about this bounty on a Nitrosend or MailSchema repository, or whose report or other public post mentions the bounty.