executor now has a desktop app! add whatever MCPs / OpenAPIs / GraphQL servers you want once and then every agent can use them converts them all into code mode under the hood, so you can have thousands of tools and no context bloat everything stays 100% local on your device

The session saw enriching conversations at GSMA’s 5G Future Summit during MWC Barcelona 2026, where Manish Mangal joined the panel “Intelligence in the Network: A Foundation for 6G.” The discussions centered on how today’s 5G Standalone and 5G‑Advanced architectural decisions are shaping the foundation for future network evolution. The panelists highlighted the roadmap to embedding intelligence, programmability, and openness into current networks that help reduce architectural lock‑in, preserve long‑term investment value, and address emerging consumer and enterprise demands. To discover how our communications solutions are enabling intelligent, future‑ready networks for CSPs, click here: techmahindra.com/industries/… #ScaleAtSpeed #TechMahindra #MWCBarcelona2026 #OpenAPIs #GSMA #MWC26

From network capability to real business value. At GSMA’s 5G Future Summit during MWC Barcelona 2026, the session sparked focused discussions as Ranjan Band joined the panel on “Monetizing Standalone Networks with Open APIs.” The conversation highlighted how standalone networks are becoming the foundation for programmable architectures and Open APIs, including GSMA Open Gateway. Panelists explored practical, core‑native capabilities such as network slicing, QoS control, and exposure APIs, and their role in enabling secure B2B monetization and ecosystem‑led #innovation. To learn how our communications solutions are helping CSPs unlock business value from network capabilities, visit our page: techmahindra.com/industries/… #ScaleAtSpeed #TechMahindra #MWCBarcelona2026 #OpenAPIs #GSMA #MWC26

From conversations to conviction, the momentum is real. As #MWCBarcelona2026 wrapped up, these moments from our booth reflect the energy and intent behind the focused discussions that took place. Sandeep Phadke highlights a clear shift in conversations, with sharper emphasis on execution and growing customer confidence in our services. He also notes how #AI discussions have decisively moved toward governance and real‑world adoption, with a strong focus on progressing beyond pilots and proof‑of‑concepts to scalable impact. This momentum is setting the stage for deeper, more strategic #partnerships that continue to shape the evolving #telecom ecosystem. If you are looking to take these conversations forward with solutions designed to unlock today’s opportunities while preparing for what lies ahead, explore our communications portfolio. Learn more: techmahindra.com/industries/… #ScaleAtSpeed #TechMahindra #OpenAPIs #GSMA

Catch glimpses from @tech_mahindra's buzzing booth on Day 1 of #MWCBarcelona2026. We kicked off the event with our new narrative — Unlock the Spectrum of Possibilities: Grow. Empower. Transform. It presents our overarching roadmap to help telcos maximize growth opportunities as the industry continues to evolve. The booth was vibrant with high energy as we exchanged ideas on emerging technologies, next‑gen network architectures, and real-world impact. These conversations extended onto our exclusive Theatre Summit stage, where leaders from across the client and partner ecosystem shared perspectives, exchanged playbooks, and explored how #collaboration today is shaping the technology and networks of tomorrow. If you’re keen to explore practical solutions to transform your business, visit us at Booth 2D46, Hall 2. Learn more: techmahindra.com/insights/ev… #ScaleAtSpeed #MWC26 #TechMahindra #OpenAPIs #6G #5G #AI

The path to monetizing future networks starts with the choices we make today. Join Ranjan Band on the panel “Monetizing Standalone Networks with Open APIs” at the #5G Future Summit, taking place during MWC Barcelona 2026. The session explores how standalone networks are laying the foundation for programmable networks and Open APIs, including GSMA Open Gateway. If you’re looking to unpack core‑native network capabilities, this session offers practical insights into network slicing, QoS control, and exposure APIs, and their role in enabling secure B2B monetization and ecosystem‑led innovation. To expand monetization horizons and unlock new growth opportunities, visit @tech_mahindra at Booth 2D46, Hall 2, from March 2–5, 2026, and experience network #innovation in action. Learn more: mwcbarcelona.com/agenda/sess… #ScaleAtSpeed #TechMahindra #MWCBarcelona2026 #OpenAPIs #GSMA

Checked in at 7am for WVC Day 1 and I’m here to listen, learn, and ask the questions that matter, vendor neutral, practice first. 🔍🏥 If you see me roaming the Expo Hall, say hi. 👋 #WVC2026 #WVC #WesternVeterinaryConference #VetMed #VeterinaryMedicine #VeterinaryPractice #AnimalHealth #VeterinarySoftware #VetTech #PracticeManagement #PIMS #VendorNeutral #WorkflowMatters #OpenAPIs #LasVegas

Just shipped some updates to openapisearch🔧 1. OpenAPI -> SKILL.md New /skills/{hostname} endpoint generates skill from any OpenAPI spec 2. OpenAPI -> llms.txt The slop is now llms.txt compatible, so every SLOP can soon be used by the LLMTEXT MCP. For example: openapisearch.com/openai 3. higher level overview: openapisearch.com/llms.txt Stop hallucinating on APIs by using the best source of truth: OpenAPIs!!!

Agile Telco’s latest Market Report explores how operators can profit from AI, not just pilot it. Marc Price, MATRIXX CTO, weighs in on the big sift ahead. Read the report here: techledworld.com/channel/agi… #AgileTelco #AI #Monetization #BSS #OpenAPIs

I treat my openais like openapis, man

