Editorial policy
Who writes Rasket's guides, how every fact is checked against the API and the docs, how posts are dated, and how to ask for a correction.
Who writes
Every guide, reference page and post on this site is written by the engineers who build Rasket, and published under one byline: the Rasket team. There is no ghostwritten persona and no contributed post.
AI tools may help draft or edit a piece. An engineer checks every fact in it before it is published, and the byline does not change because of it — the team is answerable for what is here either way.
How facts are checked
A claim about Rasket is checked against three things that cannot all be wrong at once: the API's own OpenAPI document, the documentation, and the running product. Where they disagree, nothing is published until they do not.
A claim about anyone else comes from their own public pricing or documentation pages, and we record the URL and the date we read it. We do not quote a figure we cannot point at, and we do not compare against a plan we have not read.
A claim about a standard is cited to the RFC that defines it, not to somebody's summary of one.
Dating
Every post carries the date it was published and the date it was last updated. A material change — a corrected fact, a changed limit, a rewritten section — moves the updated date. A typo does not, because a date that moves for nothing tells a reader nothing.
Corrections
If something here is wrong, write to info@rasket.com — the mailbox the contact page lists — and quote the URL. We fix what is wrong in the next posting cycle and note the correction on the post itself, rather than editing it away silently.
Try it for yourself
The product the writing is about: create a key, verify a domain, and send.