Stainless

Most API docs only show HTTP endpoints, but developers write code with SDKs. We're doing things differently with the Stainless Docs Platform, now available in early access. Stainless Docs are SDK-native. They update automatically when your API changes. Devs see your docs in the language of their choice with method signatures, types, and accurate code snippets.

RSVP: luma.com/lu4qcfd4

On April 2, we're teaming up with @KeycardLabs, @OpenAI, @vercel, and @Google for AX Night. Join us in SF for live demos and Q&A on everything your API needs for agents to integrate successfully. MCP (code mode), agent skills, CLIs, and more.

The Stainless CLI now supports agent skills 🤖 Run `stl skills` and agents like Claude Code and Codex can generate SDKs, trigger builds, manage branches, lint configs, and more. stainless.com/changelog/inst…

Big news… Stainless is expanding into rally racing! 🏎️ Just kidding. We recently worked with an old friend from Stripe, richö, on a security project. Instead of a typical payment, he asked if we’d sponsor his rally car (hard to say no to that). If you happen to see the Stainless logo flying down a gravel stage somewhere, now you know why.

If you already generate SDKs with Stainless, enabling docs takes a single configuration change. Just connect your OpenAPI spec and deploy your docs site in seconds. stainless.com/blog/stainless…

The Stainless Docs Platform is already used in production by @AnthropicAI, @OpenAI, @Beeper, @DigitalOcean, @Letta_AI, @tryprofound, and more.

The Stainless Docs Platform is now in public beta! From the same OpenAPI spec that powers your SDKs, you can generate API reference, SDK examples, and prose guides. Start shipping docs that enable AI agents and delight developers.

@fatihguner @WiroAI aslinda @WiroAI olsam @StainlessAPI kullanirdim. MCP, her dilde SDK ve CLI yaratiyor otomatik olarak ve guncel tutuyor. biz Beeper'da kullaniyoruz, hem OpenAI hem Antropic SDK'lerini onlar generate ediyor. ekibi cok iyi, birlikte calismasi keyifli.

You can now attach additional files to your GitHub releases when publishing SDKs 📦 Configure `release_assets` to upload bundled artifacts, compiled outputs, or extra documentation. stainless.com/changelog/uplo…

The way most MCP servers work is broken. You expose 200 endpoints as 200 tools. The agent burns 100K tokens just reading tool definitions. Then it makes 15 sequential calls to do something that should take one. We just shipped Code Mode on the @dodopayments MCP server. > 2 tools. Search + Execute. The agent searches our docs to understand the API, then writes TypeScript against our SDK. Code runs in an isolated sandbox. One script handles the entire workflow. > 100K tokens -> ~1K tokens > 15 round trips -> 1 execution > API keys in prompts -> server-side injection Shoutout to @StainlessAPI for making this possible. If you're building MCP servers and still exposing one tool per endpoint, you're doing it wrong.

Generated CLI tools now support binary endpoint downloads ✨ That means file exports, media downloads, and raw data endpoints work out of the box, with -o support, pipe-friendly output, and smart filename handling to prevent overwrites. stainless.com/changelog/supp…

The style of MCP server represents best in class accuracy to enable agents to operate an API. Read more and check out our evals on the Stainless blog 📖 stainless.com/blog/sdk-code-…

The agent generates SDK code to generate the context it needs to respond to the prompt, which it then requests for the MCP server to execute. The results of the API request give the agent the information it needs.

"SDK code mode" enables operating an API via MCP with SotA accuracy and efficiency. It's how Stainless MCP servers already work today - learn more on the Stainless blog and in the thread 🧵