Stainless @StainlessAPI

Best-in-class SDKs, Docs, and MCP for your API. Joining forces with @AnthropicAI - read more: https://t.co/tGV1sgAlGa stainless.com New York City Joined December 2022

Tweets

339
Followers

5K
Following

34
Likes

381

Kevin Whinnery @kevinwhinnery

2 months ago

Come hang out with me, @dkundel, @cszhu, @ianlivingstone, and @andrewqu to talk about building for and with agents 🤖 API providers are (correctly) very interested in how well coding agents understand and implement their API. I'll compare search via MCP vs. agent skills.

Stainless @StainlessAPI

3 months ago

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.

1 4 23 48K 4

2 3 25 38K 10

View Details

Stainless @StainlessAPI

2 months ago

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…

1 0 16 9K 18

View Details

Stainless @StainlessAPI

3 months ago

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

Jake 🎉 @jitl

3 months ago

shout out to @StainlessAPI folks who asked me for this at @sync_conf happy hour & kept nagging jack about it lmao

1 1 5 10K 0

0 0 7 10K 0

View Details

Stainless @StainlessAPI

3 months ago

RSVP: luma.com/lu4qcfd4

0 0 4 3K 1

View Details

Stainless @StainlessAPI

3 months ago

1 4 23 48K 4

View Details

Stainless @StainlessAPI

3 months ago

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…

0 0 5 2K 0

View Details

Stainless @StainlessAPI

3 months ago

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.

0 2 12 2K 1

View Details

Stainless @StainlessAPI

3 months ago

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…

0 0 1 1K 0

View Details

Stainless @StainlessAPI

3 months ago

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

1 0 3 2K 0

View Details

Stainless @StainlessAPI

3 months ago

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.

2 2 17 2K 7

View Details

batuhan @ThatBoredTurk

3 months ago

@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.

0 1 5 1K 3

View Details

Stainless @StainlessAPI

3 months ago

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…

0 0 1 918 1

View Details

Ayush Agarwal @ayushagarwal

3 months ago

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.