> what are your thoughts on the best and most helpful ways to onboard to an API-first product? puts on thinking cap Three things that I think you should take

> what are your thoughts on the best and most helpful ways to onboard to an API-first product? puts on thinking cap Three things that I think you should take note of here - Developers want to try your product (I do, Hi!) - Developers don't want to deal with the friction of signing up to try stuff (I don't, sorry) - Free-tier API abuse is a legitimate problem, but there are holistic ways to prevent it If I were you, I'd set up a nerfed version of your API front-and-center for people to test. Be sure to rate-limit it and maybe even add artificial latency to deter people from using it in production. You could invalidate keys after 10 minutes of use or 5 queries (or really anything), and you'd probably start getting a lot of interest. People like frictionless tools, and while paying for a public lite-version of your API might seem stupid, it's really just an investment in good marketing IMO.