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

## .NET 11 : ASP.NET Core: Union Type Support, OpenAPI 3.2 by Default and Blazor AI Components

DevFeed: [.NET 11 : ASP.NET Core: Union Type Support, OpenAPI 3.2 by Default and Blazor AI Components](<https://devfeed.tech/articles/net-11-asp-net-core-union-type-support-openapi-3-2-by-default-and-blazor-ai-components-143688.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/11/asp-net-11-release/>)

Author: Almir Vuk

Published: 2026-11-19T11:27:00Z

Content type: article

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [ASP.NET Core](<https://devfeed.tech/topics/asp-net-core.md>), [Blazor](<https://devfeed.tech/topics/blazor.md>), [SignalR](<https://devfeed.tech/topics/signalr.md>), [Minimal API](<https://devfeed.tech/topics/minimal-api.md>), [OpenAPI Specification](<https://devfeed.tech/topics/openapi.md>), [union types](<https://devfeed.tech/topics/union-types.md>), [.NET](<https://devfeed.tech/topics/net.md>)

Tags: [apis](<https://devfeed.tech/tags/apis.md>), [asp-net](<https://devfeed.tech/tags/asp-net.md>), [asp-net-11-release](<https://devfeed.tech/tags/asp-net-11-release.md>), [asp-net-core](<https://devfeed.tech/tags/asp-net-core.md>), [asynchronous](<https://devfeed.tech/tags/asynchronous.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [blazor](<https://devfeed.tech/tags/blazor.md>), [c-sharp](<https://devfeed.tech/tags/c-sharp.md>), [components](<https://devfeed.tech/tags/components.md>), [development](<https://devfeed.tech/tags/development.md>), [experimental](<https://devfeed.tech/tags/experimental.md>), [json](<https://devfeed.tech/tags/json.md>), [minimal](<https://devfeed.tech/tags/minimal.md>), [net](<https://devfeed.tech/tags/net.md>), [net-10](<https://devfeed.tech/tags/net-10.md>), [net-11](<https://devfeed.tech/tags/net-11.md>), [net-9](<https://devfeed.tech/tags/net-9.md>), [news](<https://devfeed.tech/tags/news.md>), [openapi](<https://devfeed.tech/tags/openapi.md>), [refresh](<https://devfeed.tech/tags/refresh.md>), [signalr](<https://devfeed.tech/tags/signalr.md>), [ssr](<https://devfeed.tech/tags/ssr.md>), [union](<https://devfeed.tech/tags/union.md>), [validation](<https://devfeed.tech/tags/validation.md>), [zstandard](<https://devfeed.tech/tags/zstandard.md>)

### AI overview

ASP.NET Core in .NET 11 adds C# 15 union types for JSON request and response bodies in Minimal APIs and MVC, asynchronous Minimal API validation, and OpenAPI 3.2 generation by default. Union binding is limited to JSON bodies, and OpenAPI 3.2 depends on Microsoft.OpenApi 3.3.1, which the release notes identify as a breaking change. SignalR can refresh authentication without closing long-lived connections; setup is per hub on the server, while .NET refreshes automatically by default and TypeScript can also do so. Blazor adds cached component markup, default client-side validation for static SSR forms, and opt-in circuit pausing for hidden tabs. Its experimental AI components remain prerelease throughout .NET 11. Zstandard compression is enabled by default. The release also includes Kestrel and other API changes, with .NET 11 described as a two-year Standard Term Support release.

### Source excerpt

Microsoft has released ASP.NET Core in .NET 11. The update adds C# union type support in JSON bodies, asynchronous validation for Minimal APIs, OpenAPI 3.2 by default, and SignalR authentication refresh. Blazor gains a CacheView component, client-side validation for static SSR forms, opt-in circuit pause for inactive tabs, and experimental AI components. Zstandard compression is on by default. By Almir Vuk

## OVHcloud AI Summit 2026: 55 launches to take AI into production

DevFeed: [OVHcloud AI Summit 2026: 55 launches to take AI into production](<https://devfeed.tech/articles/ovhcloud-ai-summit-2026-55-launches-to-take-ai-into-production-144298.md>)

Original publisher: [Read original article](<https://blog.ovhcloud.com/en/posts/ai-summit-2026-announcements/>)

Author: OVHcloud Team

Published: 2026-11-19T06:30:00Z

Content type: article

Language: en

Sources: [OVHcloud Blog](<https://devfeed.tech/sources/ovhcloud-blog.md>)

Topics: [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [Amazon Bedrock AgentCore](<https://devfeed.tech/topics/amazon-bedrock-agentcore.md>), [model-deployment](<https://devfeed.tech/topics/model-deployment.md>), [The Three Main Cloud Service Models](<https://devfeed.tech/topics/the-three-main-cloud-service-models.md>), [Amazon Bedrock Knowledge Bases](<https://devfeed.tech/topics/amazon-bedrock-knowledge-bases.md>), [Internationalization (i18n)](<https://devfeed.tech/topics/i18n.md>), [OpenAPI Specification](<https://devfeed.tech/topics/openapi.md>)

Tags: [17](<https://devfeed.tech/tags/17.md>), [2026](<https://devfeed.tech/tags/2026.md>), [accessible](<https://devfeed.tech/tags/accessible.md>), [act](<https://devfeed.tech/tags/act.md>), [actions](<https://devfeed.tech/tags/actions.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [agentic-platform](<https://devfeed.tech/tags/agentic-platform.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-act](<https://devfeed.tech/tags/ai-act.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [gpus](<https://devfeed.tech/tags/gpus.md>), [launches](<https://devfeed.tech/tags/launches.md>), [ovhcloud](<https://devfeed.tech/tags/ovhcloud.md>), [product-news](<https://devfeed.tech/tags/product-news.md>), [production](<https://devfeed.tech/tags/production.md>), [summit](<https://devfeed.tech/tags/summit.md>), [workspace](<https://devfeed.tech/tags/workspace.md>)

### AI overview

OVHcloud announced 55 launches at its 19 November 2026 AI Summit: 38 across cloud foundations and 17 spanning the AI stack. The excerpt emphasizes private networking and security features intended to support production workloads, alongside GPUs, orchestration, inference routing, agents, search, and applications. Olala 1.0 mini 7A1B is an open model with 7 billion parameters and 1 billion active per request; OVHcloud says it can run on an 8 GB GPU or a standard CPU and plans to release it under Apache 2.0. OVHai Workspace combines productivity, website creation, and company-data search; its free alpha launched in France with 5 GB per user, European data hosting, and a commitment not to use customer data for model training. These details describe the supplied excerpt, not necessarily all 55 launches.

### Source excerpt

Olala, OVHai Workspace, GPUs, and AI agents: discover the 55 launches from the OVHcloud AI Summit 2026, and the ones you can try right now.

## CVE-2026-76090 - Tapir: Construction/decode RCE via property name -\> raw case-class field (tapir-openapi-codegen)

DevFeed: [CVE-2026-76090 - Tapir: Construction/decode RCE via property name -\> raw case-class field (tapir-openapi-codegen)](<https://devfeed.tech/articles/cve-2026-76090-tapir-construction-decode-rce-via-property-name-raw-case-class-field-tapir-openapi-codegen-141191.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-76090>)

Author: CVEFEED.io; github.com

Published: 2026-11-18T20:19:12Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [OpenAPI Specification](<https://devfeed.tech/topics/openapi.md>), [identifier](<https://devfeed.tech/topics/identifier.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [apis](<https://devfeed.tech/tags/apis.md>), [build](<https://devfeed.tech/tags/build.md>), [code-generation](<https://devfeed.tech/tags/code-generation.md>), [codegen](<https://devfeed.tech/tags/codegen.md>), [construction](<https://devfeed.tech/tags/construction.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-76090](<https://devfeed.tech/tags/cve-2026-76090.md>), [decode](<https://devfeed.tech/tags/decode.md>), [identifier](<https://devfeed.tech/tags/identifier.md>), [object](<https://devfeed.tech/tags/object.md>), [openapi](<https://devfeed.tech/tags/openapi.md>), [parameter](<https://devfeed.tech/tags/parameter.md>), [property](<https://devfeed.tech/tags/property.md>), [query](<https://devfeed.tech/tags/query.md>), [rce](<https://devfeed.tech/tags/rce.md>), [scala](<https://devfeed.tech/tags/scala.md>), [server](<https://devfeed.tech/tags/server.md>), [source](<https://devfeed.tech/tags/source.md>), [validation](<https://devfeed.tech/tags/validation.md>)

### AI overview

Before version 1.13.27, tapir-openapi-codegen-core interpolated untrusted OpenAPI property names, parameter names, and operation tags into generated Scala without context-appropriate validation or escaping. Crafted input could inject Scala that executes when generated code is compiled or endpoints are assembled. The issue affects code generation and build-time use; the excerpt says it does not directly expose a running Tapir server. It identifies 1.13.27 as the fix, but lists no affected product versions.

### Source excerpt

CVE ID :CVE-2026-76090 Published : Nov. 18, 2026, 8:19 p.m. | 34 minutes ago Description :Tapir is a Scala library for describing HTTP APIs and exposing, consuming, and documenting them using open standards. Prior to 1.13.27, tapir-openapi-codegen-core generates Scala source from untrusted OpenAPI documents by interpolating object property names, query, header, and path parameter names, and operation tags without context-appropriate validation or escaping. Crafted names or values can break out of generated identifier or string-literal contexts and inject arbitrary Scala that executes when generated code is compiled or endpoints are assembled. This is a code-generation and build-time issue and does not make a running tapir server directly exploitable. This issue is fixed in version 1.13.27. Severity: 8.4 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## How to Expose Internal APIs to AI Agents Safely

DevFeed: [How to Expose Internal APIs to AI Agents Safely](<https://devfeed.tech/articles/how-to-expose-internal-apis-to-ai-agents-safely-141963.md>)

Original publisher: [Read original article](<https://www.swytchcode.com/content/expose-internal-apis-to-ai-agents-safely>)

Author: Swytchcode Team

Published: 2026-11-18T00:00:00Z

Content type: article

Language: en

Sources: [Swytchcode](<https://devfeed.tech/sources/swytchcode.md>)

Topics: [API Governance](<https://devfeed.tech/topics/api-governance.md>), [OpenAPI Specification](<https://devfeed.tech/topics/openapi.md>), [AI Integration Strategies](<https://devfeed.tech/topics/ai-integration-strategies.md>), [human in the loop agent](<https://devfeed.tech/topics/human-in-the-loop-agent.md>), [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [apis](<https://devfeed.tech/tags/apis.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [guardrails](<https://devfeed.tech/tags/guardrails.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [openapi](<https://devfeed.tech/tags/openapi.md>), [policy](<https://devfeed.tech/tags/policy.md>), [safely](<https://devfeed.tech/tags/safely.md>)

### AI overview

Giving an AI agent an internal API spec and a broadly valid service token can make every documented endpoint reachable, even when the task needs only a few. The article recommends importing the OpenAPI spec or Postman collection for discovery, then explicitly allowing methods one at a time with `swy add method`; credentials are stored locally and injected at execution, outside the agent's context or code. It also recommends argument-based policy rules for internal APIs, which may lack the rate limits and abuse controls common on public APIs--for example, requiring human approval for high-value cancellations. The article says requests go directly from the customer's infrastructure without a proxy hop, and that Enterprise deployments run in the customer's chosen AWS, Azure, or GCP region. If neither an OpenAPI spec nor a Postman collection exists, it suggests writing a minimal OpenAPI description for the intended endpoints.

### Source excerpt

Handing an agent your internal OpenAPI spec and a service token exposes every endpoint by default. A curated, method-by-method allowlist plus policy guardrails is the safer default for APIs that were never built expecting an AI caller.

## Microsoft Releases .NET 11: C# 15 Union Types, Native AOT CLI Host, and CoreCLR by Default in MAUI

DevFeed: [Microsoft Releases .NET 11: C# 15 Union Types, Native AOT CLI Host, and CoreCLR by Default in MAUI](<https://devfeed.tech/articles/microsoft-releases-net-11-c-15-union-types-native-aot-cli-host-and-coreclr-by-default-in-maui-137153.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/11/dotnet-11-release/>)

Author: Almir Vuk

Published: 2026-11-17T11:50:00Z

Content type: news

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [.NET](<https://devfeed.tech/topics/net.md>), [C#](<https://devfeed.tech/topics/csharp.md>), [union types](<https://devfeed.tech/topics/union-types.md>), [ASP.NET Core](<https://devfeed.tech/topics/asp-net-core.md>), [ASP.NET](<https://devfeed.tech/topics/aspnet.md>), [Closed hierarchies](<https://devfeed.tech/topics/closed-hierarchies.md>), [native aot](<https://devfeed.tech/topics/native-aot.md>), [.NET MAUI](<https://devfeed.tech/topics/net-maui.md>), [releases](<https://devfeed.tech/topics/releases.md>), [OpenAPI Specification](<https://devfeed.tech/topics/openapi.md>), [efcore](<https://devfeed.tech/topics/efcore.md>), [SignalR](<https://devfeed.tech/topics/signalr.md>)

Tags: [aot](<https://devfeed.tech/tags/aot.md>), [c-sharp](<https://devfeed.tech/tags/c-sharp.md>), [c-sharp-15](<https://devfeed.tech/tags/c-sharp-15.md>), [c-sharp-15-union-types](<https://devfeed.tech/tags/c-sharp-15-union-types.md>), [cli](<https://devfeed.tech/tags/cli.md>), [coreclr](<https://devfeed.tech/tags/coreclr.md>), [development](<https://devfeed.tech/tags/development.md>), [dotnet-11-release](<https://devfeed.tech/tags/dotnet-11-release.md>), [maui](<https://devfeed.tech/tags/maui.md>), [microsoft](<https://devfeed.tech/tags/microsoft.md>), [native](<https://devfeed.tech/tags/native.md>), [native-aot](<https://devfeed.tech/tags/native-aot.md>), [net](<https://devfeed.tech/tags/net.md>), [net-10](<https://devfeed.tech/tags/net-10.md>), [net-11](<https://devfeed.tech/tags/net-11.md>), [net-11-c-sharp](<https://devfeed.tech/tags/net-11-c-sharp.md>), [net-9](<https://devfeed.tech/tags/net-9.md>), [net-maui](<https://devfeed.tech/tags/net-maui.md>), [news](<https://devfeed.tech/tags/news.md>), [releases](<https://devfeed.tech/tags/releases.md>), [types](<https://devfeed.tech/tags/types.md>), [union](<https://devfeed.tech/tags/union.md>), [union-types](<https://devfeed.tech/tags/union-types.md>)

### AI overview

Microsoft's .NET 11 is an STS release supported for two years; .NET 10 remains the LTS option. C# 15 adds union types with compiler-checked exhaustive switch expressions and closed hierarchies, alongside collection expression arguments and extension indexers. The SDK uses a Native AOT CLI host by default and keeps the MSBuild server warm; Runtime Async remains preview-only and requires a feature flag. ASP.NET Core adds asynchronous validation and defaults to OpenAPI 3.2, a listed breaking change. MAUI switches its default runtime to CoreCLR, while Mono remains available and Native AOT is opt-in. EF Core 11 requires .NET 11 and adds experimental vector search for SQL Server. The release also raises minimum hardware requirements, including an x86-64-v2 baseline.

### Source excerpt

Microsoft has released .NET 11, a Standard Term Support release with two years of support. It ships C# 15 with union types and closed hierarchies, a Native AOT CLI host, a preview of Runtime Async, Zstandard compression, asynchronous validation and OpenAPI 3.2 in ASP.NET Core, CoreCLR as the default runtime in .NET MAUI, and EF Core 11 with experimental vector search. By Almir Vuk

## What's new in Postman: Kafka, MCP tests, RAML

DevFeed: [What's new in Postman: Kafka, MCP tests, RAML](<https://devfeed.tech/articles/what-s-new-in-postman-kafka-mcp-tests-raml-133540.md>)

Original publisher: [Read original article](<https://blog.postman.com/whats-new-in-postman-kafka-mcp-tests-raml/>)

Author: Quinton Wall

Published: 2026-11-13T16:20:26Z

Content type: release

Language: en

Sources: [Postman](<https://devfeed.tech/sources/postman-blog.md>)

Topics: [Postman](<https://devfeed.tech/topics/postman.md>), [Apache Kafka](<https://devfeed.tech/topics/apache-kafka.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [OpenAPI Specification](<https://devfeed.tech/topics/openapi.md>), [Postman Agent Mode](<https://devfeed.tech/topics/postman-agent-mode.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [advanced-security](<https://devfeed.tech/tags/advanced-security.md>), [agent-mode](<https://devfeed.tech/tags/agent-mode.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [api](<https://devfeed.tech/tags/api.md>), [apis](<https://devfeed.tech/tags/apis.md>), [asyncapi](<https://devfeed.tech/tags/asyncapi.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-iam](<https://devfeed.tech/tags/aws-iam.md>), [blog](<https://devfeed.tech/tags/blog.md>), [connect](<https://devfeed.tech/tags/connect.md>), [general](<https://devfeed.tech/tags/general.md>), [kafka](<https://devfeed.tech/tags/kafka.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [openapi](<https://devfeed.tech/tags/openapi.md>), [post](<https://devfeed.tech/tags/post.md>), [postman](<https://devfeed.tech/tags/postman.md>), [runner](<https://devfeed.tech/tags/runner.md>), [scripts](<https://devfeed.tech/tags/scripts.md>), [spec-hub](<https://devfeed.tech/tags/spec-hub.md>), [tests](<https://devfeed.tech/tags/tests.md>), [what-s-new](<https://devfeed.tech/tags/what-s-new.md>)

### AI overview

Postman brings Kafka and MCP requests into multi-protocol collections and adds RAML 1.0 and OpenAPI 3.2 support in Spec Hub. Kafka requests can produce and consume topic messages, use SASL, AWS IAM or mTLS, and run scripts and tests alongside HTTP steps; bounded consumption lets reads finish without waiting indefinitely. Kafka requests are free, while running them in the Collection Runner or Postman CLI requires Solo, Team or Enterprise. MCP scripts and tests are available on every plan, including Free and Consumption Pricing, with hooks for connection setup, server checks, per-call results and disconnect; test results are grouped by phase. Spec Hub can import RAML projects, resolve includes and libraries, generate synced collections, and author or validate OpenAPI 3.2 specs with two-way collection sync and governance linting. The post also reports cross-region domain capture for Enterprise customers with Advanced Security Administration; it routes users to allowed teams without moving data.

### Source excerpt

Postman now supports Kafka requests, MCP scripts and tests, RAML 1.0, and OpenAPI 3.2. See what shipped and try it in the Collection Runner. The post What's new in Postman: Kafka, MCP tests, RAML appeared first on Postman Blog.

## Laravel Rest Api 3.0: Typed Fields, Metrics, and OpenAPI Docs

DevFeed: [Laravel Rest Api 3.0: Typed Fields, Metrics, and OpenAPI Docs](<https://devfeed.tech/articles/laravel-rest-api-3-0-typed-fields-metrics-and-openapi-docs-126628.md>)

Original publisher: [Read original article](<https://laravel-news.com/laravel-rest-api-3>)

Author: Eric L. Barnes

Published: 2026-11-10T13:33:18Z

Content type: release

Language: en

Sources: [Laravel](<https://devfeed.tech/sources/laravel.md>)

Topics: [REST API](<https://devfeed.tech/topics/rest-api.md>), [Laravel](<https://devfeed.tech/topics/laravel.md>), [OpenAPI Specification](<https://devfeed.tech/topics/openapi.md>), [Eloquent ORM](<https://devfeed.tech/topics/eloquent.md>)

Tags: [3](<https://devfeed.tech/tags/3.md>), [actions](<https://devfeed.tech/tags/actions.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-assistant](<https://devfeed.tech/tags/ai-assistant.md>), [algolia](<https://devfeed.tech/tags/algolia.md>), [api](<https://devfeed.tech/tags/api.md>), [count](<https://devfeed.tech/tags/count.md>), [counts](<https://devfeed.tech/tags/counts.md>), [docs](<https://devfeed.tech/tags/docs.md>), [eloquent](<https://devfeed.tech/tags/eloquent.md>), [fields](<https://devfeed.tech/tags/fields.md>), [laravel](<https://devfeed.tech/tags/laravel.md>), [laravel-packages](<https://devfeed.tech/tags/laravel-packages.md>), [metric](<https://devfeed.tech/tags/metric.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [openapi](<https://devfeed.tech/tags/openapi.md>), [package](<https://devfeed.tech/tags/package.md>), [rest](<https://devfeed.tech/tags/rest.md>), [rest-api](<https://devfeed.tech/tags/rest-api.md>), [scramble](<https://devfeed.tech/tags/scramble.md>)

### AI overview

Laravel Rest Api 3.0 rebuilds Eloquent-to-REST resources around typed fields: one field declaration governs type-compatible filters, write validation, response values and API documentation. It replaces built-in docs with Scramble's OpenAPI output and tests request examples against the generated document. Resource metrics gain dedicated endpoints for values, trends, partitions, progress and tables, with date ranges, time zones, prior-period comparisons, caching, and access limited to rows the user may see. Actions and writes can require confirmation: the API returns 428 with a message and signed token, then runs the same request when resubmitted with that token. Other changes include per-resource and per-row policy checks, tenant scoping, transactional nested writes, version conflict responses, and queued action batches. Version 3.0 requires PHP 8.3+ and Laravel 13.30+; Laravel 12 users should remain on 2.x. The excerpt notes breaking changes and refers to an upgrade guide.

### Source excerpt

Laravel Rest Api 3.0 rebuilds the package around typed fields, adds metric endpoints and write confirmations, and documents your API with Scramble. The post Laravel Rest Api 3.0: Typed Fields, Metrics, and OpenAPI Docs appeared first on Laravel News. Join the Laravel Newsletter to get Laravel articles like this directly in your inbox.

## ClickHouse Managed Postgres goes GA and Xata acquisition brings agentic capabilities to the service

DevFeed: [ClickHouse Managed Postgres goes GA and Xata acquisition brings agentic capabilities to the service](<https://devfeed.tech/articles/clickhouse-managed-postgres-goes-ga-and-xata-acquisition-brings-agentic-capabilities-to-the-service-124829.md>)

Original publisher: [Read original article](<https://clickhouse.com/blog/managed-postgres-ga-xata-acquisition>)

Author: Sai Srirampur

Published: 2026-11-09T16:56:11Z

Content type: release

Language: en

Sources: [ClickHouse Blog](<https://devfeed.tech/sources/clickhouse-blog.md>)

Topics: [Tinybird news](<https://devfeed.tech/topics/tinybird-news.md>), [Heroku Postgres](<https://devfeed.tech/topics/heroku-postgres.md>), [Heroku AI](<https://devfeed.tech/topics/heroku-ai.md>), [internal developer platform automation](<https://devfeed.tech/topics/internal-developer-platform-automation.md>), [OpenAPI Specification](<https://devfeed.tech/topics/openapi.md>)

Tags: [acquisition](<https://devfeed.tech/tags/acquisition.md>), [agent-memory](<https://devfeed.tech/tags/agent-memory.md>), [agent-sandboxing](<https://devfeed.tech/tags/agent-sandboxing.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-coding-agents](<https://devfeed.tech/tags/ai-coding-agents.md>), [ai-native](<https://devfeed.tech/tags/ai-native.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [automatic](<https://devfeed.tech/tags/automatic.md>), [clickhouse](<https://devfeed.tech/tags/clickhouse.md>), [developers](<https://devfeed.tech/tags/developers.md>), [developers-and-ai](<https://devfeed.tech/tags/developers-and-ai.md>), [instant](<https://devfeed.tech/tags/instant.md>), [managed](<https://devfeed.tech/tags/managed.md>), [nvme](<https://devfeed.tech/tags/nvme.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [scale](<https://devfeed.tech/tags/scale.md>), [zero](<https://devfeed.tech/tags/zero.md>)

### AI overview

ClickHouse Managed Postgres is generally available on AWS, combining local NVMe storage with native ClickHouse analytics connectivity. The excerpt reports 2-10x OLTP performance improvements, WAL-based sub-second replication through WalShadow, and ClickPipes as an included alternative; it also lists high availability, backups, pooling, replicas, observability, and enterprise security features. GCP remains in private preview. GA ends the beta discount and makes backup storage and public network egress billable, while ClickHouse connectivity and ClickPipes replication remain included. The Xata acquisition is intended to add copy-on-write instant branching and cloning, automatic idling, and scale-to-zero for isolated development and AI-agent environments. Existing Xata capabilities are available through customer onboarding; integration into ClickHouse Managed Postgres and a dedicated agent tier are planned, not yet described as launched.

### Source excerpt

ClickHouse Managed Postgres, our NVMe-backed Postgres service natively connected to ClickHouse, is generally available, and we're acquiring Xata to add instant branching, cloning and scale-to-zero for developers and AI agents.

## Postman Plugin for Claude Code: A Hands-On Guide

DevFeed: [Postman Plugin for Claude Code: A Hands-On Guide](<https://devfeed.tech/articles/postman-plugin-for-claude-code-a-hands-on-guide-125770.md>)

Original publisher: [Read original article](<https://blog.postman.com/postman-plugin-for-claude-code-a-hands-on-guide/>)

Author: Quinton Wall

Published: 2026-11-09T16:00:00Z

Content type: tutorial

Language: en

Sources: [Postman](<https://devfeed.tech/sources/postman-blog.md>)

Topics: [Claude Code](<https://devfeed.tech/topics/claude-code.md>), [Postman](<https://devfeed.tech/topics/postman.md>), [OpenAPI Specification](<https://devfeed.tech/topics/openapi.md>), [Postman CLI](<https://devfeed.tech/topics/postman-cli.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [mock api](<https://devfeed.tech/topics/mock-api.md>), [Loop Engineering](<https://devfeed.tech/topics/loop-engineering.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>), [Spec Driven Development](<https://devfeed.tech/topics/spec-driven-development.md>), [hooks](<https://devfeed.tech/topics/hooks.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-native](<https://devfeed.tech/tags/ai-native.md>), [api](<https://devfeed.tech/tags/api.md>), [blog](<https://devfeed.tech/tags/blog.md>), [build](<https://devfeed.tech/tags/build.md>), [claude](<https://devfeed.tech/tags/claude.md>), [claude-code](<https://devfeed.tech/tags/claude-code.md>), [code](<https://devfeed.tech/tags/code.md>), [copy](<https://devfeed.tech/tags/copy.md>), [editor-s-picks](<https://devfeed.tech/tags/editor-s-picks.md>), [editors-recommendations](<https://devfeed.tech/tags/editors-recommendations.md>), [first](<https://devfeed.tech/tags/first.md>), [gate](<https://devfeed.tech/tags/gate.md>), [general](<https://devfeed.tech/tags/general.md>), [guide](<https://devfeed.tech/tags/guide.md>), [hooks](<https://devfeed.tech/tags/hooks.md>), [install](<https://devfeed.tech/tags/install.md>), [mock](<https://devfeed.tech/tags/mock.md>), [native](<https://devfeed.tech/tags/native.md>), [openapi](<https://devfeed.tech/tags/openapi.md>), [plugin](<https://devfeed.tech/tags/plugin.md>), [post](<https://devfeed.tech/tags/post.md>), [postman](<https://devfeed.tech/tags/postman.md>), [postman-plugin](<https://devfeed.tech/tags/postman-plugin.md>)

### AI overview

The Postman plugin for Claude Code routes API work through Postman CLI skills, from discovery and contract design to mocks, tests, readiness scoring, and CI checks. The guide recommends keeping an OpenAPI spec and v3 collection in the repository, linting changes, and using a deterministic CI gate; local lint, mock, and collection commands do not require Postman sign-in, while cloud features do. Discovery searches Postman resources by ownership scope, Orbit finds third-party provider candidates but does not supply credentials, and Context Graph can identify endpoint consumers but not which fields they use. Mocks can exercise failure cases, though they do not prove the implementation works and do not hot-reload. Claude Code plan mode, hooks, subagents, and bounded `/goal` loops can make the process more repeatable; token and turn limits help constrain loops. The guide also cautions that CLI flags vary by version and some commands report results or analytics to Postman by default.

### Source excerpt

Install the Postman plugin for Claude Code, then build, mock, test, and gate an AI-native API with copy-paste prompts, hooks, and /goal. The post Postman Plugin for Claude Code: A Hands-On Guide appeared first on Postman Blog.

## Governing Apache Ossie Semantic Models in Apache Polaris: APIs, Privileges, and Scope

DevFeed: [Governing Apache Ossie Semantic Models in Apache Polaris: APIs, Privileges, and Scope](<https://devfeed.tech/articles/governing-apache-ossie-semantic-models-in-apache-polaris-apis-privileges-and-scope-123563.md>)

Original publisher: [Read original article](<https://www.dremio.com/blog/governing-apache-ossie-semantic-models-in-apache-polaris-apis-privileges-and-scope/>)

Author: Alex Merced

Published: 2026-11-09T13:42:10Z

Content type: article

Language: en

Sources: [Dremio](<https://devfeed.tech/sources/dremio.md>)

Topics: [semantic-layer](<https://devfeed.tech/topics/semantic-layer.md>), [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [API Governance](<https://devfeed.tech/topics/api-governance.md>), [OpenAPI Specification](<https://devfeed.tech/topics/openapi.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [apache-iceberg](<https://devfeed.tech/tags/apache-iceberg.md>), [apache-polaris](<https://devfeed.tech/tags/apache-polaris.md>), [api](<https://devfeed.tech/tags/api.md>), [apis](<https://devfeed.tech/tags/apis.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [audit](<https://devfeed.tech/tags/audit.md>), [audit-logs](<https://devfeed.tech/tags/audit-logs.md>), [audit-trail](<https://devfeed.tech/tags/audit-trail.md>), [authoring](<https://devfeed.tech/tags/authoring.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [automate](<https://devfeed.tech/tags/automate.md>), [beta](<https://devfeed.tech/tags/beta.md>), [blast-radius](<https://devfeed.tech/tags/blast-radius.md>), [build](<https://devfeed.tech/tags/build.md>), [data-lakehouse](<https://devfeed.tech/tags/data-lakehouse.md>), [design](<https://devfeed.tech/tags/design.md>), [dremio-blog-open-data-insights](<https://devfeed.tech/tags/dremio-blog-open-data-insights.md>), [models](<https://devfeed.tech/tags/models.md>), [scope](<https://devfeed.tech/tags/scope.md>), [semantic](<https://devfeed.tech/tags/semantic.md>), [semantic-models](<https://devfeed.tech/tags/semantic-models.md>)

### AI overview

Polaris 1.8 offers beta REST endpoints for governing Apache Ossie semantic-model objects; they are disabled by default and may change. The endpoints apply Polaris role-based privileges to model operations at scopes from global or catalog down to namespace or individual object. Model privileges remain separate from Iceberg dataset permissions, so creating or publishing a model does not grant access to its referenced data. The excerpt recommends a staged author, review, and publish workflow: give authors draft permissions, reviewers read and validation access, and publishers explicit rights at the narrowest workable scope, with dataset-access checks before production publication. It also recommends verifying configuration keys and privilege semantics in Polaris documentation, testing CRUD and publish behavior in staging, and pinning client-server versions with compatibility checks during beta.

### Source excerpt

Enable and govern Apache Ossie semantic models in Apache Polaris, understand beta APIs and privilege scopes, and design a controlled publication workflow. The post Governing Apache Ossie Semantic Models in Apache Polaris: APIs, Privileges, and Scope appeared first on Dremio.

## CVE-2026-77596 - Kubeflow Pipelines API server lacks authorization for shared pipeline uploads

DevFeed: [CVE-2026-77596 - Kubeflow Pipelines API server lacks authorization for shared pipeline uploads](<https://devfeed.tech/articles/cve-2026-77596-kubeflow-pipelines-api-server-lacks-authorization-for-shared-pipeline-uploads-119713.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-77596>)

Author: CVEFEED.io; github.com

Published: 2026-11-05T23:17:00Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [api server](<https://devfeed.tech/topics/api-server.md>), [OpenAPI Specification](<https://devfeed.tech/topics/openapi.md>), [TFX](<https://devfeed.tech/topics/tfx.md>), [MLOps](<https://devfeed.tech/topics/mlops.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [api](<https://devfeed.tech/tags/api.md>), [api-server](<https://devfeed.tech/tags/api-server.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-77596](<https://devfeed.tech/tags/cve-2026-77596.md>), [cvss](<https://devfeed.tech/tags/cvss.md>), [deploy](<https://devfeed.tech/tags/deploy.md>), [deployments](<https://devfeed.tech/tags/deployments.md>), [exploit](<https://devfeed.tech/tags/exploit.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [http](<https://devfeed.tech/tags/http.md>), [issue](<https://devfeed.tech/tags/issue.md>), [kubeflow](<https://devfeed.tech/tags/kubeflow.md>), [latest](<https://devfeed.tech/tags/latest.md>), [learning](<https://devfeed.tech/tags/learning.md>), [machine](<https://devfeed.tech/tags/machine.md>), [pipeline](<https://devfeed.tech/tags/pipeline.md>), [pipelines](<https://devfeed.tech/tags/pipelines.md>), [uploads](<https://devfeed.tech/tags/uploads.md>)

### AI overview

Before Kubeflow Pipelines 2.18.0, two multi-user upload endpoints can bypass SubjectAccessReview when the target namespace is empty and REQUIRE_NAMESPACE_FOR_PIPELINES is false. A low-privilege tenant can create shared pipelines or inject versions without write permission; an unauthenticated caller can do so only when the API server is directly reachable without an authenticating proxy. An enabled recurring run that follows the latest version may execute an injected specification in another tenant's namespace under that workload's service account. Runs pinned to a version or using an embedded specification are not automatically substituted. The issue is fixed in version 2.18.0.

### Source excerpt

CVE ID :CVE-2026-77596 Published : Nov. 5, 2026, 11:17 p.m. | 2 hours, 30 minutes ago Description :Kubeflow Pipelines enables users to build and deploy portable, scalable machine learning workflows. Prior to 2.18.0, the multi-user HTTP endpoints POST /apis/v2beta1/pipelines/upload and POST /apis/v2beta1/pipelines/upload_version call canUploadVersionedPipeline, which returns without SubjectAccessReview when the target namespace is empty while REQUIRE_NAMESPACE_FOR_PIPELINES defaults to false. A low-privilege tenant can create shared pipelines or inject attacker-controlled versions into existing shared pipelines without the required write permission; if the API server is directly reachable without an authenticating proxy, an unauthenticated caller can exploit the same bypass, while deployments protected by such a proxy do not expose anonymous access. An enabled unpinned recurring run that follows the latest version can then execute the injected specification in another tenant's namespace under that workload's service account, while pinned or embedded-specification runs are not automatically substituted. This issue is fixed in version 2.18.0. Severity: 9.6 | CRITICAL Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## 6 of the Best Company Enrichment APIs in 2026 (A Benchmark-Based Comparison)

DevFeed: [6 of the Best Company Enrichment APIs in 2026 (A Benchmark-Based Comparison)](<https://devfeed.tech/articles/6-of-the-best-company-enrichment-apis-in-2026-a-benchmark-based-comparison-119317.md>)

Original publisher: [Read original article](<https://hackernoon.com/6-of-the-best-company-enrichment-apis-in-2026-a-benchmark-based-comparison?source=rss>)

Author: CompanyEnrich

Published: 2026-11-05T16:36:10Z

Content type: comparison

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Benchmark](<https://devfeed.tech/topics/benchmark.md>), [OpenAPI Specification](<https://devfeed.tech/topics/openapi.md>), [API Economy](<https://devfeed.tech/topics/api-economy.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [api](<https://devfeed.tech/tags/api.md>), [apis](<https://devfeed.tech/tags/apis.md>), [b2b-data-enrichment](<https://devfeed.tech/tags/b2b-data-enrichment.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [company](<https://devfeed.tech/tags/company.md>), [company-data-api](<https://devfeed.tech/tags/company-data-api.md>), [company-data-providers](<https://devfeed.tech/tags/company-data-providers.md>), [company-enrichment-api](<https://devfeed.tech/tags/company-enrichment-api.md>), [companyenrich](<https://devfeed.tech/tags/companyenrich.md>), [comparison](<https://devfeed.tech/tags/comparison.md>), [coverage](<https://devfeed.tech/tags/coverage.md>), [data](<https://devfeed.tech/tags/data.md>), [data-enrichment](<https://devfeed.tech/tags/data-enrichment.md>), [domains](<https://devfeed.tech/tags/domains.md>), [enrichment](<https://devfeed.tech/tags/enrichment.md>), [fields](<https://devfeed.tech/tags/fields.md>), [good-company](<https://devfeed.tech/tags/good-company.md>), [lead-enrichment](<https://devfeed.tech/tags/lead-enrichment.md>), [profile](<https://devfeed.tech/tags/profile.md>)

### AI overview

In CompanyEnrich's published comparison of six APIs on 349 DNS-checked alphabetic .com domains, CompanyEnrich led overall find rate and average profile depth, but competitors led specific fields: People Data Labs had higher employee-count presence and led LinkedIn URL and corporate-relationship coverage. The benchmark measured field presence, not accuracy, and did not rank price or latency. Choose by defining required fields and a usable-record threshold, then test identical samples from your target market. Check identity, field meanings, matching settings, endpoint defaults and request bundles; measure records meeting acceptance criteria, full workflow cost and latency. Provider-specific caveats include CompanyEnrich's asynchronous 404 path when data is not stored, People Data Labs' match threshold and required-field controls, and APIs that may return empty results or multiple candidates.

### Source excerpt

Compare six company enrichment APIs using benchmark data from 349 domains. Explore coverage, profile depth, and key fields to find the right API for your workfl

## MongoDB CDC connector for ClickPipes is now generally available

DevFeed: [MongoDB CDC connector for ClickPipes is now generally available](<https://devfeed.tech/articles/mongodb-cdc-connector-for-clickpipes-is-now-generally-available-117630.md>)

Original publisher: [Read original article](<https://clickhouse.com/blog/mongodb-cdc-connector-clickpipes-ga>)

Author: Marta Paes

Published: 2026-11-04T17:46:41Z

Content type: release

Language: en

Sources: [ClickHouse Blog](<https://devfeed.tech/sources/clickhouse-blog.md>)

Topics: [MongoDB](<https://devfeed.tech/topics/mongodb.md>), [streaming data analytics](<https://devfeed.tech/topics/streaming-data-analytics.md>), [releases](<https://devfeed.tech/topics/releases.md>), [Prometheus](<https://devfeed.tech/topics/prometheus.md>), [OpenAPI Specification](<https://devfeed.tech/topics/openapi.md>)

Tags: [cdc](<https://devfeed.tech/tags/cdc.md>), [lag](<https://devfeed.tech/tags/lag.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [mongodb](<https://devfeed.tech/tags/mongodb.md>), [openapi](<https://devfeed.tech/tags/openapi.md>), [parallel](<https://devfeed.tech/tags/parallel.md>), [resource](<https://devfeed.tech/tags/resource.md>), [structured](<https://devfeed.tech/tags/structured.md>), [terraform](<https://devfeed.tech/tags/terraform.md>)

### AI overview

MongoDB CDC ClickPipes is generally available for ClickHouse Cloud, using MongoDB Change Streams for near-real-time replication. GA adds automatic parallel snapshots partitioned by `_id`, with sampled boundaries to balance uneven collections. Structured ingestion is optional: it infers a schema and maps top-level fields to typed columns; unknown fields and type mismatches are retained in `_peerdb_malformed_data`. Deeper flattening is not yet supported. Users can configure target fields, partitioning, sorting keys, enable collection pre-images for deletes, or filter deletes to retain history. New CPU, memory, network, and source, destination, and end-to-end lag metrics are available in the UI and Prometheus endpoint. OpenAPI and Terraform management require Terraform v3.14.0 or later. Billing began November 4, 2026; the connector is available in all ClickHouse Cloud service tiers.

### Source excerpt

The MongoDB CDC connector for ClickPipes is now generally available, with parallel snapshotting, structured ingestion into typed columns, lag and resource metrics, and Terraform and OpenAPI support.

## Cisco IQ: Engineering APIs for the Agentic Era

DevFeed: [Cisco IQ: Engineering APIs for the Agentic Era](<https://devfeed.tech/articles/cisco-iq-engineering-apis-for-the-agentic-era-117180.md>)

Original publisher: [Read original article](<https://blogs.cisco.com/customerexperience/cisco-iq-engineering-apis-for-the-agentic-era>)

Author: Bhaskar Jayakrishnan

Published: 2026-11-04T17:30:28Z

Content type: article

Language: en

Sources: [Cisco Blogs](<https://devfeed.tech/sources/cisco-blogs.md>)

Topics: [AI Integration Strategies](<https://devfeed.tech/topics/ai-integration-strategies.md>), [API Governance](<https://devfeed.tech/topics/api-governance.md>), [OpenAPI Specification](<https://devfeed.tech/topics/openapi.md>), [Cisco](<https://devfeed.tech/topics/cisco.md>)

Tags: [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [api](<https://devfeed.tech/tags/api.md>), [apis](<https://devfeed.tech/tags/apis.md>), [canonical](<https://devfeed.tech/tags/canonical.md>), [cisco](<https://devfeed.tech/tags/cisco.md>), [cisco-customer-experience](<https://devfeed.tech/tags/cisco-customer-experience.md>), [cisco-iq](<https://devfeed.tech/tags/cisco-iq.md>), [cisco-services](<https://devfeed.tech/tags/cisco-services.md>), [correlation](<https://devfeed.tech/tags/correlation.md>), [developers](<https://devfeed.tech/tags/developers.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [guardrails](<https://devfeed.tech/tags/guardrails.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-server](<https://devfeed.tech/tags/mcp-server.md>), [model](<https://devfeed.tech/tags/model.md>), [platform](<https://devfeed.tech/tags/platform.md>)

### AI overview

Cisco IQ describes an API and MCP architecture built from one canonical domain model, so REST contracts, permissions, storage, queries, and agent tools share the same definitions. Its structured query operation handles cross-domain filtering, expansion, and aggregation on the platform; the bulk engine orders multi-entity changes and reports partial successes. The MCP server exposes four model-derived tools--discover, describe, query, and mutate--and agents use the calling principal's existing authorization. Queries are validated before execution, with structured errors and corrected payloads; mutations expose prerequisite states for human review. In scripted tests across 17 scenarios, the company reports tool calls falling from 256 to 36 and approval prompts from 181 to 1; standard multi-domain reads took two calls. These are scripted benchmark results, while live-agent measurements are described as forthcoming. Semantic discovery is also planned.

### Source excerpt

Discover how Cisco IQ's APIs and MCP server give developers and AI agents one canonical model, deterministic guardrails, and platform-level correlation.

## WAR-CRAFT: Refining Web API Recommendations through Requirement Auditing

DevFeed: [WAR-CRAFT: Refining Web API Recommendations through Requirement Auditing](<https://devfeed.tech/articles/war-craft-refining-web-api-recommendations-through-requirement-auditing-115052.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.00564>)

Author: Zishuo Xu, Dezhong Yao, Zhiqiang Xu

Published: 2026-11-03T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Artificial Intelligence](<https://devfeed.tech/sources/arxiv-artificial-intelligence.md>)

Topics: [API](<https://devfeed.tech/topics/api.md>), [audit](<https://devfeed.tech/topics/audit.md>), [AI Foundation Models](<https://devfeed.tech/topics/ai-foundation-models.md>), [OpenAPI Specification](<https://devfeed.tech/topics/openapi.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [apis](<https://devfeed.tech/tags/apis.md>), [auditing](<https://devfeed.tech/tags/auditing.md>), [audits](<https://devfeed.tech/tags/audits.md>), [capabilities](<https://devfeed.tech/tags/capabilities.md>), [catalog](<https://devfeed.tech/tags/catalog.md>), [code](<https://devfeed.tech/tags/code.md>), [coverage](<https://devfeed.tech/tags/coverage.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [functional](<https://devfeed.tech/tags/functional.md>), [generative](<https://devfeed.tech/tags/generative.md>), [llm](<https://devfeed.tech/tags/llm.md>), [recommendation](<https://devfeed.tech/tags/recommendation.md>), [recommendations](<https://devfeed.tech/tags/recommendations.md>), [redundancy](<https://devfeed.tech/tags/redundancy.md>), [request](<https://devfeed.tech/tags/request.md>), [resolver](<https://devfeed.tech/tags/resolver.md>), [upstream](<https://devfeed.tech/tags/upstream.md>), [web](<https://devfeed.tech/tags/web.md>), [web-api](<https://devfeed.tech/tags/web-api.md>)

### AI overview

WAR-CRAFT refines a frozen Web API recommender by checking its output against provider documentation and request requirements. An LLM jointly removes unsupported or subsumed APIs, then a requirement audit identifies gaps; a fine-tuned, catalog-constrained Resolver proposes an API or abstains, and an independent documentation check admits only supported proposals. On ProgrammableWeb across seven upstream recommenders, mean SetF1 rose from 0.558 to 0.644, exceeding the strongest of five refinement baselines (62.5%). Functional redundancy roughly halved, from 0.127 to 0.065, while mean functional coverage stayed unchanged. Gains varied by recommender type (+2.2 points for generative recommenders and +18.2 for fixed-cutoff rankers); WAR-CRAFT also outperformed output truncation at matched set sizes.

### Source excerpt

arXiv:2611.00564v1 Announce Type: new Abstract: Web API recommenders return a set of APIs for a mashup request but do not check it against provider documentation, the main public evidence of an API's capabilities. The set can therefore contain unsupported or redundant APIs and miss requested capabilities. Filling every apparent gap does not fix this, because a gap may already be served, may not need its own API, or may have no documented provider. We study post-recommendation refinement, which revises a frozen recommender's output using only the request, the catalog, and provider documentation. We propose WAR-CRAFT, which treats refinement as three decisions. An LLM removes unsupported or subsumed APIs by judging candidates jointly, then audits the remaining set against a requirement checklist derived from the request. For each uncovered requirement, a fine-tuned catalog-constrained Resolver proposes a catalog API or abstains, and an independent documentation check admits only supported proposals. On ProgrammableWeb with 7 heterogeneous upstream recommenders, WAR-CRAFT raises mean SetF1 from 0.558 to 0.644, above the strongest of 5 refinement baselines (62.5%), and roughly halves functional redundancy (0.127 to 0.065) without changing mean functional coverage. Gains range from +2.2 points on generative recommenders to +18.2 on fixed-cutoff rankers. At matched set sizes, WAR-CRAFT still outperforms truncating the upstream output, so the gain is not explained by set-size calibration alone. Our code is available at https://github.com/ZsXu-enrico/WAR-CRAFT.

## From Stories to Bugs: Story-Based Semantic Fuzzing of Interactive Systems

DevFeed: [From Stories to Bugs: Story-Based Semantic Fuzzing of Interactive Systems](<https://devfeed.tech/articles/from-stories-to-bugs-story-based-semantic-fuzzing-of-interactive-systems-113499.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.01173>)

Author: Yeshayahu Weiss, Achiya Elyasaf, Gera Weiss

Published: 2026-11-03T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [Fuzzing/Fuzz testing](<https://devfeed.tech/topics/fuzzing.md>), [business logic](<https://devfeed.tech/topics/business-logic.md>), [race-condition](<https://devfeed.tech/topics/race-condition.md>), [REST API](<https://devfeed.tech/topics/rest-api.md>), [OpenAPI Specification](<https://devfeed.tech/topics/openapi.md>), [User Interfaces](<https://devfeed.tech/topics/user-interfaces.md>)

Tags: [ablation](<https://devfeed.tech/tags/ablation.md>), [apis](<https://devfeed.tech/tags/apis.md>), [bugs](<https://devfeed.tech/tags/bugs.md>), [business-logic](<https://devfeed.tech/tags/business-logic.md>), [concurrency](<https://devfeed.tech/tags/concurrency.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [deep](<https://devfeed.tech/tags/deep.md>), [dependency](<https://devfeed.tech/tags/dependency.md>), [fuzzing](<https://devfeed.tech/tags/fuzzing.md>), [interactive](<https://devfeed.tech/tags/interactive.md>), [interface](<https://devfeed.tech/tags/interface.md>), [magento](<https://devfeed.tech/tags/magento.md>), [model](<https://devfeed.tech/tags/model.md>), [openapi](<https://devfeed.tech/tags/openapi.md>), [ordering](<https://devfeed.tech/tags/ordering.md>), [ranking](<https://devfeed.tech/tags/ranking.md>), [reproduction](<https://devfeed.tech/tags/reproduction.md>), [rest-apis](<https://devfeed.tech/tags/rest-apis.md>), [semantic](<https://devfeed.tech/tags/semantic.md>), [stories](<https://devfeed.tech/tags/stories.md>), [systems](<https://devfeed.tech/tags/systems.md>)

### AI overview

Story-based semantic fuzzing searches constrained compositions of behavioral stories to reach deep valid states and expose concurrency-sensitive failures. In Behavioral Programming, semantic bindings and state constraints preserve legal prefixes, while event eligibility, schedule selection, and replay explore relevant interleavings. On Magento, overlap-aware ranking raised reproduction of a sporadic Shipping Fee race from 3.6% to 41.2%; a controlled ordering intervention reduced another failure signature from 100/100 initial executions to 0/200 constrained executions. In a REST API study, a pipeline generated stories, dependencies, and bindings from frozen public OpenAPI contracts. Under a shared black-box evaluation, Basic and Complex confirmed 0/11 and 11/11 semantic fault classes, compared with RESTler's 2/11 and EvoMaster's 0/11. Binding yielded 250/250 valid dependent operations versus 0/250 without it; prefix controls attributed the difference to preserving legal relational state.

### Source excerpt

arXiv:2611.01173v1 Announce Type: new Abstract: Complex interactive systems hide business-logic failures along two complementary axes: deep state-dependent behaviors that require long valid prefixes and concurrency-sensitive failures that depend on the ordering of otherwise legal operations. We present story-based semantic fuzzing, a methodology that treats semantically constrained compositions of behavioral stories as primary search objects. Implemented through Behavioral Programming, semantic binding and state constraints preserve legal prefixes, while event eligibility, schedule selection, and replay expose failure-relevant interleavings. We evaluate the methodology on Magento and four stateful REST APIs. On Magento, overlap-aware ranking increased reproduction of a sporadic Shipping Fee race from 3.6% to 41.2%; a controlled ordering intervention reduced a second failure signature from 100/100 initial executions to 0/200 constrained executions. For the REST study, a versioned end-to-end pipeline took each frozen public OpenAPI contract as its sole benchmark-specific model-generation input and automatically generated the Basic and Complex stories, dependency structure, and interface bindings. Under a shared black-box task and sequence-local evaluation contract, Basic and Complex confirmed 0/11 and 11/11 semantic fault classes, while RESTler and EvoMaster confirmed 2/11 and 0/11. A paired binding ablation produced 250/250 valid dependent operations with binding and 0/250 without it, while supplementary prefix controls localized the difference to preservation of legal relational state. Together, the studies show that searching admissible semantic compositions provides a unified and effective representation for reaching deep states and exposing concurrency-sensitive business-logic failures.

## Scaling LLM Agent Tool Access: The MCP Gateway

DevFeed: [Scaling LLM Agent Tool Access: The MCP Gateway](<https://devfeed.tech/articles/scaling-llm-agent-tool-access-the-mcp-gateway-113763.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2607.15593>)

Author: Mingxin Li, Enge Song, Yueshang Zuo, Xiaodong Liu, Rong Wen, Qiang Fu, Gianni Antichi, Jian He, Jing Tie, Zhou Shao, Xiaobo Xue, Xiong Xiao, Luyao Zhong, Shaokai Zhang, Jiangu Zhao, Jianyuan Lu, Shize

Published: 2026-11-03T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Distributed Computing](<https://devfeed.tech/sources/arxiv-distributed-computing.md>), [arXiv: Networking](<https://devfeed.tech/sources/arxiv-networking.md>)

Topics: [gateway](<https://devfeed.tech/topics/gateway.md>), [MSP MCP](<https://devfeed.tech/topics/msp-mcp.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>), [context window](<https://devfeed.tech/topics/context-window.md>), [Cloud Architecture](<https://devfeed.tech/topics/cloud-architecture.md>), [OpenAPI Specification](<https://devfeed.tech/topics/openapi.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [affinity](<https://devfeed.tech/tags/affinity.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [compatibility](<https://devfeed.tech/tags/compatibility.md>), [complexity](<https://devfeed.tech/tags/complexity.md>), [context-window](<https://devfeed.tech/tags/context-window.md>), [conversion](<https://devfeed.tech/tags/conversion.md>), [cost](<https://devfeed.tech/tags/cost.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [cs-dc](<https://devfeed.tech/tags/cs-dc.md>), [cs-ni](<https://devfeed.tech/tags/cs-ni.md>), [deployments](<https://devfeed.tech/tags/deployments.md>), [engine](<https://devfeed.tech/tags/engine.md>), [gateway](<https://devfeed.tech/tags/gateway.md>), [hybrid](<https://devfeed.tech/tags/hybrid.md>), [inference](<https://devfeed.tech/tags/inference.md>), [llm](<https://devfeed.tech/tags/llm.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-gateway](<https://devfeed.tech/tags/mcp-gateway.md>), [scaling](<https://devfeed.tech/tags/scaling.md>), [tool](<https://devfeed.tech/tags/tool.md>)

### AI overview

The MCP Gateway addresses production scaling problems on both sides of tool access: legacy services and changing MCP variants burden providers, while large mounted tool sets increase agent context use and latency and may lower task success. It centralizes legacy-service integration, protocol compatibility, access control, tool recommendation, and session-aware routing. Its conversion module supports 315 OpenAPI services, and its hybrid retrieval engine reports about 98% Top-15 recall while scaling access to 3,000+ tools with improved tool selection accuracy. The abstract does not provide further evaluation details.

### Source excerpt

arXiv:2607.15593v2 Announce Type: replace Abstract: LLM agents increasingly rely on tool calling to complete tasks. Model Context Protocol (MCP) standardizes tool calling between LLM agents and tool providers. It reduces integration cost and drives rapid growth in tool scale. In production deployments, tool access becomes difficult to scale. On the tool provider side, legacy services are not directly callable through MCP; the rapid protocol development creates ongoing compatibility cost. On the agent side, the number of mounted tools is limited by the LLM context window and inference overhead; mounting a large tool set increases token usage and inference latency and can reduce task success rate. Moreover, for stateful MCP backends with multiple replicas, preserving session affinity increases client-side complexity. We present a cloud-scale MCP Gateway system. It breaks the direct-connect model on the data plane and offloads legacy service integration, consolidating incompatible MCP variants, access control, tool recommendation, and session-aware routing at the gateway. The conversion module supports 315 OpenAPI services in the cloud and integrates MCP transport variants. Session-aware routing decouples the scalability of the gateway layer and the MCP service layer. The hybrid retrieval engine sustains $\sim$98\% Top-15 recall; it scales agent tool access to 3{,}000+ tools with improved tool selection accuracy. We also share the lessons learned from deploying the gateway system in production.

## CVE-2026-63346 - Refitter: C# source injection through OpenAPI header parameter names

DevFeed: [CVE-2026-63346 - Refitter: C# source injection through OpenAPI header parameter names](<https://devfeed.tech/articles/cve-2026-63346-refitter-c-source-injection-through-openapi-header-parameter-names-109482.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-63346>)

Author: CVEFEED.io; github.com

Published: 2026-10-30T23:17:14Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [C#](<https://devfeed.tech/topics/csharp.md>), [OpenAPI Specification](<https://devfeed.tech/topics/openapi.md>), [client library](<https://devfeed.tech/topics/client-library.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [api](<https://devfeed.tech/tags/api.md>), [application](<https://devfeed.tech/tags/application.md>), [assembly](<https://devfeed.tech/tags/assembly.md>), [behavior](<https://devfeed.tech/tags/behavior.md>), [c-sharp](<https://devfeed.tech/tags/c-sharp.md>), [class](<https://devfeed.tech/tags/class.md>), [client](<https://devfeed.tech/tags/client.md>), [code](<https://devfeed.tech/tags/code.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-63346](<https://devfeed.tech/tags/cve-2026-63346.md>), [header](<https://devfeed.tech/tags/header.md>), [interface](<https://devfeed.tech/tags/interface.md>), [library](<https://devfeed.tech/tags/library.md>), [name](<https://devfeed.tech/tags/name.md>), [net](<https://devfeed.tech/tags/net.md>), [net-8](<https://devfeed.tech/tags/net-8.md>), [openapi](<https://devfeed.tech/tags/openapi.md>), [parameter](<https://devfeed.tech/tags/parameter.md>), [source](<https://devfeed.tech/tags/source.md>)

### AI overview

Before Refitter 2.1.2, an OpenAPI header parameter name was inserted unescaped into a Refit `[Header("")]` attribute. An attacker-controlled description could therefore inject valid C# into generated code; a `[ModuleInitializer]` could run the injected code when the compiled assembly loads at startup, even if the API client is never called. The excerpt says default validation does not block this path and notes that query `AliasAs` and enum/default value sinks are escaped. The behavior was verified with Refitter 2.0.0 and .NET 8; the issue is fixed in 2.1.2.

### Source excerpt

CVE ID :CVE-2026-63346 Published : Oct. 30, 2026, 11:17 p.m. | 39 minutes ago Description :Refitter is a tool for generating a C# REST API client using the Refit library. Prior to 2.1.2, the header parameter name in `parameters[].name` with `in: header` is emitted verbatim into a Refit `[Header("")]` attribute string without escaping quotation marks. An attacker-influenced OpenAPI description can pass default validation without `--skip-validation` and break out from the parameter-list position by closing the parameter and method syntax, attribute, interface, and namespace. The generated file can remain valid C# while containing a top-level file class with a `[ModuleInitializer]` method, which executes attacker code when the compiled assembly is loaded at application startup, even if the client is never called. Query `AliasAs` and enum/default value sinks are escaped; this flaw is in header-name attribute-string emission. The behavior was verified with Refitter 2.0.0 and .NET 8. This issue is fixed in version 2.1.2. Severity: 8.6 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## CVE-2026-63345 - Refitter: C# source injection through OpenAPI path keys

DevFeed: [CVE-2026-63345 - Refitter: C# source injection through OpenAPI path keys](<https://devfeed.tech/articles/cve-2026-63345-refitter-c-source-injection-through-openapi-path-keys-109481.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-63345>)

Author: CVEFEED.io; github.com

Published: 2026-10-30T23:17:13Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [OpenAPI Specification](<https://devfeed.tech/topics/openapi.md>), [REST API](<https://devfeed.tech/topics/rest-api.md>), [Compilers and Linkers](<https://devfeed.tech/topics/compilers-and-linkers.md>), [Boilerplate](<https://devfeed.tech/topics/boilerplate.md>), [client library](<https://devfeed.tech/topics/client-library.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [c-sharp](<https://devfeed.tech/tags/c-sharp.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-63345](<https://devfeed.tech/tags/cve-2026-63345.md>), [openapi](<https://devfeed.tech/tags/openapi.md>)

### AI overview

Before Refitter 2.1.2, OpenAPI `paths` keys were inserted verbatim into generated C# Refit route attributes. An attacker-controlled, single-line slash-prefixed path can survive default validation and inject a `[ModuleInitializer]` that runs when the generated assembly is compiled and loaded at startup, without the client being called. The excerpt says enum and default-value output is escaped and is not the vulnerable sink. The behavior was verified on Refitter 2.0.0 with .NET 8; the issue is fixed in 2.1.2. The excerpt does not identify affected products in the catalog table.

### Source excerpt

CVE ID :CVE-2026-63345 Published : Oct. 30, 2026, 11:17 p.m. | 39 minutes ago Description :Refitter is a tool for generating a C# REST API client using the Refit library. Prior to 2.1.2, OpenAPI `paths`-object keys are emitted verbatim into Refit route attributes such as `[Get("")]` without escaping quotation marks or restricting characters. An attacker-influenced single-line, slash-prefixed path survives default validation without `--skip-validation` and can close the attribute string, interface, and namespace while introducing a top-level file class and reopening the generated structure to keep valid C#. A `[ModuleInitializer]` method executes attacker code when an application compiles and loads the generated assembly at startup, even without calling the generated client. The enum and default value sinks are escaped and are not the vulnerable path-emission sink. The behavior was verified on Refitter 2.0.0 with .NET 8. This issue is fixed in version 2.1.2. Severity: 8.6 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## Discover the APIs an agent will call before you build

DevFeed: [Discover the APIs an agent will call before you build](<https://devfeed.tech/articles/discover-the-apis-an-agent-will-call-before-you-build-109703.md>)

Original publisher: [Read original article](<https://www.swytchcode.com/content/api-discovery-before-building-agents>)

Author: Swytchcode Team

Published: 2026-10-30T18:46:00Z

Content type: article

Language: en

Sources: [Swytchcode](<https://devfeed.tech/sources/swytchcode.md>)

Topics: [OpenAPI Specification](<https://devfeed.tech/topics/openapi.md>), [Cloud Architecture](<https://devfeed.tech/topics/cloud-architecture.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [agent](<https://devfeed.tech/tags/agent.md>), [allowed](<https://devfeed.tech/tags/allowed.md>), [api](<https://devfeed.tech/tags/api.md>), [api-governance](<https://devfeed.tech/tags/api-governance.md>), [apis](<https://devfeed.tech/tags/apis.md>), [article](<https://devfeed.tech/tags/article.md>), [axios](<https://devfeed.tech/tags/axios.md>), [build](<https://devfeed.tech/tags/build.md>), [call](<https://devfeed.tech/tags/call.md>), [catalog](<https://devfeed.tech/tags/catalog.md>), [cli](<https://devfeed.tech/tags/cli.md>), [client](<https://devfeed.tech/tags/client.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [has](<https://devfeed.tech/tags/has.md>), [logs](<https://devfeed.tech/tags/logs.md>), [providers](<https://devfeed.tech/tags/providers.md>), [public](<https://devfeed.tech/tags/public.md>), [registry](<https://devfeed.tech/tags/registry.md>), [search](<https://devfeed.tech/tags/search.md>), [service](<https://devfeed.tech/tags/service.md>)

### AI overview

Before building an agent, inventory the operations it may need from a week of gateway or mesh logs, existing HTTP client code, and working on-call examples. `swy search` queries the remote registry; `swy discover` searches only downloaded bundles, so neither finds undocumented internal services. Use `swy get` to download a found bundle and `swy list methods` to inspect local methods; downloading does not enable them. Record one row per operation with its method, owner, registry status, and whether it reads or writes. Keep unowned rows out of scope, compare the inventory with the gateway catalog, and enable only operations needed for the first release. Missing internal providers or paths require documentation and, on Business or Enterprise, a scoped bring-your-own provider; Free and Pro use registry offerings. An empty internal-service search is an expected result, not proof the service does not exist.

### Source excerpt

The agent stalls on the internal service nobody documented. Search the public registry for known providers, then build the other rows from your own call logs.

## How MoEngage turned over 400 APIs into agent tools with AgentCore Gateway

DevFeed: [How MoEngage turned over 400 APIs into agent tools with AgentCore Gateway](<https://devfeed.tech/articles/how-moengage-turned-over-400-apis-into-agent-tools-with-agentcore-gateway-106874.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/machine-learning/how-moengage-turned-over-400-apis-into-agent-tools-with-agentcore-gateway/>)

Author: Nikhil Kumar

Published: 2026-10-29T16:54:52Z

Content type: article

Language: en

Sources: [Artificial Intelligence](<https://devfeed.tech/sources/artificial-intelligence.md>)

Topics: [Amazon Bedrock AgentCore](<https://devfeed.tech/topics/amazon-bedrock-agentcore.md>), [OpenAPI Specification](<https://devfeed.tech/topics/openapi.md>), [AI Integration Strategies](<https://devfeed.tech/topics/ai-integration-strategies.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Tool](<https://devfeed.tech/topics/tool.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agent-tools](<https://devfeed.tech/tags/agent-tools.md>), [agentcore](<https://devfeed.tech/tags/agentcore.md>), [amazon-bedrock](<https://devfeed.tech/tags/amazon-bedrock.md>), [amazon-bedrock-agentcore](<https://devfeed.tech/tags/amazon-bedrock-agentcore.md>), [amazon-vpc](<https://devfeed.tech/tags/amazon-vpc.md>), [amazon-vpc-lattice](<https://devfeed.tech/tags/amazon-vpc-lattice.md>), [apis](<https://devfeed.tech/tags/apis.md>), [aws](<https://devfeed.tech/tags/aws.md>), [context](<https://devfeed.tech/tags/context.md>), [customer-solutions](<https://devfeed.tech/tags/customer-solutions.md>), [egress](<https://devfeed.tech/tags/egress.md>), [gateway](<https://devfeed.tech/tags/gateway.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-servers](<https://devfeed.tech/tags/mcp-servers.md>), [openapi](<https://devfeed.tech/tags/openapi.md>), [permission](<https://devfeed.tech/tags/permission.md>), [policies](<https://devfeed.tech/tags/policies.md>), [private](<https://devfeed.tech/tags/private.md>), [public](<https://devfeed.tech/tags/public.md>), [tools](<https://devfeed.tech/tags/tools.md>)

### AI overview

MoEngage used Amazon Bedrock AgentCore Gateway to expose roughly 400 private REST API operations across seven AWS Regions as permission-scoped MCP tools for 10 internal agents. Product teams opt in through OpenAPI annotations; CI registers targets, while Cedar policies scope tool discovery and calls by each agent's IAM role. Agents connect privately through a VPC interface endpoint, and managed egress over Amazon VPC Lattice reaches internal APIs. Identity context is passed in headers rather than model-visible tool arguments. A search-first client presents relevant tools without sending the full catalog into the model's context. MoEngage reports no product team wrote MCP server code or provisioned integration networking, API onboarding now takes hours instead of days, and the approach saved an estimated six months of platform engineering effort. AgentCore feature availability varies by Region.

### Source excerpt

MoEngage turned roughly 400 private REST APIs across 7 AWS Regions into permission-scoped agent tools with Amazon Bedrock AgentCore Gateway. No per-service MCP servers, no public endpoints, and no 400-tool context bloat. See how OpenAPI specs, Cedar policies, and managed Amazon VPC Lattice egress made it work.

## ToolContractGate: Versioned Trusted Contracts for Drift-Safe Agent Tool Invocation

DevFeed: [ToolContractGate: Versioned Trusted Contracts for Drift-Safe Agent Tool Invocation](<https://devfeed.tech/articles/toolcontractgate-versioned-trusted-contracts-for-drift-safe-agent-tool-invocation-101383.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2610.33108>)

Author: Sachin Gupta

Published: 2026-10-27T04:00:00Z

Content type: article

Language: en

Sources: [arXiv: Cryptography and Security](<https://devfeed.tech/sources/arxiv-cryptography-and-security.md>), [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [OpenAPI Specification](<https://devfeed.tech/topics/openapi.md>), [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>)

Tags: [ablation](<https://devfeed.tech/tags/ablation.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agent-tools](<https://devfeed.tech/tags/agent-tools.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [contracts](<https://devfeed.tech/tags/contracts.md>), [coverage](<https://devfeed.tech/tags/coverage.md>), [cs-cr](<https://devfeed.tech/tags/cs-cr.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [evaluation](<https://devfeed.tech/tags/evaluation.md>), [execution](<https://devfeed.tech/tags/execution.md>), [fingerprint](<https://devfeed.tech/tags/fingerprint.md>), [latency](<https://devfeed.tech/tags/latency.md>), [openapi](<https://devfeed.tech/tags/openapi.md>), [provenance](<https://devfeed.tech/tags/provenance.md>), [run](<https://devfeed.tech/tags/run.md>), [runtime](<https://devfeed.tech/tags/runtime.md>), [schema](<https://devfeed.tech/tags/schema.md>), [semantic](<https://devfeed.tech/tags/semantic.md>), [synthetic](<https://devfeed.tech/tags/synthetic.md>), [tests](<https://devfeed.tech/tags/tests.md>), [tool](<https://devfeed.tech/tags/tool.md>), [unit-tests](<https://devfeed.tech/tags/unit-tests.md>)

### AI overview

ToolContractGate evaluates OpenAPI-derived agent tool calls against versioned contracts that bind a stored OpenAPI fingerprint to access, schema, and behavioral declarations. Its full evaluator uses ten checks, including cached boot-time provenance. In a synthetic 45-case benchmark, it detected all 35 unsafe cases across 12 drift classes, issuing 29 BLOCK, 3 REVIEW, and 3 WARN decisions, with no false blocks among 10 safe cases. The archived run reports 0.18 ms mean latency and 2 ms p95, measured in integer milliseconds. These results cover contract decisions; enforcement depends on a host honoring them. Production traffic, semantic backend drift, and dynamic provenance refresh remain untested opportunities.

### Source excerpt

arXiv:2610.33108v1 Announce Type: cross Abstract: Agent tool approval and input validation do not, by themselves, bind a request to an approved source artifact. ToolContractGate provides a deterministic runtime contract evaluator for OpenAPI-derived agent tools. Each versioned ToolContract combines a stored OpenAPI fingerprint with access, schema, and behavioral declarations. The full evaluator applies ten checks, including a cached boot-time provenance result; four execution modes and five evaluation configurations support baseline, ablation, and non-blocking shadow analysis. On a synthetic benchmark of 45 cases (35 unsafe cases across 12 drift classes and 10 safe cases), the full pipeline detects all 35 faults: 29 BLOCK, 3 REVIEW, and 3 WARN decisions, with no false blocks on the safe cases. The archived run reports a mean gate latency of 0.18 ms and a 95th percentile (p95) of 2 ms using integer-millisecond measurements. The open-source artifact includes seven OpenAPI specifications, twelve enterprise contracts, 29 unit tests, and a 900-record evaluation. Results characterize contract-decision coverage; downstream enforcement requires a host that honors the returned decision. Production traffic, semantic backend drift, and dynamic provenance refresh remain evaluation and integration opportunities.

## How to make enterprise APIs agent-ready

DevFeed: [How to make enterprise APIs agent-ready](<https://devfeed.tech/articles/how-to-make-enterprise-apis-agent-ready-100446.md>)

Original publisher: [Read original article](<https://www.infoworld.com/article/4239263/how-to-make-enterprise-apis-agent-ready.html>)

Author: Marco Palladino

Published: 2026-10-26T09:00:00Z

Content type: article

Language: en

Sources: [InfoWorld](<https://devfeed.tech/sources/infoworld.md>)

Topics: [API Governance](<https://devfeed.tech/topics/api-governance.md>), [AI Integration Strategies](<https://devfeed.tech/topics/ai-integration-strategies.md>), [AI Context Management](<https://devfeed.tech/topics/ai-context-management.md>), [OpenAPI Specification](<https://devfeed.tech/topics/openapi.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [apis](<https://devfeed.tech/tags/apis.md>), [apis-artificial-intelligence-development-tools-generative-ai-software-development](<https://devfeed.tech/tags/apis-artificial-intelligence-development-tools-generative-ai-software-development.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [context](<https://devfeed.tech/tags/context.md>), [context-layer](<https://devfeed.tech/tags/context-layer.md>), [cost](<https://devfeed.tech/tags/cost.md>), [crm](<https://devfeed.tech/tags/crm.md>), [development-tools](<https://devfeed.tech/tags/development-tools.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [gateway](<https://devfeed.tech/tags/gateway.md>), [generative-ai](<https://devfeed.tech/tags/generative-ai.md>), [governance](<https://devfeed.tech/tags/governance.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-server](<https://devfeed.tech/tags/mcp-server.md>), [model-context-protocol](<https://devfeed.tech/tags/model-context-protocol.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [storytype-opinion](<https://devfeed.tech/tags/storytype-opinion.md>)

### AI overview

Exposing every API operation as a separate MCP tool can burden agents with large tool lists, increasing token use, tool-selection errors, and latency; trimming lists can create integration sprawl. The proposed code-mode pattern exposes an SDK-like interface: agents search for operations, load schemas as needed, and run short code snippets in a sandbox, returning only final results to the model. The article reports one tested workflow dropping from roughly 120,000 tokens with standard tool calling to about 1,200 in code mode. It says this approach requires a trusted sandbox and full observability. For governance, it recommends generating interfaces from managed API specifications and policies, routing calls through the existing gateway, registering interfaces in a central catalog, and composing task-scoped access to APIs, MCP servers, and data sources.

### Source excerpt

Enterprises spent the last decade building API programs. A large organization now runs thousands of internal APIs, each with a spec, owner, authentication scheme, and access policies enforced at a gateway. As agents move into production, those APIs are the obvious source of the context agents need: customer records, order status, inventory, pricing, and support tickets. The more difficult question now is how agents reach those systems at scale. The Model Context Protocol (MCP) gave the industry a standard way to connect agents to tools. But the most common way teams expose APIs over MCP, one tool per API operation, starts to fail well before an agent touches a meaningful share of the enterprise's API estate. Here's why that happens, what a better pattern looks like, and how platform teams can build a context layer that reuses the governance they already have. Why one tool per endpoint doesn't scale The default way to turn an API into an MCP server is to take its OpenAPI spec and generate one tool per operation. That works for a small API. However, a typical enterprise CRM or ERP API can have hundreds of operations, and an agent that needs a few of those APIs quickly faces hundreds of tool definitions. Using this approach, three things go sideways fast. Cost. Every tool definition loads into the model's context before the agent does any work, and every intermediate result flows back through the model. A routine workflow, such as looking up a customer, pulling their open orders, and checking shipment status, pays for each hop in tokens. Accuracy. Once the tool list grows past what the model can reason about, tool selection degrades. The agent picks the wrong tool from a set of similar-looking options, or makes three calls where one would do. Latency. More context to process and more back-and-forth between the model and its tools slows the agent down. Users notice that long before anyone sees the token bill. Teams usually respond by curating. They trim tool lists and s

## Python REST APIs With Flask, Connexion, and SQLAlchemy - Part 1

DevFeed: [Python REST APIs With Flask, Connexion, and SQLAlchemy - Part 1](<https://devfeed.tech/articles/python-rest-apis-with-flask-connexion-and-sqlalchemy-part-1-100399.md>)

Original publisher: [Read original article](<https://realpython.com/flask-connexion-rest-api/>)

Author: Philipp Acsany

Published: 2026-10-25T14:00:00Z

Content type: tutorial

Language: en

Sources: [Real Python](<https://devfeed.tech/sources/real-python.md>)

Topics: [REST API](<https://devfeed.tech/topics/rest-api.md>), [Flask](<https://devfeed.tech/topics/flask.md>), [OpenAPI Specification](<https://devfeed.tech/topics/openapi.md>), [Swagger](<https://devfeed.tech/topics/swagger.md>)

Tags: [2022](<https://devfeed.tech/tags/2022.md>), [about](<https://devfeed.tech/tags/about.md>), [added](<https://devfeed.tech/tags/added.md>), [airplay](<https://devfeed.tech/tags/airplay.md>), [api](<https://devfeed.tech/tags/api.md>), [apis](<https://devfeed.tech/tags/apis.md>), [application](<https://devfeed.tech/tags/application.md>), [build](<https://devfeed.tech/tags/build.md>), [flask](<https://devfeed.tech/tags/flask.md>), [foundation](<https://devfeed.tech/tags/foundation.md>), [python](<https://devfeed.tech/tags/python.md>), [rest](<https://devfeed.tech/tags/rest.md>), [rest-api](<https://devfeed.tech/tags/rest-api.md>), [rest-apis](<https://devfeed.tech/tags/rest-apis.md>), [series](<https://devfeed.tech/tags/series.md>), [sqlalchemy](<https://devfeed.tech/tags/sqlalchemy.md>), [swagger](<https://devfeed.tech/tags/swagger.md>), [this](<https://devfeed.tech/tags/this.md>), [ui](<https://devfeed.tech/tags/ui.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

The tutorial builds a Flask REST API for managing people, using Connexion to connect OpenAPI definitions to Python functions and generate interactive Swagger UI documentation. It starts with a virtual environment, Flask app, and SQLite as a planned later component, but this part stores records in an in-memory dictionary keyed by unique, case-sensitive last names; changes disappear when the app restarts. The OpenAPI file defines collection and individual-person routes, while handlers list, create, read, update, and delete records. The guide notes that Connexion runs the app with Uvicorn, so it uses `reload=True` and an import string instead of Flask's `debug=True`. Part two is intended to add persistent database storage.

### Source excerpt

Build a Flask REST API with Connexion and Swagger UI in this three-part series. Part one lays the foundation of your application.

[Next page](<https://devfeed.tech/topics/openapi.md?cursor=WyIyMDI2LTEwLTI1VDE0OjAwOjAwKzAwOjAwIiwgIjliYjMyOTEzLTU2M2MtNDk3Ny1iNGY2LTA3NDY5YTE5ODFjOSJd>)