Reviewing Salad's API developer experience

Bill Doerrfeld | August 19, 2024

I recently was hired by Salad to audit the developer experience of their platform. I dug deep into the developer documentation, assessing the onboarding process, testing API calls to see how they function, looking at the error responses, and gauging the overall experience. 


Salad has a really cool offering, and I encourage people to try it out. The platform offers a platform-as-a-service to deploy containerized cloud-based GPUs for training and running machine learning models. It also offers more SaaS-y options for calling pre-trained AI models to perform specific tasks, like audio transcription. You can configure some of this visually, but the entire platform is accessible via a RESTful HTTP API as well.


When I do these audits, I really try to get in the developer's shoes and take a "show me the code" mindset. I spent a few days getting comfortable and toying around with the platform. The project culminated in a 10-page audit and an hour-long consultation with the team. 


My biggest recommendation was to unify the developer experience, as learnability felt fragmented between the developer portal, individual cards for model recipes, tutorial pages, and the core API reference. I also noticed naming inconsistencies, errors, delays in running certain model jobs, a lack of SDKs, and other minor UI issues.


I loved the Salad API reference's playground, which is based on
Mintlify. I also suggested ways to refine the sandbox experience with auto-population for default fields. Some other tips could aid developer experience on Salad, such as including a public OpenAPI file, a public changelog, and stories around developer use cases.


All in all, the platform has a lot of potential, and the team was super friendly and helpful. I look forward to following their journey!


I really enjoy doing these audits (check out the one I did for
Authenticating.com), as it feels very fulfilling to help teams refine their product. Also, I can put all the best practices around API documentation and developer experience that we've been sharing on Nordic APIs for years to good use!

If you are interested in having me audit your API's developer experience, read more information here.

Learn more: API Developer Experience Audit

Other Blog Posts

By Bill Doerrfeld June 10, 2026
I'm working with Zuplo on some new content around their MCP Gateway release. First up: a deep comparison of MCP gateways on the market!
By Bill Doerrfeld June 10, 2026
The constant barrage of AI layoffs is overshadowing the economic reasons behind these cuts, as well as the net-positive talent redistribution happening at large.
By Bill Doerrfeld June 8, 2026
My latest for InfoWorld reviews MCP servers and agent-ready tools for connecting AI agents with popular database styles.
By Bill Doerrfeld May 29, 2026
For my latest DirectorPlus edition, Joel Carusone from NinjaOne shares how engineering leaders can build the muscle for making tough calls.
Close-up of a glowing laptop keyboard in blue light, viewed at an angle with the screen above
By Bill Doerrfeld May 25, 2026
My latest InfoWorld feature explores how Model Context Protocol (MCP) supports context engineering for AI-assisted coding.
A set of metal keys on a keyring resting on a wooden surface.
By Bill Doerrfeld May 22, 2026
My latest for Nordic APIs explores 10 API key security risks and what to use alongside keys for stronger API security.
By Bill Doerrfeld May 18, 2026
The yearly API conference, apidays New York, is a hotbed for solid discussion on what's top of mind in the API space, and as MC I had a front row seat.
By Bill Doerrfeld May 13, 2026
My latest for CIO Online features real results form CIOs actively deploying AI agents to empower sales and revenue teams.
By Bill Doerrfeld May 12, 2026
Reports say consumers are souring on AI everywhere, all the time. So, at the risk of losing trust, or even potential business, is adding AI to an existing product really worth it?
By Bill Doerrfeld May 1, 2026
Cloudflare rebuilt Next.js over a weekend using agentic coding.