(See sequence steps.)
Hi {{firstName}},
Your API key: `{{apiKey}}` — treat it like a password.
Try this from your terminal:
```
curl -X POST https://api.{{domain}}/v1/rewrite \
-H "Authorization: Bearer {{apiKey}}" \
-H "Content-Type: application/json" \
-d '{"draft":"Hi there, hope all is well.","kind":"cold-outreach"}'
```
That's hello-world. Full docs: {{docsURL}}.
— {{senderName}}Hi {{firstName}},
Three patterns most developers use the API for. Code samples in each:
1. [Bulk rewrite a CSV of cold emails]({{example1URL}})
2. [Wire score-as-you-type into your in-app editor]({{example2URL}})
3. [Generate subject lines from a CRM deal record]({{example3URL}})
If you're doing something not on this list — reply and I'll add an example.
— {{senderName}}Hi {{firstName}},
Boring but useful:
- Free tier: 50 calls/day, 1 RPS.
- All endpoints rate-limited per workspace, not per key.
- 429s return a `Retry-After` header; respect it.
- Pricing is per generation, not per token. Haiku endpoints cost 0.25 credits, Sonnet endpoints cost 1.
If you're hitting limits and need a real plan, ping me directly — I read this address.
— {{senderName}}Hi {{firstName}},
You've made {{apiCallCount}} API calls in the last two weeks. One question:
What's the endpoint you wish existed?
I'll read every answer. If multiple people ask for the same thing, we'll ship it.
— {{senderName}}Developer welcomes lose the fluff. Show the curl command in email body 1, link to a working tutorial in body 2, talk about rate limits and pricing in body 3, and ask for feedback in body 4. The shortest, most technical welcome sequence — most developers will tell you they prefer it.
Drop your draft into our editor. One anonymous run, no signup required.