We're thrilled to announce that Stainless is joining @AnthropicAI! Stainless was founded to make software better for everyone, and we're honored to continue that mission on the Anthropic team. Check out the announcement blog post for more: stainless.com/blog/stainless…

MCP -> agent skills -> Cloudflare's discovery RFC. All in ~1 year. Agent experience (AX) is evolving fast, and here’s a practical starting point for API providers. stainless.com/blog/steps-tow…

We'll hunt you down at happy hour if that's what it takes 👀 (we 🫶 @NotionHQ at Stainless)

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.

The Stainless Docs Platform is already used in production by @AnthropicAI, @OpenAI, @Beeper, @DigitalOcean, @Letta_AI, @profound, 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.

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…

"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 🧵

Headed to @HumanXCo? Join us at SFMOMA on April 8 for the biggest AI afterparty of the year. @browserbase | @resolveai | @WorkOS | @modal | @mintlify

Yes! We have a blog post coming out soon - we've built our own evals framework and will be detailing the results, methodology, use cases, etc.

MCP is approaching an inflection point, and the limiting factor is becoming obvious. Last week we held our first event in SF with @KeycardLabs, @Cloudflare, @temporalio, and @humanlayer_dev. We talked about what’s breaking in MCP right now, and what it will take to make agent-driven software robust. Some hard truths: - Many MCP servers work in demos but fail across real-world use cases. - “Giant agent skills” are becoming an anti-pattern with thousands of lines explaining things the model already knows, without clarity on the 5% it doesn’t. - Standard MCP approaches (one tool per endpoint or dynamic tools) scored ~50% correctness, but more advanced implementations reached ~70%. - The real kicker: when agents wrote code against production-grade SDKs, correctness jumped to 90–95%. But capability is only half the story. Control is the other half. An in-house Gmail MCP server was great for drafting emails… until it sent one unintentionally. The question isn’t just “can the agent do this?” but “what is it allowed to do?” OAuth scopes and coarse endpoint controls aren’t enough, and we’ll need fine-grained, programmable boundaries like: - Limit an agent to a single document - Cap refund amounts - Prevent broad, unintended actions If AI interfaces are going to replace dashboards, the underlying systems need to behave like an operating system kernel, not a shell script. Capability gets attention. Control earns trust. Trust is what scales.

Java SDK builds now come with a hosted Maven repo for early testing. When a build succeeds, Stainless automatically generates a shareable Maven repository so you can test and distribute pre-release versions before a formal release. The same pre-release testing workflow is supported for Python and TypeScript as well. stainless.com/changelog/stag…

We agree - every company is an API company in a world where AI agents take on more and more work for us. If you need help doing APIs well, and want to make sure agents successfully use your API, we've got you 💪

This post adds a bit more detail regarding SDK generation for SQL databases from OpenAPI specs: stainless.com/blog/introduci… Let us know if you want to try: `SELECT * FROM your_api_endpoint.list();`

Totally agree! "Every company is now an API company, whether they want to be or not." We're proud to partner with devtools leaders like @OpenAI to deliver best-in-class SDKs, docs, and tools for agents that supercharge API adoption. Let's build! 🚀

You can now iterate on your SDKs locally with the Stainless Language Server ⚡ It brings all of the editing capabilities of the Stainless Studio directly into your local environment - VS Code, Cursor, Neovim, Zed, and more. The LSP supports: ✱ Real-time diagnostics with one-click autofixes ✱ Context-aware completions powered by your OpenAPI spec ✱ Go-to-definition + find references across config and spec ✱ Inline codelenses to see SDK coverage in your API ✱ Live Transforms updates as you edit Tighter feedback loops without ever leaving your editor.

Today we're releasing something experimental: a SQL SDK generator. It takes your OpenAPI spec and generates a PostgreSQL extension. Every endpoint becomes a native SQL function.