OpenAPI
0 statements across 0 episodes · 1 bullish · 1 bearish · 3 people on the record · first statement Jun 21, 2024 by James Brady · said 13 times in 4 episodes since 2024 · across every show →
Mentions by year
brought up most by Ben Firshman (3), Samuel Colvin (1), David Soria Parra (1)
tap a year for its mentions
2025 10 mentions in 3 episodes 3 per episode
2024 3 mentions in 1 episode
Everything said about OpenAPI, oldest first
Jun 21, 2024 neutral
Brady: Elicit generates TypeScript types from Python OpenAPI specs instead of GraphQL
“We don't use GraphQL. So we've got the types defined in Python. That's the source of truth. And we go from the open API spec and there's a tool that you can use to generate types dynamically, like TypeScript types from those opening API definitions.”
Mar 28, 2025 positive
Shah: MCP provides distinct value above OpenAPI for LLM workflows
“I do think MCP as a pro adds value above open API. It's yeah, just because it solves this particular thing. And if we had come to the world, which we have, like, it's like, Hey, we already have open API. It's like, if that were good enough for the universe wou…”
Dec 28, 2025 negative
Passing raw OpenAPI specifications directly to LLMs bloats context and causes confusion
“If you put that into a model, like you will have a lot of bloat there too, right? Actually way worse. And funny enough, when people try to like map one to one things, often the model gets slightly confused because You have like search by name, search by ID, se…”