<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Agentic Index: agent infrastructure platforms change log</title>
    <link>https://agenticindex.io/rankings/agent-infrastructure</link>
    <atom:link href="https://agenticindex.io/feeds/agent-infrastructure.xml" rel="self" type="application/rss+xml" />
    <description>Verified changes to agent infrastructure platforms, from the Agentic Index change log. Every entry is dated and sourced from public vendor material.</description>
    <language>en-us</language>
    <copyright>Free to reuse with a visible link to agenticindex.io. Terms: https://agenticindex.io/use-this-data</copyright>
    <lastBuildDate>Fri, 25 Sep 2026 12:00:00 GMT</lastBuildDate>
    <ttl>720</ttl>
    <image>
      <url>https://media.base44.com/images/public/69e4cec10b4126d233ee7ee4/a44c0d34a_generated_image.png</url>
      <title>Agentic Index: agent infrastructure platforms change log</title>
      <link>https://agenticindex.io/rankings/agent-infrastructure</link>
    </image>
    <item>
      <title>LiteLLM launched the public preview of LiteAgents, an SDK that supports Deep Agents, Pydantic AI, Claude Agent SDK, Codex and OpenCode…</title>
      <link>https://agenticindex.io/change-log/litellm</link>
      <guid isPermaLink="false">agenticindex.io:change:litellm-k9gz3u-2026-09-25</guid>
      <pubDate>Fri, 25 Sep 2026 12:00:00 GMT</pubDate>
      <category>MCP / tool calling / API</category>
      <category>Agent infrastructure</category>
      <description><![CDATA[<p>LiteLLM launched the public preview of LiteAgents, an SDK that supports Deep Agents, Pydantic AI, Claude Agent SDK, Codex and OpenCode through a common query interface. Profiles select the runtime while retaining shared tools, MCP connections and model configuration; native runtime options remain available. Optional Temporal integration adds recovery from recorded operations and checkpoints, while simple local agents require neither Temporal nor PostgreSQL. Changing runtimes starts new runs and does not migrate an active native session.</p><p><strong>Why it matters:</strong> Teams can compare agent runtimes on their own workloads with less integration work and add recovery for longer jobs. Production evaluation should account for preview maturity and ensure that tools causing external changes tolerate retries.</p><p>Impact: High. Verification: Verified. Type: MCP / tool calling / API.</p><p>Evidence: <a href="https://docs.litellm.ai/blog/liteagents-sdk">Official blog</a></p><p>Source: <a href="https://agenticindex.io/change-log/litellm">Agentic Index change log</a>. Free to reuse with a link back. <a href="https://agenticindex.io/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>Windmill v1.818.0 counts enabled service accounts as operator seats in self hosted Enterprise deployments, billing each as half a seat…</title>
      <link>https://agenticindex.io/change-log/windmill</link>
      <guid isPermaLink="false">agenticindex.io:change:windmill-170vtl-2026-09-25</guid>
      <pubDate>Fri, 25 Sep 2026 12:00:00 GMT</pubDate>
      <category>Pricing / packaging</category>
      <category>Agent infrastructure</category>
      <category>Agent builder</category>
      <description><![CDATA[<p>Windmill v1.818.0 counts enabled service accounts as operator seats in self hosted Enterprise deployments, billing each as half a seat regardless of its assigned role. Enabled service accounts also count toward the offline license seat cap, and creation is refused when the cap is reached. The related Cloud Team billing change is separate from this release.</p><p><strong>Why it matters:</strong> Organizations using dedicated identities for agents and automation need to include those accounts in license forecasts. Reviewing unused enabled accounts before upgrading can help avoid unexpected charges or blocked account creation.</p><p>Impact: High. Verification: Verified. Type: Pricing / packaging.</p><p>Evidence: <a href="https://github.com/windmill-labs/windmill/releases/tag/v1.818.0">GitHub release</a></p><p>Source: <a href="https://agenticindex.io/change-log/windmill">Agentic Index change log</a>. Free to reuse with a link back. <a href="https://agenticindex.io/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>Exa launched Agent Ultra, its highest effort mode for exhaustive research and building large lists of entities.</title>
      <link>https://agenticindex.io/change-log/exa</link>
      <guid isPermaLink="false">agenticindex.io:change:exa-zqk2ll-2026-09-25</guid>
      <pubDate>Fri, 25 Sep 2026 12:00:00 GMT</pubDate>
      <category>Agent capability</category>
      <category>Agent infrastructure</category>
      <description><![CDATA[<p>Exa launched Agent Ultra, its highest effort mode for exhaustive research and building large lists of entities. It coordinates agents across many sources and supports research runs lasting up to three hours. Users can set spending and duration limits or stop a run early while retaining the results gathered so far.</p><p><strong>Why it matters:</strong> Research teams can allocate more computation to difficult verification and enrichment tasks while controlling the budget for each run. This offers a configurable option for work where completeness matters more than response speed.</p><p>Impact: Medium. Verification: Verified. Type: Agent capability.</p><p>Evidence: <a href="https://exa.ai/blog/exa-agent-ultra">Official blog</a></p><p>Source: <a href="https://agenticindex.io/change-log/exa">Agentic Index change log</a>. Free to reuse with a link back. <a href="https://agenticindex.io/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>Browserbase Agents can pause a run for human input and resume within the same browser session.</title>
      <link>https://agenticindex.io/change-log/browserbase</link>
      <guid isPermaLink="false">agenticindex.io:change:browserbase-1jwxbb-2026-09-24</guid>
      <pubDate>Thu, 24 Sep 2026 12:00:00 GMT</pubDate>
      <category>Human approval / guardrails</category>
      <category>Browser / computer-use agent</category>
      <category>Agent infrastructure</category>
      <description><![CDATA[<p>Browserbase Agents can pause a run for human input and resume within the same browser session. Developers set a natural language pauseWhen condition, which gives the agent a pause tool and lets it enter PAUSED when the condition is met. The resume API accepts a follow up task, such as continuing after a user supplies an MFA code.</p><p><strong>Why it matters:</strong> Teams can include human checkpoints in browser workflows without rebuilding the session after each interruption. They should test that their pause conditions reliably identify the situations requiring human input.</p><p>Impact: High. Verification: Verified. Type: Human approval / guardrails.</p><p>Evidence: <a href="https://www.browserbase.com/changelog/pause-and-resume-for-agents">Official changelog</a></p><p>Source: <a href="https://agenticindex.io/change-log/browserbase">Agentic Index change log</a>. Free to reuse with a link back. <a href="https://agenticindex.io/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>Corti updated Guided Generation to pass user edited, added, and discarded facts with explicit type metadata.</title>
      <link>https://agenticindex.io/change-log/corti</link>
      <guid isPermaLink="false">agenticindex.io:change:corti-qgp3j2-2026-09-24</guid>
      <pubDate>Thu, 24 Sep 2026 12:00:00 GMT</pubDate>
      <category>Human approval / guardrails</category>
      <category>Healthcare agent</category>
      <category>Agent infrastructure</category>
      <description><![CDATA[<p>Corti updated Guided Generation to pass user edited, added, and discarded facts with explicit type metadata. User edits now take precedence over conflicting transcript content, and discarded facts are excluded from generated notes. User added facts and system supplied context also receive explicit priority.</p><p><strong>Why it matters:</strong> Clinical application teams should test correction and deletion workflows against this release, especially where generated notes previously reintroduced rejected transcript details.</p><p>Impact: Medium. Verification: Verified. Type: Human approval / guardrails.</p><p>Evidence: <a href="https://docs.corti.ai/release-notes/textgen#2026-09-24">Official changelog</a></p><p>Source: <a href="https://agenticindex.io/change-log/corti">Agentic Index change log</a>. Free to reuse with a link back. <a href="https://agenticindex.io/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>DBOS Python 3.1.0 added workflow rewind, allowing a workflow in a terminal state to restart from a specified step.</title>
      <link>https://agenticindex.io/change-log/dbos</link>
      <guid isPermaLink="false">agenticindex.io:change:dbos-gfcvc0-2026-09-24</guid>
      <pubDate>Thu, 24 Sep 2026 12:00:00 GMT</pubDate>
      <category>Workflow orchestration</category>
      <category>Agent infrastructure</category>
      <description><![CDATA[<p>DBOS Python 3.1.0 added workflow rewind, allowing a workflow in a terminal state to restart from a specified step. The release also added workflow ID reuse policies and local configuration of Conductor metadata only mode.</p><p><strong>Why it matters:</strong> Teams operating durable agent workflows gain a recovery option for completed or failed runs. Rewind can repeat downstream messages and actions, so recovery procedures should account for those effects before replaying a run.</p><p>Impact: Medium. Verification: Verified. Type: Workflow orchestration.</p><p>Evidence: <a href="https://github.com/dbos-inc/dbos-transact-py/releases/tag/3.1.0">GitHub release</a></p><p>Source: <a href="https://agenticindex.io/change-log/dbos">Agentic Index change log</a>. Free to reuse with a link back. <a href="https://agenticindex.io/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>LangSmith launched the public beta of smithtune, a CLI and coding agent skill that turns recorded agent trajectories into supervised fine…</title>
      <link>https://agenticindex.io/change-log/langsmith</link>
      <guid isPermaLink="false">agenticindex.io:change:langsmith-1m7p56-2026-09-24</guid>
      <pubDate>Thu, 24 Sep 2026 12:00:00 GMT</pubDate>
      <category>Workflow orchestration</category>
      <category>Agent infrastructure</category>
      <description><![CDATA[<p>LangSmith launched the public beta of smithtune, a CLI and coding agent skill that turns recorded agent trajectories into supervised fine tuning workflows. It prepares and persists training datasets, submits training jobs to Fireworks or Baseten, compares the resulting model with the base model through LangSmith evaluations, and can deploy the selected model. Users need a LangSmith account with agent traces and an API key for a supported training provider.</p><p><strong>Why it matters:</strong> Teams can test whether their production examples support a specialized agent model without building separate data preparation, training, and evaluation pipelines. Recorded datasets and evaluation comparisons give reviewers a way to inspect gains and regressions before deployment.</p><p>Impact: High. Verification: Verified. Type: Workflow orchestration.</p><p>Evidence: <a href="https://www.langchain.com/blog/langsmith-fine-tuning">Official blog</a></p><p>Source: <a href="https://agenticindex.io/change-log/langsmith">Agentic Index change log</a>. Free to reuse with a link back. <a href="https://agenticindex.io/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>Braintrust announced Nitro, a new asynchronous query engine for Brainstore that separates storage reads from compute work to accelerate…</title>
      <link>https://agenticindex.io/change-log/braintrust</link>
      <guid isPermaLink="false">agenticindex.io:change:braintrust-ok05u5-2026-09-24</guid>
      <pubDate>Thu, 24 Sep 2026 12:00:00 GMT</pubDate>
      <category>Observability / auditability</category>
      <category>Agent infrastructure</category>
      <description><![CDATA[<p>Braintrust announced Nitro, a new asynchronous query engine for Brainstore that separates storage reads from compute work to accelerate trace investigations. Nitro is automatically enabled for SaaS and BYOC customers, with support starting at dataplane 2.15 for deployments customers host themselves. Braintrust reports that full text searches ran more than twice as fast in its production comparison.</p><p><strong>Why it matters:</strong> Teams investigating agent failures can search large trace histories with less waiting, including when coding agents issue many concurrent queries. Existing hosted customers receive the improvement without configuring a new search interface.</p><p>Impact: Medium. Verification: Verified. Type: Observability / auditability.</p><p>Evidence: <a href="https://www.braintrust.dev/blog/nitro">Official blog</a></p><p>Source: <a href="https://agenticindex.io/change-log/braintrust">Agentic Index change log</a>. Free to reuse with a link back. <a href="https://agenticindex.io/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>Cognee v1.6.1 adds a Google Drive OAuth connector, Gmail ingestion, and shared drive synchronization, with Google connectors bundled in…</title>
      <link>https://agenticindex.io/change-log/cognee</link>
      <guid isPermaLink="false">agenticindex.io:change:cognee-85mffc-2026-09-24</guid>
      <pubDate>Thu, 24 Sep 2026 12:00:00 GMT</pubDate>
      <category>Integrations</category>
      <category>Agent infrastructure</category>
      <description><![CDATA[<p>Cognee v1.6.1 adds a Google Drive OAuth connector, Gmail ingestion, and shared drive synchronization, with Google connectors bundled in the SDK. The release also streams graph visualization responses and preserves document metadata in retrieved chunks while restricting provenance to datasets the caller can read.</p><p><strong>Why it matters:</strong> Teams can populate agent memory from shared Google workspace content with fewer integration steps. Large memory graphs become easier to inspect, and retrieval retains clearer links to source documents.</p><p>Impact: Medium. Verification: Verified. Type: Integrations.</p><p>Evidence: <a href="https://github.com/topoteretes/cognee/releases/tag/v1.6.1">GitHub release</a></p><p>Source: <a href="https://agenticindex.io/change-log/cognee">Agentic Index change log</a>. Free to reuse with a link back. <a href="https://agenticindex.io/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>Agno 3.0.11 introduced a shared Knowledge retrieval pipeline with MMR reranking for result diversity and recency reranking to favor newer…</title>
      <link>https://agenticindex.io/change-log/agno</link>
      <guid isPermaLink="false">agenticindex.io:change:agno-uyyzyp-2026-09-23</guid>
      <pubDate>Wed, 23 Sep 2026 12:00:00 GMT</pubDate>
      <category>MCP / tool calling / API</category>
      <category>Agent infrastructure</category>
      <description><![CDATA[<p>Agno 3.0.11 introduced a shared Knowledge retrieval pipeline with MMR reranking for result diversity and recency reranking to favor newer revisions. It deprecates reranker configuration on individual vector databases in favor of the Knowledge layer. The release adds guarded APIs for relocating indexed documentation sources, with migration running as a dry run by default. Typed page tool results expose errors, completeness and truncation, while run outputs and API schemas gain a cancellation_stage field.</p><p><strong>Why it matters:</strong> Teams can apply retrieval policies consistently across storage backends and distinguish incomplete evidence from complete results before an agent acts. Existing integrations should migrate reranker configuration and can replace brittle cancellation message parsing with explicit status data.</p><p>Impact: Medium. Verification: Verified. Type: MCP / tool calling / API.</p><p>Evidence: <a href="https://github.com/agno-agi/agno/releases/tag/v3.0.11">GitHub release</a></p><p>Source: <a href="https://agenticindex.io/change-log/agno">Agentic Index change log</a>. Free to reuse with a link back. <a href="https://agenticindex.io/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>Cartesia introduced Multilingual Voices, a library of more than 50 voices that support up to 25 languages while retaining the same vocal…</title>
      <link>https://agenticindex.io/change-log/cartesia</link>
      <guid isPermaLink="false">agenticindex.io:change:cartesia-pcsges-2026-09-23</guid>
      <pubDate>Wed, 23 Sep 2026 12:00:00 GMT</pubDate>
      <category>Agent capability</category>
      <category>Agent infrastructure</category>
      <category>Voice agent</category>
      <description><![CDATA[<p>Cartesia introduced Multilingual Voices, a library of more than 50 voices that support up to 25 languages while retaining the same vocal identity. Customers can keep a voice ID across its supported languages and select a locale in speech generation requests. The offering is available through the voice library and API, with language and accent support varying by voice.</p><p><strong>Why it matters:</strong> Voice agent teams can expand language coverage without assigning a different speaker identity to each market. Buyers should validate each voice's supported locales and fallback behavior before deploying it across languages.</p><p>Impact: Medium. Verification: Verified. Type: Agent capability.</p><p>Evidence: <a href="https://www.cartesia.ai/blog/multilingual-voices">Official blog</a></p><p>Source: <a href="https://agenticindex.io/change-log/cartesia">Agentic Index change log</a>. Free to reuse with a link back. <a href="https://agenticindex.io/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>Forest's September release lets Claude, Dust and other MCP clients start Forest Workflows through its MCP server.</title>
      <link>https://agenticindex.io/change-log/forest-admin</link>
      <guid isPermaLink="false">agenticindex.io:change:forest-admin-17p4b5-2026-09-23</guid>
      <pubDate>Wed, 23 Sep 2026 12:00:00 GMT</pubDate>
      <category>Workflow orchestration</category>
      <category>Enterprise operations agent</category>
      <category>Agent infrastructure</category>
      <description><![CDATA[<p>Forest's September release lets Claude, Dust and other MCP clients start Forest Workflows through its MCP server. Decision steps now offer Automatic (Deterministic) execution, evaluating conditions against preceding Get Data steps without model interpretation during execution. Manual, AI assisted and Full AI modes remain available for decisions that need interpretation.</p><p><strong>Why it matters:</strong> Operations teams can make governed business processes available to external agents while keeping predictable routing under explicit rules. Buyers can distinguish where a model's judgment is necessary from the parts of a process that should behave consistently on every run.</p><p>Impact: Medium. Verification: Verified. Type: Workflow orchestration.</p><p>Evidence: <a href="https://forest.app/blog/forest-release-notes-september-2026">Official changelog</a></p><p>Source: <a href="https://agenticindex.io/change-log/forest-admin">Agentic Index change log</a>. Free to reuse with a link back. <a href="https://agenticindex.io/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>Arcade announced a new Snowflake toolkit that lets agents discover warehouses, databases, schemas, tables, and columns, then run queries…</title>
      <link>https://agenticindex.io/change-log/arcade</link>
      <guid isPermaLink="false">agenticindex.io:change:arcade-rvnbry-2026-09-23</guid>
      <pubDate>Wed, 23 Sep 2026 12:00:00 GMT</pubDate>
      <category>Integrations</category>
      <category>Agent infrastructure</category>
      <description><![CDATA[<p>Arcade announced a new Snowflake toolkit that lets agents discover warehouses, databases, schemas, tables, and columns, then run queries using the requesting user's identity. Existing Snowflake grants determine what the agent can access. The toolkit permits read only queries and blocks writes, schema changes, and role switches.</p><p><strong>Why it matters:</strong> Enterprise teams can give agents warehouse access while retaining existing user permissions and data policies. The read only boundary limits mutation risk, though query compute costs still need operational controls.</p><p>Impact: Medium. Verification: Verified. Type: Integrations.</p><p>Evidence: <a href="https://www.arcade.dev/blog/agent-optimized-toolkit-round-up/">Official blog</a></p><p>Source: <a href="https://agenticindex.io/change-log/arcade">Agentic Index change log</a>. Free to reuse with a link back. <a href="https://agenticindex.io/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>Prime Intellect made Prime Sandboxes generally available through its CLI and SDK and as part of its reinforcement learning stack.</title>
      <link>https://agenticindex.io/change-log/prime-intellect</link>
      <guid isPermaLink="false">agenticindex.io:change:prime-intellect-1fz57x-2026-09-23</guid>
      <pubDate>Wed, 23 Sep 2026 12:00:00 GMT</pubDate>
      <category>Deployment / data residency</category>
      <category>Agent infrastructure</category>
      <description><![CDATA[<p>Prime Intellect made Prime Sandboxes generally available through its CLI and SDK and as part of its reinforcement learning stack. Each sandbox runs a Linux microVM with its own kernel, supporting Docker Compose, background services and custom Docker images. Accounts start with capacity for 1,024 concurrent sandboxes.</p><p><strong>Why it matters:</strong> Teams training and evaluating agents can use VM isolation while retaining their existing Docker environment definitions. Native Docker and kernel support broaden the workloads they can test without operating the underlying VM fleet.</p><p>Impact: High. Verification: Verified. Type: Deployment / data residency.</p><p>Evidence: <a href="https://www.primeintellect.ai/blog/sandboxes">Official blog</a></p><p>Source: <a href="https://agenticindex.io/change-log/prime-intellect">Agentic Index change log</a>. Free to reuse with a link back. <a href="https://agenticindex.io/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>W&amp;B Weave: W&amp;B Server v0.85.0 adds links in both directions between Weave calls and the agent spans they produce or invoke.</title>
      <link>https://agenticindex.io/change-log/wandb-weave</link>
      <guid isPermaLink="false">agenticindex.io:change:wandb-weave-lffuaj-2026-09-23</guid>
      <pubDate>Wed, 23 Sep 2026 12:00:00 GMT</pubDate>
      <category>Observability / auditability</category>
      <category>Agent infrastructure</category>
      <description><![CDATA[<p>W&amp;B Server v0.85.0 adds links in both directions between Weave calls and the agent spans they produce or invoke. The same release adds a configurable process wide query parallelism budget, allowing deployments to reduce peak memory use when Weave workloads load large text heavy tables by trading off request concurrency.</p><p><strong>Why it matters:</strong> Agent operators can follow execution across call and span views when investigating behavior. Deployment owners can tune resource use for large analytical workloads instead of relying on the fixed default concurrency.</p><p>Impact: Medium. Verification: Partially Verified. Type: Observability / auditability.</p><p>Evidence: <a href="https://docs.wandb.ai/release-notes/server-releases">Official changelog</a></p><p>Source: <a href="https://agenticindex.io/change-log/wandb-weave">Agentic Index change log</a>. Free to reuse with a link back. <a href="https://agenticindex.io/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>FlowX.AI documented a Browser Automation node for Agent Builder, available from release 5.13.0 on SaaS.</title>
      <link>https://agenticindex.io/change-log/flowx-ai</link>
      <guid isPermaLink="false">agenticindex.io:change:flowx-ai-b7s3kq-2026-09-23</guid>
      <pubDate>Wed, 23 Sep 2026 12:00:00 GMT</pubDate>
      <category>Agent capability</category>
      <category>Agent builder</category>
      <category>Enterprise operations agent</category>
      <category>Agent infrastructure</category>
      <category>Multi-agent platform</category>
      <description><![CDATA[<p>FlowX.AI documented a Browser Automation node for Agent Builder, available from release 5.13.0 on SaaS. The node drives a real browser through web applications that have no API, filling multi page forms, navigating portals and retrieving results from a task written in plain language. It checks outcomes against the target site's recorded state rather than the agent's own report and keeps the browser session across workflow steps. Self hosted deployments receive it with the next LTS release family.</p><p><strong>Why it matters:</strong> Banks and insurers running agents on FlowX can now reach legacy portals and third party sites that expose no integration point from inside the same governed workflow, with every run logged. Verification against the site's recorded state is the detail to test in a pilot, since an agent reporting success on a form it never submitted is the usual failure in this category.</p><p>Impact: High. Verification: Verified. Type: Agent capability.</p><p>Evidence: <a href="https://docs.flowx.ai/5.9/ai-platform/agent-builder/browser-automation">Official documentation</a></p><p>Source: <a href="https://agenticindex.io/change-log/flowx-ai">Agentic Index change log</a>. Free to reuse with a link back. <a href="https://agenticindex.io/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>Mastra released @mastra/mcp 2.0.0, whose servers support only the July 28, 2026 MCP revision and require @mastra/core 1.68 or newer.</title>
      <link>https://agenticindex.io/change-log/mastra</link>
      <guid isPermaLink="false">agenticindex.io:change:mastra-4khz10-2026-09-22</guid>
      <pubDate>Tue, 22 Sep 2026 12:00:00 GMT</pubDate>
      <category>MCP / tool calling / API</category>
      <category>Agent infrastructure</category>
      <description><![CDATA[<p>Mastra released @mastra/mcp 2.0.0, whose servers support only the July 28, 2026 MCP revision and require @mastra/core 1.68 or newer. Tools that need caller input now suspend and resume through input_required continuations with signed request state. The release removes legacy initialization, session headers, standalone HTTP plus SSE transport, and earlier elicitation APIs.</p><p><strong>Why it matters:</strong> Teams upgrading existing MCP integrations need to revise transport and input handling code and verify client compatibility. Deployments serving older clients can retain supported 1.x servers alongside 2.x servers.</p><p>Impact: High. Verification: Verified. Type: MCP / tool calling / API.</p><p>Evidence: <a href="https://github.com/mastra-ai/mastra/releases/tag/@mastra%2Fcore@1.68.0">GitHub release</a></p><p>Source: <a href="https://agenticindex.io/change-log/mastra">Agentic Index change log</a>. Free to reuse with a link back. <a href="https://agenticindex.io/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>OpenRouter launched a Batch API for asynchronous chat completions, Responses, Messages, and embedding workloads across more than 70 models.</title>
      <link>https://agenticindex.io/change-log/openrouter</link>
      <guid isPermaLink="false">agenticindex.io:change:openrouter-167fg4-2026-09-22</guid>
      <pubDate>Tue, 22 Sep 2026 12:00:00 GMT</pubDate>
      <category>MCP / tool calling / API</category>
      <category>Agent infrastructure</category>
      <description><![CDATA[<p>OpenRouter launched a Batch API for asynchronous chat completions, Responses, Messages, and embedding workloads across more than 70 models. Developers submit an inline request array and poll for results within a 24 hour completion window, with token pricing typically discounted by 50%. Each batch runs on one eligible provider, and inputs and results remain stored for 30 days unless deleted.</p><p><strong>Why it matters:</strong> Evaluation, labeling, and backlog processing jobs can trade response latency for lower inference cost through one interface. Teams should check provider eligibility and retention requirements before moving sensitive or urgent workloads into batch processing.</p><p>Impact: High. Verification: Verified. Type: MCP / tool calling / API.</p><p>Evidence: <a href="https://openrouter.ai/blog/announcements/batch-api/">Official blog</a></p><p>Source: <a href="https://agenticindex.io/change-log/openrouter">Agentic Index change log</a>. Free to reuse with a link back. <a href="https://agenticindex.io/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>Smallest AI added POST /waves/v1/auth/token so servers can issue temporary credentials for browser and mobile speech clients while…</title>
      <link>https://agenticindex.io/change-log/smallest-ai</link>
      <guid isPermaLink="false">agenticindex.io:change:smallest-ai-1gpsnt-2026-09-22</guid>
      <pubDate>Tue, 22 Sep 2026 12:00:00 GMT</pubDate>
      <category>MCP / tool calling / API</category>
      <category>Voice agent</category>
      <category>Agent infrastructure</category>
      <category>Customer support agent</category>
      <description><![CDATA[<p>Smallest AI added POST /waves/v1/auth/token so servers can issue temporary credentials for browser and mobile speech clients while retaining the API key. Tokens last 30 to 900 seconds, defaulting to 300, and authorize supported speech synthesis, transcription, speech to speech, and voice listing routes. They cannot authorize voice cloning, LLM chat completions, analytics, or further token creation; usage remains billed to the issuing key.</p><p><strong>Why it matters:</strong> Teams can expose speech inference to clients with narrower credentials instead of distributing a persistent API key. Integrators must use the same region for token issuance and inference, and account for open WebSocket sessions continuing after token expiry.</p><p>Impact: Medium. Verification: Verified. Type: MCP / tool calling / API.</p><p>Evidence: <a href="https://docs.smallest.ai/models/changelog/general/2026/9/22">Official changelog</a></p><p>Source: <a href="https://agenticindex.io/change-log/smallest-ai">Agentic Index change log</a>. Free to reuse with a link back. <a href="https://agenticindex.io/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>TrueFoundry 0.174.0 enables plan based feature gating for nonpaying tenants on managed control planes.</title>
      <link>https://agenticindex.io/change-log/truefoundry</link>
      <guid isPermaLink="false">agenticindex.io:change:truefoundry-sxsc3s-2026-09-22</guid>
      <pubDate>Tue, 22 Sep 2026 12:00:00 GMT</pubDate>
      <category>Pricing / packaging</category>
      <category>Agent infrastructure</category>
      <description><![CDATA[<p>TrueFoundry 0.174.0 enables plan based feature gating for nonpaying tenants on managed control planes. Resource caps block further creation, and capabilities including agents, MCP tool approval, custom roles and SSO require higher plans. Existing configurations and traffic continue, but gated features disappear from the Developer plan UI; paying customers and self hosted or dedicated control planes are unaffected.</p><p><strong>Why it matters:</strong> Teams using the Developer plan for a pilot must account for paid access when evaluating governance controls and expanding agent workloads. A successful existing deployment does not guarantee that its configuration remains manageable under the same plan.</p><p>Impact: High. Verification: Verified. Type: Pricing / packaging.</p><p>Evidence: <a href="https://www.truefoundry.com/docs/change-announcements/plan-based-feature-gating-v0.174.0">Official documentation</a></p><p>Source: <a href="https://agenticindex.io/change-log/truefoundry">Agentic Index change log</a>. Free to reuse with a link back. <a href="https://agenticindex.io/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>Firecrawl launched Alexandria, a common interface for agents to discover and retrieve information from official data providers, custom…</title>
      <link>https://agenticindex.io/change-log/firecrawl</link>
      <guid isPermaLink="false">agenticindex.io:change:firecrawl-3n8fuc-2026-09-22</guid>
      <pubDate>Tue, 22 Sep 2026 12:00:00 GMT</pubDate>
      <category>MCP / tool calling / API</category>
      <category>Agent infrastructure</category>
      <description><![CDATA[<p>Firecrawl launched Alexandria, a common interface for agents to discover and retrieve information from official data providers, custom connectors and its Research, Developer and Government indexes. Agents can query providers and use specialized tools alongside live web search through Firecrawl.</p><p><strong>Why it matters:</strong> Teams can expand an agent's research coverage without maintaining a separate connection and data format for each provider.</p><p>Impact: High. Verification: Verified. Type: MCP / tool calling / API.</p><p>Evidence: <a href="https://www.firecrawl.dev/blog/introducing-alexandria-series-b">Official blog</a></p><p>Source: <a href="https://agenticindex.io/change-log/firecrawl">Agentic Index change log</a>. Free to reuse with a link back. <a href="https://agenticindex.io/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>LangChain: LangGraph 1.2.12 added the optional response_schema parameter to interrupt().</title>
      <link>https://agenticindex.io/change-log/langchain</link>
      <guid isPermaLink="false">agenticindex.io:change:langchain-1c8vmm-2026-09-21</guid>
      <pubDate>Mon, 21 Sep 2026 12:00:00 GMT</pubDate>
      <category>Human approval / guardrails</category>
      <category>Agent infrastructure</category>
      <category>Multi-agent platform</category>
      <description><![CDATA[<p>LangGraph 1.2.12 added the optional response_schema parameter to interrupt(). It exposes the expected response as JSON Schema and validates resumed values when supplied with a Pydantic model, TypedDict, or dataclass. Raw JSON Schema dictionaries are passed through without validation.</p><p><strong>Why it matters:</strong> Teams building human approval workflows gain a more explicit contract at decision points, helping keep malformed responses out of persisted agent state.</p><p>Impact: Medium. Verification: Verified. Type: Human approval / guardrails.</p><p>Evidence: <a href="https://github.com/langchain-ai/langgraph/releases/tag/1.2.12">GitHub release</a></p><p>Source: <a href="https://agenticindex.io/change-log/langchain">Agentic Index change log</a>. Free to reuse with a link back. <a href="https://agenticindex.io/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>Sourcegraph Cloud updated Code Finder to accept the repository as a separate parameter and expanded read_live_changesets so Agentic Batch…</title>
      <link>https://agenticindex.io/change-log/sourcegraph</link>
      <guid isPermaLink="false">agenticindex.io:change:sourcegraph-2k6okp-2026-09-21</guid>
      <pubDate>Mon, 21 Sep 2026 12:00:00 GMT</pubDate>
      <category>MCP / tool calling / API</category>
      <category>Agent infrastructure</category>
      <category>Coding agent</category>
      <description><![CDATA[<p>Sourcegraph Cloud updated Code Finder to accept the repository as a separate parameter and expanded read_live_changesets so Agentic Batch Changes can inspect live CI checks and branch state before requesting help. The same release adds structured publish credential problems to prepare_batch_spec metadata and enables repository fetch history logs. Deep Search gains safe date functions for analyzing commit activity and time windows.</p><p><strong>Why it matters:</strong> Teams integrating code agents should review tool argument handling and can give agents more evidence before escalating failed changes to an engineer. Repository fetch history also helps administrators diagnose whether stale source data affected an investigation.</p><p>Impact: Medium. Verification: Verified. Type: MCP / tool calling / API.</p><p>Evidence: <a href="https://sourcegraph.com/changelog/2026-09-21">Official changelog</a></p><p>Source: <a href="https://agenticindex.io/change-log/sourcegraph">Agentic Index change log</a>. Free to reuse with a link back. <a href="https://agenticindex.io/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>Vapi added a serviceTier setting that lets assistants request faster OpenAI processing for supported GPT-5.6 and GPT-5.5 models.</title>
      <link>https://agenticindex.io/change-log/vapi</link>
      <guid isPermaLink="false">agenticindex.io:change:vapi-14pxd8-2026-09-21</guid>
      <pubDate>Mon, 21 Sep 2026 12:00:00 GMT</pubDate>
      <category>MCP / tool calling / API</category>
      <category>Agent infrastructure</category>
      <category>Customer support agent</category>
      <category>Voice agent</category>
      <description><![CDATA[<p>Vapi added a serviceTier setting that lets assistants request faster OpenAI processing for supported GPT-5.6 and GPT-5.5 models. Its September 21 update also adds provider request IDs to call logs for language model, transcription, and voice services when customers bring their own keys.</p><p><strong>Why it matters:</strong> Voice teams can test a latency and cost tradeoff without changing their agent workflow, while request IDs make provider support investigations easier to correlate with specific calls. Fast processing uses the provider's corresponding rates and may be downgraded under load.</p><p>Impact: Medium. Verification: Verified. Type: MCP / tool calling / API.</p><p>Evidence: <a href="https://docs.vapi.ai/whats-new/2026/9/21">Official changelog</a></p><p>Source: <a href="https://agenticindex.io/change-log/vapi">Agentic Index change log</a>. Free to reuse with a link back. <a href="https://agenticindex.io/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>Temporal introduced Amazon Bedrock AgentCore Runtime as a compute provider for Serverless Workers in prerelease.</title>
      <link>https://agenticindex.io/change-log/temporal</link>
      <guid isPermaLink="false">agenticindex.io:change:temporal-zc0scx-2026-09-21</guid>
      <pubDate>Mon, 21 Sep 2026 12:00:00 GMT</pubDate>
      <category>Integrations</category>
      <category>Agent infrastructure</category>
      <description><![CDATA[<p>Temporal introduced Amazon Bedrock AgentCore Runtime as a compute provider for Serverless Workers in prerelease. Teams can try the integration through self hosted Temporal, with workers started as task demand rises and workflow progress retained across worker failures. Temporal Cloud access remains subject to approval.</p><p><strong>Why it matters:</strong> Teams building agents on AWS can evaluate elastic worker capacity without maintaining a continuously running fleet. Buyers should distinguish the publicly usable self hosted path from the restricted Cloud prerelease when planning adoption.</p><p>Impact: Medium. Verification: Verified. Type: Integrations.</p><p>Evidence: <a href="https://temporal.io/blog/amazon-bedrock-agentcore-with-temporal-serverless-workers">Official blog</a></p><p>Source: <a href="https://agenticindex.io/change-log/temporal">Agentic Index change log</a>. Free to reuse with a link back. <a href="https://agenticindex.io/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>Confident AI launched Voice AI Evals with caller simulations covering interruptions, background noise, and turn patterns.</title>
      <link>https://agenticindex.io/change-log/confident-ai</link>
      <guid isPermaLink="false">agenticindex.io:change:confident-ai-8swabv-2026-09-21</guid>
      <pubDate>Mon, 21 Sep 2026 12:00:00 GMT</pubDate>
      <category>Observability / auditability</category>
      <category>Agent infrastructure</category>
      <description><![CDATA[<p>Confident AI launched Voice AI Evals with caller simulations covering interruptions, background noise, and turn patterns. Seven deterministic audio metrics assess naturalness, intelligibility, consistency, turn taking, responsiveness, audio integrity, and reliability alongside existing conversation evaluations. Supported connections include SIP, phone calls, WebRTC, WebSockets, and LiveKit integrations.</p><p><strong>Why it matters:</strong> Teams evaluating voice agents can test audible behavior and conversational correctness in a shared workflow. This exposes failures that transcript scoring alone misses, such as poor interruption handling or unusable audio.</p><p>Impact: High. Verification: Verified. Type: Observability / auditability.</p><p>Evidence: <a href="https://www.confident-ai.com/blog/launch-week-q3-2026-day-1-voice-ai-evals">Official blog</a></p><p>Source: <a href="https://agenticindex.io/change-log/confident-ai">Agentic Index change log</a>. Free to reuse with a link back. <a href="https://agenticindex.io/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>Delight.ai introduces Intelligent Voice Handoff, which keeps a caller connected while the agent reaches and briefs the person taking over.</title>
      <link>https://agenticindex.io/change-log/sendbird</link>
      <guid isPermaLink="false">agenticindex.io:change:sendbird-x0rpe6-2026-09-21</guid>
      <pubDate>Mon, 21 Sep 2026 12:00:00 GMT</pubDate>
      <category>Workflow orchestration</category>
      <category>Customer support agent</category>
      <category>Agent infrastructure</category>
      <category>Voice agent</category>
      <description><![CDATA[<p>Delight.ai introduces Intelligent Voice Handoff, which keeps a caller connected while the agent reaches and briefs the person taking over. Answer detection distinguishes people from voicemail, while recovery handles busy lines and unanswered calls by returning to the caller, leaving a message, or creating a follow up case. Supported integrations can attach the summary, transcript, and sentiment to a ticket before the transfer.</p><p><strong>Why it matters:</strong> Support teams can preserve the work already completed by an AI agent when a case needs human judgment. Failed transfers retain a follow up path, reducing the risk of callers being stranded between automated and human support.</p><p>Impact: Medium. Verification: Verified. Type: Workflow orchestration.</p><p>Evidence: <a href="https://delight.ai/blog/product/introducing-intelligent-voice-handoff">Official blog</a></p><p>Source: <a href="https://agenticindex.io/change-log/sendbird">Agentic Index change log</a>. Free to reuse with a link back. <a href="https://agenticindex.io/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>xpander.ai added a Secrets section that declares an agent's required credentials, validates personal connections, and resolves secrets on…</title>
      <link>https://agenticindex.io/change-log/xpander-ai</link>
      <guid isPermaLink="false">agenticindex.io:change:xpander-ai-1gn0f1-2026-09-20</guid>
      <pubDate>Sun, 20 Sep 2026 12:00:00 GMT</pubDate>
      <category>Human approval / guardrails</category>
      <category>Agent infrastructure</category>
      <description><![CDATA[<p>xpander.ai added a Secrets section that declares an agent's required credentials, validates personal connections, and resolves secrets on every turn. Its September 20 release also adds skill visibility scopes, grants for individual agents, and a public skill publishing API. Gated mode now holds web fetch and search calls for approval, with gated command editing available for Claude Code, Codex, and OpenCode agents.</p><p><strong>Why it matters:</strong> Administrators gain more explicit control over credential availability, reusable skills, and outbound web activity. Teams can apply approval policies across supported coding harnesses while keeping personal connections associated with the user.</p><p>Impact: High. Verification: Partially Verified. Type: Human approval / guardrails.</p><p>Evidence: <a href="https://docs.xpander.ai/changelog/product-updates">Official changelog</a></p><p>Source: <a href="https://agenticindex.io/change-log/xpander-ai">Agentic Index change log</a>. Free to reuse with a link back. <a href="https://agenticindex.io/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>AutoGPT Platform v0.8.0 generates secrets per installation, refuses the previously published default encryption key, and removes legacy…</title>
      <link>https://agenticindex.io/change-log/autogpt</link>
      <guid isPermaLink="false">agenticindex.io:change:autogpt-g25165-2026-09-19</guid>
      <pubDate>Sat, 19 Sep 2026 12:00:00 GMT</pubDate>
      <category>Security / enterprise</category>
      <category>Agent builder</category>
      <category>Agent infrastructure</category>
      <category>Multi-agent platform</category>
      <description><![CDATA[<p>AutoGPT Platform v0.8.0 generates secrets per installation, refuses the previously published default encryption key, and removes legacy HS256 JWT verification. Existing installations using the defaults must migrate stored integration credentials to a new key. The release also adds scheduled expert routines, spending threshold approvals, and restrictions that let experts run only installed workflows with granted credentials.</p><p><strong>Why it matters:</strong> Self hosted operators need to plan the credential migration before upgrading to avoid startup failures or losing access to connected services. Teams delegating recurring work gain clearer controls over cost and authorized actions.</p><p>Impact: High. Verification: Verified. Type: Security / enterprise.</p><p>Evidence: <a href="https://github.com/Significant-Gravitas/AutoGPT/releases/tag/autogpt-platform-beta-v0.8.0">GitHub release</a></p><p>Source: <a href="https://agenticindex.io/change-log/autogpt">Agentic Index change log</a>. Free to reuse with a link back. <a href="https://agenticindex.io/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>Noma Security is available through the AWS Security Hub Extended console as its AI security partner, so enterprises can turn on AI…</title>
      <link>https://agenticindex.io/change-log/noma-security</link>
      <guid isPermaLink="false">agenticindex.io:change:noma-security-zkqq6f-2026-09-18</guid>
      <pubDate>Fri, 18 Sep 2026 12:00:00 GMT</pubDate>
      <category>Integrations</category>
      <category>Security / SOC agent</category>
      <category>Agent infrastructure</category>
      <description><![CDATA[<p>Noma Security is available through the AWS Security Hub Extended console as its AI security partner, so enterprises can turn on AI security monitoring from within AWS.</p><p><strong>Why it matters:</strong> Buying through the console an organization already uses shortens procurement. Check which Noma capabilities are included in the Security Hub offering.</p><p>Impact: Medium. Verification: Partially Verified. Type: Integrations.</p><p>Evidence: <a href="https://noma.security/blog/aws-and-noma-building-the-foundation-for-secure-enterprise-ai">Official blog</a></p><p>Source: <a href="https://agenticindex.io/change-log/noma-security">Agentic Index change log</a>. Free to reuse with a link back. <a href="https://agenticindex.io/use-this-data">Terms</a>.</p>]]></description>
    </item>
  </channel>
</rss>
