Send an email with a 30-line Nitrosend SDK script 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 TypeScript SDK 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. Write a TypeScript script of 30 lines or fewer that uses @nitrosend/sdk 0.11.2 or later (earlier versions do not identify themselves, so their sends earn no receipt) to send one email to proof@dogfood.nitrosend.net, and run it. Make the client with new Nitrosend(<key>) and send with ns.messages.send({ channel: "email", to, subject, html }, "<idempotency-key>"); the second argument is a plain string. Read the key from the environment, never from the file. The script must compile under strict mode (tsc --strict); with TypeScript 7, add "types": ["node"] to tsconfig.json. Run it on any runtime (Node, Bun, Deno, an edge runtime) and name the runtime and its version. Publish the script as a .ts file in the gist beside your report.

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 SDK 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>, script=<raw URL of the .ts file> 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 SDK README (github.com/nitrosend/typescript-sdk) and the Nitrosend docs. 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 script over 30 lines, one that does not compile under strict mode, or one that holds a key 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: fetch script, count its lines, compile it with tsc --strict, confirm it is the script the report describes, and check each finding against the SDK 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.