Accelerate your digital journey with API Setu – the unified platform that simplifies the entire API lifecycle, from publishing to consumption. Connects the public and private sectors through a secure gateway of trusted APIs. Enables innovation, efficiency, and inclusivity through open and secure APIs. Unlock new possibilities with API Setu today! #APISetu #DigitalIndia #Innovation #TechforGood #OpenAPIs #DigitalTransformation #InnovationInAction

SDKs suck in the age of AI coding. With AI tooling like cursor and claude code we're all blindly trusting the "AI context engine" that it will just magically find what it needs to know and nothing else, and never hallucinate. But is it really that great? Tools like @context7AI seem to improve it, but is Vector Search the only way? Tbh, it never works for me! Docs aren't complete. SDK context is too large. The complete spec can often be found in the API reference which is based off OpenAPI. With OpenAPISearch I created a way to allow very easy navigation through large OpenAPIs with tons of information. @mintlify adopted the same approach, linking to subsets of the openapi spec (each operation) from their generated `llms.txt`. Now I'm looking for the same thing for SDKs. @StainlessAPI has some great reads on MCP stainless.com/blog/mcp-is-ea…, stainless.com/blog/from-api-…, but their SDK builds don't create neat API surface files. Are these MCPs gonna be able to use the SDK, or just the APIs? Seems people are skipping a step. Parallel uses Stainless and soon we'll have a Typescript SDK. The token count of the source of the Typescript SDK is around 180k tokens. After merging types into one file for the Parallel SDK using api-extractor.com, I got it down to 18k tokens. But this is still a lot! The original source OpenAPI was under 12000 tokens. A simple prompt shows it can easily be reduced to just 4500 tokens letmeprompt.com/rules-httpsu…. This is starting to be more manageable for AI. What if SDK companies like @StainlessAPI, @buildwithfern, and @scalar would generate "agent friendly" API surface files? - .d.ts for typescript - .pyi for python - etc etc etc But not only for the entire SDK but also for every individual method, like openapisearch.com does for API operations? I think this would make selecting the right context much easier and give the developer more freedom to choose different strategies to build high-quality context. Library and API maintainers, SDK creators, please! Fix your context and put it in your repos. Is it just me? Am I just using AI wrong? Or is there really a big drawback to these convoluted contexts of libraries and SDKs?

Did a small revamp and UX improvements to OpenAPI search today - More professional landingpage and mobile friendliness - Improved directory page - Error page for when OpenAPIs couldn't be found: it leads people to instructions on how to make the OpenAPI more discoverable! Especially the last point is something I think is much needed, almost nobody does it right! Still has a lot more potential, but this was a much needed QOL update. For one, I want to turn the MCP into a remote MCP that is accessible through some browser-based MCP client. Also, I'm thinking to maybe make it stateful since I'm getting quote a few requests and it has a cost. I can start caching the URLs into a bidirectional KV to create shorter slugs for custom openapi URLs. Any other ideas on how to improve this?

Why is @econetzimbabwe limiting access to key APIs like SMS and others? These restrictions are stifling innovation and locking out developers who could build services that benefit users and grow the digital economy. @WillarShoko @Techzim @begottensun @econet_support Open access = progress. #DigitalZimbabwe #OpenAPIs #InnovationBlocked

How can telcos monetize data & scale partnerships? Watch our expert webinar to explore: 🔹 Telco in the platform economy 🔹 Data-as-a-Service value 🔹 Open API-led partner onboarding Watch now: torryharris.com/events/webin… #OpenAPIs #DaaS #OpenBusinessPlatform

👨‍💻 개발자분들, 주목! UXLINK의 SDK 및 API가 개방되었습니다 🔓 54M 사용자 기반을 활용해 강력한 dApp을 구축하세요. Web3의 미래를 함께 만들어가요. #UXLINK #Web3Dev #OpenAPIs

Stricter schema. Better sdk generation. Docs go hand in hand with schema design instead off out of date openapis forever. Waaay easier and cleaner pagination than any odata atrocities. Lazy loaded nesting. Easier to fragment. Easier to facade. Easier to project.

Lot of people disagree with me. They have good arguments, most of current apis won't work well if you make a direct mapping from OpenAPI operations to tools. The thing is, semantically an operation is very similar to a tool, and there are 1000s of openapis in the ecosystem. MCP is a new ecosystem and because it doesn't connect with anything, in practice we see most of the introduced MCPs being thin wrappers around REST APIs, adding some improved description and selecting some parameters. This whole filtering is done in code and makes it very hard to analyse with code. Rater than that, we could've done the same filtering and editing in the openapi data structure, creating a new openapi from the old openapi I've built dozens of openapi specs in recent years and have built tool calling on top of it as well. if your openapi definition is good and the endpoints make sense to llms, it works just as well for current day models. also worked well 2-3 years ago I started experimenting. I'm sure MCP is gonna be more than what OpenAPI-as-MCP can deliver as it has more features specific for LLMs, but you can't just ignore the defacto standard for specifying REST apis completely. A bridge needs to exist. It's a huge gap right now and I think (concpiracy mode on) it was purposefully NOT DONE because MCP didn't want to loose value to OpenAPI. Genius go to market making it fully different.

Minor Update: 102040 is live! ⚙️ • Translations AI & OpenAPIs are now live! • Major speed improvements for maps • New Storage Box features & UI fixes Full changelog in the thread below 👇

OpenAPI Specを使ったMCPサーバ "janwilmake/openapi-mcp-server: Allow AI to wade through complex OpenAPIs using Simple Language" github.com/janwilmake/openap… #OpenAPI #MCP