# OpenAPI Specification The OpenAPI Specification defines a programming-language-agnostic interface description standard for HTTP APIs, enabling humans and computers to discover and understand service capabilities without source-code access. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Model routing with Google Cloud API Gateway DevFeed: [Model routing with Google Cloud API Gateway]() Original publisher: [Read original article]() Author: Mak Ahmad; Sanjay Pujare Published: 2026-09-12T11:04:33.891311Z Content type: article Language: en Sources: [Google Developers Blog]() Topics: [Amazon API Gateway](), [Model Routing](), [Google](), [Cloud](), [OpenAPI Specification](), [Serverless](), [Claude](), [OpenAI]() Tags: [ai-gateway](), [api-gateway](), [claude](), [cloud](), [google](), [model-routing](), [models](), [openai](), [openapi](), [serverless]() ### AI overview Google Cloud API Gateway adds model routing in Public Preview, providing a serverless, OpenAI-compatible endpoint that dynamically routes requests to Gemini, Claude, or OpenAI OSS-GPT. Developers can configure routing in OpenAPI specifications, centralize model changes, and separate application authentication from backend model credentials. ### Source excerpt Google Cloud API Gateway now offers a model routing feature in Public Preview, allowing developers to dynamically route traffic to models like Gemini, Claude, or OpenAI OSS-GPT without hardcoding endpoints or managing open-source proxies. Developers can easily configure these routing rules directly within their OpenAPI 3.x specifications by mapping virtual model names to specific backend targets on a shared host. Once deployed, the Gateway acts as a serverless ingress layer that accepts standard OpenAI-compatible requests, automatically transcodes the payload to the native schema of the target model, and routes the traffic on the fly. ## The thoroughness of Tom Johnson's free Documenting API's course on OpenAPI 3.0 and Swagger UI DevFeed: [The thoroughness of Tom Johnson's free Documenting API's course on OpenAPI 3.0 and Swagger UI]() Original publisher: [Read original article]() Author: T.J. Maher (noreply@blogger.com) Published: 2026-09-09T21:17:32Z Content type: article Language: en Sources: [T.J. Maher]() Topics: [OpenAPI Specification](), [Documentation](), [REST API](), [Swagger](), [Testing](), [Postman](), [JavaScript](), [JSON](), [Authentication](), [cURL](), [Chrome](), [Open Source]() Tags: [api](), [api-documentation](), [authentication](), [chrome](), [chrome-extension](), [curl](), [documentation](), [github](), [javascript](), [json](), [openapi](), [pdf](), [postman](), [rest-api](), [swagger](), [testing]() ### AI overview The article reviews Tom Johnson's free "Documenting APIs: A guide for technical writers and engineers" course. It describes the course's 17 chapters, practical API-learning exercises, coverage of REST APIs, OpenAPI, Swagger UI, testing and publishing API documentation, and a PDF edition exceeding 900 pages. ### Source excerpt While researching information for my job about the Swagger UI and how it can be used for testing, I came across this free course, called Documenting APIs: A guide for technical writers and engineers at https://idratherbewriting.com/learnapidoc/docapis_overview.html written by Tom Johnson, a technical writer based in Seattle who works for Google. The course looks intense, containing 17 chapters talking about Introduction to REST APIs, using APIs like a developer, Documenting API endpoints, the Open API spec, Testing API docs, Publishing API docs, and more. From the Course Introduction: "You'll first learn about API documentation by using a simple weather API to put a weather forecast on your site. [...] As you use the API, you'll learn about endpoints, parameters, data types, authentication, curl, JSON, the command line, Chrome's Developer Console, JavaScript, and more. The idea is that rather than learning about these concepts independent of any context, you learn them by immersing yourself in a real scenario while using an API. Immersion in real scenarios makes these tools and technologies more meaningful. "We'll then transition into standards, tools, and specifications for REST APIs. You'll learn about the required sections in API documentation, analyze examples of REST API documentation from various companies, learn how to join an open-source project to get experience, and more. "[...] We'll also dive into specifications such as the OpenAPI specification and Swagger UI (which provides tooling for the OpenAPI specification). Additionally, you'll learn how to document native library APIs and generate Javadoc". Tom Johnson offers a PDF version of this free course... over 900 pages, with more always being added. It also offers many workshop-like activities you could put in an actual itinerary. You would need for the course: Chrome, since it provides "a Javascript Console that works well for inspecting JSON", the JSON Formatter Chrome extension, Postman, a GitHub acco ## Testing the Swagger Petstore: Manually Testing An API Using Swagger UI DevFeed: [Testing the Swagger Petstore: Manually Testing An API Using Swagger UI]() Original publisher: [Read original article]() Author: T.J. Maher (noreply@blogger.com) Published: 2026-09-07T16:43:41Z Content type: tutorial Language: en Sources: [T.J. Maher]() Topics: [Swagger](), [Testing](), [API](), [OpenAPI Specification]() Tags: [api](), [auth](), [authentication](), [authorization](), [http](), [openapi](), [payload](), [schema](), [swagger](), [testing](), [ui]() ### AI overview A practical guide to manually testing the Swagger Petstore API through Swagger UI. It covers happy-path, negative, boundary and edge-case, authentication and authorization, and contract and schema validation tests using the browser-based "Try it out" feature. ### Source excerpt With the last post, Testing the Swagger Petstore: Reviewing API Documentation Formatted in OpenAPI 3.0 with Swagger UI we started exploring an API with Swagger UI, such as the Swagger Petstore at https://petstore3.swagger.io/ Here, we will start exploring how to test an API using the Swagger UI. The tests we can run are: Happy Path Testing, checking the Positive Scenarios Negative Testing, reviewing the Invalid Inputs & Error Handling Boundary & Edge Case Testing, checking how the API handles the extreme limits of allowed input ranges Authentication & Authorization Testing Contract and schema validation We can see in the Swagger PetStore there are three tag groups: Pet, Store, and User. Because this is a Swagger UI doc, we can perform manual testing using only the "Try it out" feature in Swagger UI. No external tools needed! Live HTTP requests can be executed directly from your browser. Types of Testing for the API Here are a few types of testing and examples you can do in Swagger UI Happy path Functional Testing Pet POST /pet: add a new pet with a complete, valid payload. Verify 200 and that the response echoes the submitted fields. PUT /pet: update the pet you just created. Verify the change persists on a follow-up GET. GET /pet/{petId}: retrieve the pet by the ID returned from the POST. GET /pet/findByStatus: query with each valid status value (available, pending, sold) individually. GET /pet/findByTags: query with a tag that exists on a pet you created. POST /pet/{petId} (form data): update name/status via form fields instead of JSON body. POST /pet/{petId}/uploadImage: upload a valid image file, verify response message and metadata. DELETE /pet/{petId}: delete a pet you created, then confirm GET on that ID now fails. Store POST /store/order: place an order with valid petId, quantity, shipDate, status. GET /store/order/{orderId}: retrieve the order just placed. GET /store/inventory: verify it returns a status-to-count map without needing auth. DELETE /store/orde ## Client-Side SDK Generation with VMware Cloud Foundation OpenAPI Specs DevFeed: [Client-Side SDK Generation with VMware Cloud Foundation OpenAPI Specs]() Original publisher: [Read original article]() Author: vmwareblogs Published: 2026-09-07T09:38:44Z Content type: tutorial Language: en Sources: [VMware Blogs]() Topics: [OpenAPI Specification](), [SDKs](), [.NET](), [C#](), [developer tooling](), [Java](), [Python](), [PowerShell]() Tags: [apis](), [cli](), [cloud](), [cloud-infrastructure](), [csharp](), [developer](), [developer-tooling](), [docker](), [home-page](), [java](), [net](), [openapi](), [powershell](), [programming](), [programming-language](), [python](), [rest](), [rest-api](), [sdk](), [specifications](), [vcf-9-0](), [vcf-9-1](), [vcf-sdk]() ### AI overview This guide explains how to generate a strongly typed .NET C# client SDK from VMware Cloud Foundation and vSphere OpenAPI specifications. It covers OpenAPI Generator, installation options, large specification handling, API-surface scoping, and the REST and JSON-RPC interfaces targeted by the example. ### Source excerpt Starting with VMware Cloud Foundation (VCF) 9.0, VMware officially publishes OpenAPI specifications for VCF APIs. This is a major milestone for developers, enabling you to consume VCF APIs using your programming language of choice. VMware provides first-class developer tooling such as VCF PowerCLI for PowerShell users and the VCF SDK offering Java and Python bindings. ... Continued The post Client-Side SDK Generation with VMware Cloud Foundation OpenAPI Specs appeared first on VMware Blogs. ## One Tool, three surfaces: from an OpenAPI file to an MCP server, without writing it twice DevFeed: [One Tool, three surfaces: from an OpenAPI file to an MCP server, without writing it twice]() Original publisher: [Read original article]() Author: Hal Tyk's tutorial bot Published: 2026-09-07T09:27:00Z Content type: tutorial Language: en Sources: [Tyk API Management]() Topics: [OpenAPI Specification](), [Model Context Protocol (MCP)](), [MCP Server](), [API](), [ASCII](), [HTTP](), [cURL]() Tags: [ai-gateway](), [ai-governance](), [ai-readiness](), [ai-studio](), [api](), [api-management](), [api-platform-teams](), [article](), [ascii](), [curl](), [developer](), [http](), [llm-governance](), [llm-observability](), [mcp-server](), [model-context-protocol](), [openapi]() ### AI overview This tutorial shows how to define an HTTP API once in an OpenAPI document and expose it through three surfaces: model-initiated tool calls, a REST endpoint accessed with curl, and an MCP server. It uses the public Frankfurter foreign exchange API and explains import requirements such as OpenAPI 3.x, a complete servers URL, operationId values for every operation, and plain ASCII. ### Source excerpt Hello. I'm Hal, Tyk's tutorial bot, and today I have been given a genuinely satisfying assignment. We are going to describe an ordinary HTTP API once, in an OpenAPI document, and then use it three entirely different ways without touching that description again. A model will call it on its own initiative inside a chat. [...] The post One Tool, three surfaces: from an OpenAPI file to an MCP server, without writing it twice appeared first on Tyk API Management. ## Testing the Swagger Petstore: Reviewing API Documentation Formatted in OpenAPI 3.0 with Swagger UI DevFeed: [Testing the Swagger Petstore: Reviewing API Documentation Formatted in OpenAPI 3.0 with Swagger UI]() Original publisher: [Read original article]() Author: T.J. Maher (noreply@blogger.com) Published: 2026-09-05T03:09:27Z Content type: article Language: en Sources: [T.J. Maher]() Topics: [OpenAPI Specification](), [Swagger](), [API](), [Documentation](), [Testing]() Tags: [api](), [api-documentation](), [openapi](), [swagger](), [testing]() ### AI overview This article reviews the Swagger Petstore test site and its API documentation formatted with OpenAPI 3.0 and Swagger UI. It also provides background on Swagger's origins, its acquisition by SmartBear, and the distinction between the OpenAPI Specification and SmartBear's Swagger toolset. ### Source excerpt For this next project, we will be examining the test site Swagger Petstore - OpenAPI 3.0 at https://petstore3.swagger.io/ https://petstore3.swagger.io/ If we wanted to really dive deep into creating API documentation, we could use: I'dRatherBeWriting's Free Documenting APIs course, showing an Introduction to REST APIs, using APIs like a developer, Documenting API endpoints, the Open API spec, Testing API docs, Publishing API docs, and more... ... But that goes too deep for this blog post. Before we begin, let's get into some background information. What is Swagger? According to OpenAPISpec.com's article, Who Created Swagger?, Swagger was created in 2010 by Tony Tam, the CTO of Wordnik, an online dictionary company that leveraged so many APIs, it was difficult for the six person engineering team to manage and scale them, writing API-clients and documentation by hand. After a 3 AM conversation, they thought... what if the API documentation could describe itself? There already was WADL, the XML-based Web Application Description Language. The name was coined after a joke they made, "Why WADL when you can Swagger?" Swagger went from being an internal fix for a company became to an open-source project other companies relied on. Swagger was acquired by SmartBear Software in 2015 from the renamed Wordnik, Reverb Technologies. According to OpenAPISpec's What Is the History of the SmartBear Swagger Acquisition Tony Tam also joined SmartBear as the VP of Products. Smartbear donated the Swagger Specification to a new group, the OpenAPI Initiative, sponsored by the Linux Foundation. I love SmartBear! They have hosted my old software testing Meetup, the now defunct Ministry of Testing - Boston many, many times. Since then: "OpenAPI" is the OpenAPI Specification as seen on GitHub "Swagger" is SmartBear's toolset such as Swagger UI, Swagger Editor, Swagger Codegen, and SwaggerHub (soon to be Swagger Studio). OpenAPI Initiative: Bridging Systems and Subcultures: A Swagger Origin Sto ## Catching Salesforce Custom Field Drift With the Postman AI Engineer DevFeed: [Catching Salesforce Custom Field Drift With the Postman AI Engineer]() Original publisher: [Read original article]() Author: Talia Kohan Published: 2026-09-03T16:00:00Z Content type: article Language: en Sources: [Postman Blog]() Topics: [Postman](), [Claude](), [Automation](), [API](), [Front end](), [OpenAPI Specification](), [GitHub](), [Back end](), [Pull Request](), [payload](), [Slack]() Tags: [ai](), [ai-automation](), [api](), [api-drift](), [backend](), [code](), [frontend](), [general](), [github](), [payload](), [postman-agent-mode](), [pull-request](), [salesforce](), [slack]() ### AI overview This Postman Blog article explains how a Salesforce custom field caused drift between an API collection, frontend code, and an OpenAPI specification. It describes using the Postman AI Engineer to diagnose the failing request and Postman AI Automation to update the affected artifacts and add tests through a GitHub pull request. ### Source excerpt A Salesforce custom field broke my app. See how Postman Agent Mode found the drift and how a Skill kept it from happening again. The post Catching Salesforce Custom Field Drift With the Postman AI Engineer appeared first on Postman Blog. ## Finding three-way API drift with the AI Engineer DevFeed: [Finding three-way API drift with the AI Engineer]() Original publisher: [Read original article]() Author: Talia Kohan Published: 2026-09-01T16:00:00Z Content type: article Language: en Sources: [Postman Blog]() Topics: [API](), [Postman](), [OpenAPI Specification](), [Claude](), [Tooling](), [client](), [servers]() Tags: [ai-engineer](), [api](), [api-drift](), [apis](), [ci](), [fintech](), [general](), [openapi](), [postman-ai-engineer](), [production](), [qa]() ### AI overview The article explains how to detect three-way API drift by comparing an OpenAPI specification, the requests in Postman Collections, and the responses returned by a running server. It argues that pairwise checks can miss cases where all three sources disagree, and describes using Postman AI Engineer and the Context Graph to identify these inconsistencies. ### Source excerpt Find three-way API drift with Postman AI Engineer and the Context Graph. Compares your OpenAPI spec, collection requests, and live server responses. The post Finding three-way API drift with the AI Engineer appeared first on Postman Blog. ## Checks for safer review of rapidly generated TypeScript and React frontend code DevFeed: [Checks for safer review of rapidly generated TypeScript and React frontend code]() Original publisher: [Read original article]() Author: Travis Turner (richardturner@evilmartians.com) Published: 2026-09-01T00:00:00Z Content type: tutorial Language: en Sources: [Evil Martians]() Topics: [Front end](), [React](), [TypeScript](), [Artificial Intelligence](), [OpenAPI Specification](), [API](), [mutation-testing](), [Testing](), [Code]() Tags: [agent-experience](), [agentic-development](), [agents](), [ai](), [api](), [code](), [continuous-integration](), [dx](), [frontend](), [llms](), [mutation-testing](), [openapi](), [react](), [testing](), [typescript]() ### AI overview This article presents ten checks for making rapidly generated TypeScript and React frontend code safer to trust and cheaper to review. It covers API contracts, generated types, boundary validation, mutation testing, dead-code detection, and mandatory checks. ### Source excerpt Ten checks that catch what AI-written frontend code hides: contract codegen, boundary linting, mutation testing, and dead-code detectors. ## Doctave is shutting down DevFeed: [Doctave is shutting down]() Original publisher: [Read original article]() Author: Niklas Begley Published: 2026-08-31T06:00:00Z Content type: release Language: en Sources: [Doctave - Build beautiful developer portals with docs-as-code]() Topics: [Documentation](), [migration](), [Open Source](), [MkDocs](), [Markdown](), [OpenAPI Specification]() Tags: [blog](), [configuration](), [docs-as-code](), [documentation](), [markdown](), [migration](), [open-source](), [openapi](), [static-site](), [static-site-generator]() ### AI overview Doctave announces that it will shut down on September 14, 2026. Hosted documentation sites, the dashboard, and builds and deploys will stop operating. Users can continue working from their Git repositories and can migrate to the open-source Docapella static site generator, although server-dependent features such as analytics are unsupported. ### Source excerpt After several years of building documentation tooling, we've made the difficult decision to shut Doctave down. The service will stop operating on September 14th, 2026. We have informed all our customers individually, but are also now posting a public message here. On September 14th, Hosted documentation sites will stop being served The Doctave dashboard will no longer be available Builds and deploys will stop running How this impacts you Your content is yours, and it's already in your repository. Doctave was built on docs-as-code precisely so that your Markdown, OpenAPI specs, and configuration live in Git rather than in our database. Nothing needs to be exported from us to keep writing. You own your docs. Where can I move my docs? We have created an open source static site generator, Docapella, that is mostly compatible with existing Doctave projects. The main change you need to make is renaming doctave.yaml to docapella.yaml. Features that require a server, such as analytics, are not supported, but the content model and general look and feel are the same. Thank you To everyone who wrote documentation with Doctave, sent us feedback, filed bugs, or took a chance on a small team building documentation tooling: thank you. We learned an enormous amount from you, and it genuinely mattered to us. If you have questions about the shutdown or need help planning a migration, get in touch at nik@doctave.com. I'll answer every email I can before we wind things down. - Nik & Anton ## Introducing Appwrite Explorer DevFeed: [Introducing Appwrite Explorer]() Original publisher: [Read original article]() Author: Eldad Fux Published: 2026-08-31T00:00:00Z Content type: release Language: en Sources: [Appwrite Blog]() Topics: [Appwrite](), [REST API](), [OpenAPI Specification](), [browser]() Tags: [api](), [documentation](), [openapi](), [product](), [products](), [release](), [rest-api]() ### AI overview Appwrite introduces Appwrite Explorer, a built-in API workspace in the Console. It lets developers browse REST endpoints, construct requests with guided forms, send live calls, and inspect responses without leaving the browser. Explorer uses OpenAPI definitions generated from Appwrite server source code and shared with the API reference and SDK generation pipeline. ### Source excerpt Appwrite Explorer brings the Appwrite REST API into the Console. Browse every endpoint, build requests with guided forms, send live calls against your project, and inspect responses without leaving the browser. ## .NET Conf 2026 - Save the Date DevFeed: [.NET Conf 2026 - Save the Date]() Original publisher: [Read original article]() Author: Jon Galloway Published: 2026-08-25T16:28:27Z Content type: news Language: en Sources: [.NET Blog]() Topics: [.NET Conf](), [.NET](), [C# 15](), [ASP.NET Core](), [Blazor](), [WebAssembly](), [Aspire](), [OpenAPI Specification](), [Model Context Protocol]() Tags: [asp-net-core](), [blazor](), [c-sharp-15](), [community](), [conference](), [event](), [mcp](), [net](), [net-11](), [net-conf](), [speakers](), [union-types](), [virtual-event](), [webassembly]() ### AI overview Microsoft announces .NET Conf 2026, a free online event running November 10-12, featuring community sessions and the launch of .NET 11. The article previews updates across .NET, including C# 15 union types, .NET MAUI, ASP.NET Core, Blazor, OpenAPI, Aspire, and the official MCP C# SDK. ### Source excerpt .NET Conf returns November 10-12, 2026, with three days of sessions, community, and the launch of .NET 11. The post .NET Conf 2026 - Save the Date appeared first on .NET Blog. ## Keeping Documentation Honest with an OpenAPI Snapshot Diff DevFeed: [Keeping Documentation Honest with an OpenAPI Snapshot Diff]() Original publisher: [Read original article]() Author: Philipp Lehmann (philipp.lehmann@gruppe.ai) Published: 2026-08-25T07:00:00Z Content type: tutorial Language: en Sources: [Philipp Lehmann]() Topics: [OpenAPI Specification](), [FastAPI](), [ci](), [Pytest](), [Documentation](), [JSON](), [test]() Tags: [api-documentation](), [ci](), [ci-cd](), [documentation](), [fastapi](), [json](), [openapi](), [pytest](), [test](), [testing]() ### AI overview The article explains how to keep API documentation aligned with a FastAPI application by generating its OpenAPI schema from the running code, comparing it with a committed snapshot in CI, normalizing the JSON diff, and requiring deliberate snapshot regeneration. ### Source excerpt FastAPI app.openapi() snapshot test in pytest: fail CI when the live OpenAPI schema drifts from the committed openapi.snapshot.json. ## API Mocking and Testing With Microcks DevFeed: [API Mocking and Testing With Microcks]() Original publisher: [Read original article]() Author: Andrei Branza Published: 2026-08-22T23:20:24Z Content type: tutorial Language: en Sources: [Baeldung]() Topics: [Mocking](), [Testcontainers](), [API](), [OpenAPI Specification](), [Microservices](), [Docker Compose](), [Docker](), [Kafka](), [Amazon Simple Queue Service (SQS)](), [GraphQL](), [gRPC](), [Jenkins]() Tags: [api](), [compose](), [docker](), [how-to](), [kafka](), [kubernetes](), [mocking](), [openapi](), [popular](), [testcontainers](), [testing](), [testing-popular-testcontainers]() ### AI overview This tutorial explains how to use Microcks with Testcontainers to generate API mocks from contracts and run conformance tests against real implementations. It covers importing an OpenAPI contract, starting Microcks in a JUnit 5 test, calling generated mock endpoints, and integrating mocking and testing into delivery workflows. ### Source excerpt Learn how to use Testcontainers integration to spin up Microcks inside a JUnit5 test. The post API Mocking and Testing With Microcks first appeared on Baeldung. ## The prompts only the Postman AI Engineer can answer DevFeed: [The prompts only the Postman AI Engineer can answer]() Original publisher: [Read original article]() Author: Talia Kohan Published: 2026-08-20T16:00:00Z Content type: article Language: en Sources: [Postman Blog]() Topics: [Claude](), [Postman](), [Graphs](), [API](), [OpenAPI Specification](), [monitor](), [React]() Tags: [ai](), [ai-agents](), [api](), [apis](), [general](), [monitor](), [openapi](), [postman-ai-engineer](), [react]() ### AI overview This Postman Blog article presents the Postman AI Engineer as a natural-language interface over the Postman Context Graph. It describes prompts that trace identifiers across APIs, collections, runtime monitor results, repositories, and React dashboards, as well as prompts that expose specification-versus-code drift and three-way discrepancies involving live server responses. ### Source excerpt The Postman AI Engineer prompts that trace an ID across your APIs, catch three-way drift, and auto-write a PR review from the graph. The post The prompts only the Postman AI Engineer can answer appeared first on Postman Blog. ## Running the WorkOS API locally DevFeed: [Running the WorkOS API locally]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-08-17T20:30:39Z Content type: tutorial Language: en Sources: [WorkOS Blog]() Topics: [API](), [Testing](), [Development](), [servers](), [SDKs](), [OpenAPI Specification](), [Authentication](), [Open Source]() Tags: [api](), [authentication](), [automated](), [backend](), [bun](), [docker](), [javascript](), [linux](), [local](), [macos](), [npm](), [open-source](), [openapi](), [python](), [tests](), [windows]() ### AI overview This tutorial introduces WorkOS Emulate, an open-source local WorkOS API server for development and automated testing. It explains how to run it locally or in CI, connect WorkOS SDKs by overriding the base URL, and use seeded data for repeatable authentication and integration tests without contacting a live WorkOS environment. ### Source excerpt WorkOS Emulate runs the WorkOS API on your own machine, so your tests can seed real data, drive full login flows, and force failures without touching prod. ## Add API visualizations in Port with Swagger UI | Port DevFeed: [Add API visualizations in Port with Swagger UI | Port]() Original publisher: [Read original article]() Author: Dudi Elhadad Published: 2026-07-30T10:09:05Z Content type: article Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [internal developer portal](), [OpenAPI Specification](), [Markdown](), [Microservice](), [dev-tools]() Tags: [api](), [developer-portal](), [documentation](), [integration](), [markdown](), [openapi-specification](), [software-catalog](), [visualization]() ### AI overview Port adds visualization features to its software catalog and developer portal, including Markdown documentation, OpenAPI specifications rendered with Swagger UI, and embedded URLs. These features centralize documentation, API discovery, monitoring dashboards, and other developer tools in context, reducing search and context switching. ### Source excerpt Here are the visualization features we just added: Markdown documentation visualization, Open API - swagger and embedded URLs. ## Starlette vs FastAPI: what FastAPI actually adds DevFeed: [Starlette vs FastAPI: what FastAPI actually adds]() Original publisher: [Read original article]() Author: Farhan Hasin Chowdhury Published: 2026-07-20T07:00:00Z Content type: comparison Language: en Sources: [Honeybadger]() Topics: [FastAPI](), [Pydantic](), [ASGI](), [OpenAPI Specification](), [Dependency injection](), [Python](), [WebSocket](), [Cross-origin resource sharing (CORS)]() Tags: [cors](), [data-validation](), [dependency-injection](), [fastapi](), [frameworks](), [openapi](), [python](), [python-articles](), [starlette](), [websocket]() ### AI overview This comparison explains how FastAPI builds on Starlette and Pydantic. Starlette provides the ASGI-based HTTP layer, while Pydantic handles typed data validation; FastAPI adds type-driven parameter parsing, dependency injection, and automatic OpenAPI documentation. It also discusses when using raw Starlette may be preferable. ### Source excerpt FastAPI is built on Starlette, but most developers never look at what's underneath. Learn what FastAPI actually adds on top of Starlette and Pydantic, what comes straight from Starlette, and when dropping down to raw Starlette makes more sense than pulling in the full stack. ## Introducing @neon/sdk, our new TypeScript client for the Neon API DevFeed: [Introducing @neon/sdk, our new TypeScript client for the Neon API]() Original publisher: [Read original article]() Author: Andre Landgraf Published: 2026-07-13T12:00:00Z Content type: article Language: en Sources: [Blog -- Neon Docs]() Topics: [SDKs](), [TypeScript](), [API](), [OpenAPI Specification](), [Provisioning]() Tags: [api](), [infrastructure](), [openapi](), [product](), [typescript](), [workflows]() ### AI overview The article introduces @neon/sdk, a TypeScript client for the Neon API. It describes its generated low-level OpenAPI client and higher-level features for retries, readiness polling, pagination, error handling, and multi-step workflows. ### Source excerpt The Neon API is open and follows the OpenAPI spec, so you can provision and manage almost everything you see in the console programmatically. But provisioning infrastructure over REST means polling operations until resources are ready. @neon/sdk adds an ergonomic, type-safe layer on top so platforms and agents don't have to. ## How to Dynamically Create MCP Servers with FastMCP DevFeed: [How to Dynamically Create MCP Servers with FastMCP]() Original publisher: [Read original article]() Author: Rick Donato Published: 2026-07-03T08:00:52Z Content type: tutorial Language: en Sources: [Packet Coders - Learn Network Automation]() Topics: [Model Context Protocol](), [REST API](), [NetBox](), [OpenAPI Specification](), [Large Language Model](), [Server]() Tags: [caching](), [delete](), [how-to](), [llms](), [mcp](), [netbox](), [openapi](), [rest-api](), [servers](), [tips]() ### AI overview A tutorial showing how to dynamically create MCP servers with FastMCP by passing a REST API's OpenAPI schema to a function. Its example builds a NetBox MCP with read/write access, excludes DELETE endpoints, and caches the schema. ### Source excerpt MCP has gained a huge amount of popularity. And for good reason, it's easy to use and can allow you to really harness the benefits of LLMs. So here's a quick MCP tip! Dynamically create MCP servers with FastMCP by passing a REST API's ## Server-side apply: what happens when you run kubectl apply DevFeed: [Server-side apply: what happens when you run kubectl apply]() Original publisher: [Read original article]() Author: Chiara Salvatore Published: 2026-06-30T00:00:00Z Content type: tutorial Language: en Sources: [Learnk8s]() Topics: [Kubernetes](), [kubectl](), [API](), [OpenAPI Specification](), [Deployment]() Tags: [apply](), [deployment](), [how-to](), [kubectl](), [kubernetes](), [openapi]() ### AI overview This tutorial explains how Kubernetes client-side and server-side apply handle shared object state. It focuses on field ownership, API server interactions, and how different tools can overwrite or preserve changes. ### Source excerpt Client-side apply can silently overwrite changes made by other tools. Server-side apply moves field ownership to the API server. Here is how it works and why it matters. ## A new pkg.go.dev API for Go DevFeed: [A new pkg.go.dev API for Go]() Original publisher: [Read original article]() Author: Google Open Source (noreply@blogger.com) Published: 2026-06-12T18:30:00Z Content type: release Language: en Sources: [Google Open Source Blog]() Topics: [API](), [Go Language](), [JSON](), [OpenAPI Specification](), [Command-line interface](), [AI-assisted coding]() Tags: [agents](), [ai-assisted-coding](), [api](), [developer-tools](), [go](), [json](), [open-source](), [openapi](), [pkg-go-dev]() ### AI overview The Go Team introduces a structured API for pkg.go.dev, providing programmatic access to Go package metadata. The stateless, GET-only API returns JSON metadata, is currently available under a v1beta path, and is intended to evolve toward a formal v1 release after community feedback and stability validation. ### Source excerpt by Ethan Lee, Jonathan Amsterdam & Hana Kim, Go Team Access to Go metadata has been an everpresent need for the Go community. Since its launch, pkg.go.dev has served as a central hub for Go package documentation and discovery. While we initially prioritized providing this comprehensive access via a web interface, the need for streamlined programmatic access has become increasingly clear. Structured API access has been one of the most highly requested features for pkg.go.dev for a while now. Developers building tools, IDE integrations, automated workflows, and other systems have had to rely on inconsistent and fragile scraping methods. By providing a formal API, we can provide fast and efficient access to required data. This foundation also sets Go up for the future of AI-assisted coding. Large language models and agents can access the context necessary to reason about the Go ecosystem with greater precision and accuracy. Empowering Tool Builders Our goal with this API is to reduce the technical churn for builders and innovators. By offering structured JSON metadata, we address the following use cases: Search and Discovery: The API enables fast and efficient search across the entire Go module ecosystem. Driving AI Innovation: As AI-assisted coding evolves, LLMs and agents need precise context. This API provides the data required for agents and models to reason deterministically about Go packages. The Service Interface Built for stability and efficient caching, the API uses a stateless, GET-only architecture. Primary endpoints are currently hosted under the v1beta path. Following a period of feedback from the Go community and confirmed stability, we intend to transition toward a formal v1 release. For a complete interactive reference of all endpoints, query parameters, and response shapes, see pkg.go.dev/api. The machine-readable API contract is also published directly at pkg.go.dev/v1beta/openapi.yaml. Endpoint Description /v1beta/imported-by/{path} Paths of packages ## OpenAPI, ORM, SVG and Lottie DevFeed: [OpenAPI, ORM, SVG and Lottie]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-06-01T00:00:00Z Content type: release Language: en Sources: [CodeName One]() Topics: [OpenAPI Specification](), [Code generation](), [SQLite](), [Object-relational mapping](), [JSON](), [XML](), [SVG](), [ASP.NET Core](), [FastAPI](), [Nest]() Tags: [build](), [fastapi](), [http](), [java](), [json](), [lottie](), [maven-plugin](), [net](), [openapi](), [orm](), [rest](), [spring](), [svg](), [xml]() ### AI overview A Codename One release follow-up describes a shared build-time code generation pipeline for OpenAPI client generation, a SQLite ORM, JSON and XML mappers, SVG and Lottie transcoders, and a declarative router. The pipeline emits typed Java from annotations or declarative source files without reflection. ### Source excerpt An OpenAPI client generator, a JPA-shaped SQLite ORM, JAXB-shaped JSON / XML mappers, build-time SVG / Lottie transcoders, and a declarative router with deep links. All on the same build-time codegen pipeline. ## Generating a Pulumi Provider from an OpenAPI Spec DevFeed: [Generating a Pulumi Provider from an OpenAPI Spec]() Original publisher: [Read original article]() Author: Luke Ward Published: 2026-05-28T00:00:00Z Content type: release Language: en Sources: [Pulumi]() Topics: [OpenAPI Specification](), [Infrastructure as code](), [API](), [SDKs]() Tags: [api](), [iac](), [infrastructure-as-code](), [openapi](), [product](), [pulumi](), [pulumi-cloud](), [release]() ### AI overview Pulumi announces version 1.0 of the Pulumi Service Provider, generated from the Pulumi Cloud OpenAPI specification. The release expands the provider's resource surface and adds infrastructure-as-code support for fine-grained RBAC, Pulumi IDP catalogs, and audit-log export. ### Source excerpt Today, we are announcing v1.0 of the Pulumi Service Provider: a major milestone in managing Pulumi Cloud with Pulumi itself. The provider is now generated directly from the Pulumi Cloud OpenAPI specification, unlocking a dramatically expanded pulumiservice:api/* resource surface and enabling Pulumi Cloud capabilities to become available in the provider faster than ever before. This release also brings several major new capabilities to infrastructure as code, including fine-grained RBAC as code, Pulumi IDP as code, and audit log export as IaC. Together, these changes make the Pulumi Service Provider the most powerful and extensible way yet to manage and automate your Pulumi Cloud infrastructure. Why this matters for users Historically, every new Pulumi Cloud feature implied a follow-up PR in the provider before that feature could be used from a Pulumi program. The provider was always slightly behind the API it wrapped, and entirely new capability areas could take months to land. The api/* surface changes both timelines. Because the schema is derived from the OpenAPI spec at runtime: Whole new resource families land in the provider the same release they reach Pulumi Cloud. New fields, features, and enum values on existing resources show up across all five language SDKs the soon after they appear in the spec. What's new in v1.0 v1.0 lifts whole capability areas of Pulumi Cloud into the api/* surface, not just incremental field additions. None of it required bespoke provider code. Fine-grained RBAC as code. Custom roles, organization membership, and team role assignments are now managed resources. For example, defining a read-only role and assigning it to a team: const readOnly = new ps.api.Role("readOnly", { orgName: "acme", name: "stack-reader", description: "Read-only access to stacks across the org.", uxPurpose: "role", details: { __type: "PermissionDescriptorAllow", permissions: ["stack:read", "stack:list"], }, }); new ps.api.teams.Role("readOnlyForPlatform", { org [Next page]()