Mathew Varughese

@stripe • #h2p

[Mathew Varughese @varhawk5]

@stripe How it works under the hood: https://t.co/VdCWTqoRsp.

[Mathew Varughese @varhawk5]

Inside how we ship API changes at @stripe: over the years, we’ve built a highly extensible OpenAPI-based pipeline that propagates changes to our CLI, SDKs, Docs, and internal tools simultaneously.

[Stripe @stripe]

@f6ary Try cmd + shift + d. 👀🌝🤖

[Mathew Varughese @varhawk5]

@janwilmake @stripesupport @stevekaliski yes!

[Mathew Varughese @varhawk5]

@janwilmake @stripesupport @stevekaliski pushed another fix - can you try again?

[Kye @kyeburchard]

For teams who move at the speed of agents, knowledge becomes fragmented, lost to the void, and out of date as fast as its created.

We built Falconer to solve that.

[Falconer @falconer_ai]

Craft and beauty are finally coming to internal docs. Today we're previewing Falconer: the single source of truth for company knowledge.

We're still working through our waitlist, but are now excited to take on more demo requests.

Engineers spend way too much time answering repeated questions and searching for outdated information. We experienced these problems during hypergrowth at Uber and Stripe and thought, "What if we applied external docs treatment to our internal docs?"

That simple approach achieved pretty remarkable results for productivity. And now Falconer is building the AI-native version of those platforms for everyone.

With Falconer, your internal docs are:

- In one place
- Always up to date
- Easy to find
- Synced with your data

Coding agents allow us to generate more code faster than ever...but that code is poorly understood and out of step with the company's crown jewels: business context and tribal knowledge.

Falconer's mission is to connect teams and agents with a shared memory system—always available and always accurate. We're working on it, and will have much more to share soon.

[Mathew Varughese @varhawk5]

@tristanbob @stripe @boltdotnew @base44 @lovable @v0 @Replit Live in v0 and Replit now, try it out! https://t.co/yMi4RWrD2F

[Stripe Developers @StripeDev]

You can now integrate and test Stripe directly in @v0.

[Mathew Varughese @varhawk5]

@jeff_weinstein @stripe h/t @victoria_r_li

[Mathew Varughese @varhawk5]

@tristanbob @stripe good call! fixed - https://t.co/PA3088TJ6p

[Mathew Varughese @varhawk5]

@hafezverde @jeff_weinstein @stripe @cursor_ai Tracking here https://t.co/j27NDjKvTh ! ty for reporting

[Mathew Varughese @varhawk5]

@markwong_987 @jeff_weinstein @stripe @OpenAI Would love to hear more about what use cases you’re thinking of! Mind explaining in more depth here: https://t.co/G13tVlZFvp ?

[Mathew Varughese @varhawk5]

@johnbuilds @jeff_weinstein @stripe @OpenAI What filters would be useful for you? Let us know here: https://t.co/G13tVlZFvp

[Jeff Weinstein @jeff_weinstein]

New as of today: @stripe MCP in @OpenAI Responses API. Just plop in your API key and prompt Stripe in your agentic workflows.

Here’s a quick demo. (Feedback and feature requests welcome!)

[Mathew Varughese @varhawk5]

@jasonzhou1993 @jeff_weinstein @stripe @Cloudflare Hey Jason - have you seen: https://t.co/hRWHUbAp1j ?

[Mathew Varughese @varhawk5]

@dead8309 @jeff_weinstein great feedback - tracking this issue here: https://t.co/XurU5G71m9

[Jeff Weinstein @jeff_weinstein]

In-depth technical details on how we built @stripe's AI assistant for VS Code, including retrieval, evals, measurement, and how we embedded Q&A data from our Discord channel: https://t.co/7910VdtmJ4

[Stripe Developers @StripeDev]

We’ve added /llms.txt and Markdown to @stripe docs: https://t.co/mG9FIaXLTS

Use the .md pages to quickly move Stripe knowledge into your LLM of choice. 📄