<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>RunPod — The AI Toolchain</title>
    <link>https://aitoolchain.io/tools/runpod</link>
    <description>New releases and features in RunPod, tracked by The AI Toolchain.</description>
    <language>en</language>
    <lastBuildDate>Sat, 01 Aug 2026 00:00:00 GMT</lastBuildDate>
    <atom:link href="https://aitoolchain.io/tools/runpod/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>RunPod New ReleaseBatch Jobs (BETA)</title>
      <link>https://docs.runpod.io/serverless/batch-jobs</link>
      <guid isPermaLink="true">https://docs.runpod.io/serverless/batch-jobs</guid>
      <pubDate>Sat, 01 Aug 2026 00:00:00 GMT</pubDate>
      <description>RunPod launches Batch Jobs (BETA) for Serverless endpoints, adding a full async bulk-inference API via REST API v2.
• Adds `POST /v2/{endpoint_id}/batch` to create a new batch (optionally with initial requests as a JSON array) against a Serverless endpoint.
• Adds `POST /v2/{endpoint_id}/batch/{id}/requests` to append requests to a DRAFT batch; request body is limited to 10 MiB per call and can be called multiple times to build large batches incrementally.
• Adds `POST /v2/{endpoint_id}/batch/{id}/finalize` to lock a batch and make it eligible for execution, transitioning status from `DRAFT` to `FINALIZED`.
• Adds `GET /v2/{endpoint_id}/batch/{id}` to poll batch progress via `requestTotal`, `requestInProgress`, `requestCompleted`, and `requestFailed` counts; `createdAt` is a Unix epoch timestamp in milliseconds.
• Adds `GET /v2/{endpoint_id}/batch/{id}/requests` to retrieve paginated child-request results including per-request `status`, `output`, `error`, `startedAt`, and `completedAt`; supports `offset` and `limit` query parameters with a `hasMore` field.
• Adds `POST /v2/{endpoint_id}/batch/{id}/cancel` to cancel a batch; queued requests are cancelled immediately (not billed) while in-progress requests finish and are billed normally.
• Adds `DELETE /v2/{endpoint_id}/batch/{id}/requests/{requestId}` to remove a single request from a DRAFT batch.
• Adds `PUT /v2/{endpoint_id}/batch/{id}` to update batch attributes such as display name.
• Adds `GET /v2/{endpoint_id}/batch` to list all batches for an endpoint, newest first.
• Batch jobs run on dedicated workers isolated from standard `/run` traffic, so submitting a batch never delays interactive requests.
• Batch limits: 10 active batches per endpoint, 5,000 requests per batch, 50,000 queued requests per endpoint (up to 1,000,000 daily for enterprise); limits are configurable for enterprise accounts.
• Adds webhook event notifications when a batch reaches a terminal state (`FAILED` or `CANCELLED`), if a webhook subscription is configured for batch events.
• Adds a Batch tab in the RunPod console for each endpoint, showing batch name, status, progress counts, per-request rows with timestamps and error messages, and links to child request detail views.
• Adds AWS ECR Integration (BETA) allowing private container images to be pulled into Pods and Serverless endpoints via ECR delegation, without migrating registries or managing credentials.
Breaking changes:
• REST API v1 will be retired on November 15, 2026; existing integrations must migrate to REST API v2 at the new base URL `https://api.runpod.io/v2` before that date.
• The GraphQL API will be retired in early 2027; new integrations should use REST API v2.</description>
    </item>
    <item>
      <title>RunPod New ReleaseBatch Jobs (BETA)</title>
      <link>https://docs.runpod.io/serverless/advanced-workflows/batch-jobs</link>
      <guid isPermaLink="true">https://docs.runpod.io/serverless/advanced-workflows/batch-jobs</guid>
      <pubDate>Sat, 01 Aug 2026 00:00:00 GMT</pubDate>
      <description>RunPod launches Batch Jobs (BETA) with a full REST API for submitting, managing, and polling large async inference workloads on Serverless endpoints.
• New `POST /v2/{endpoint_id}/batch` endpoint creates a batch job, optionally seeding it with an initial array of requests (each matching the standard `/run` shape with an `input` field).
• New `POST /v2/{endpoint_id}/batch/{id}/requests` endpoint appends additional requests to a DRAFT batch; accepts up to 10 MiB per call and can be called multiple times incrementally.
• New `POST /v2/{endpoint_id}/batch/{id}/finalize` endpoint locks the batch and makes it eligible for execution, transitioning status to `FINALIZED`.
• New `GET /v2/{endpoint_id}/batch/{id}` endpoint returns a batch summary including `requestTotal`, `requestInProgress`, `requestCompleted`, and `requestFailed` counts for progress polling.
• New `GET /v2/{endpoint_id}/batch/{id}/requests` endpoint returns paginated child-request results with per-request `status`, `output`, `error`, `startedAt`, and `completedAt` fields; supports `offset` and `limit` query parameters, with a `hasMore` field indicating remaining pages.
• New `POST /v2/{endpoint_id}/batch/{id}/cancel` endpoint cancels a batch; queued requests are cancelled and not billed, while in-progress requests complete normally.
• New `GET /v2/{endpoint_id}/batch` endpoint lists all batches for an endpoint, newest first.
• New `PUT /v2/{endpoint_id}/batch/{id}` endpoint updates batch attributes such as display name.
• New `DELETE /v2/{endpoint_id}/batch/{id}/requests/{requestId}` endpoint removes a single request from a DRAFT batch.
• Batch jobs run on dedicated workers isolated from standard `/run` traffic, so submitting a batch never delays interactive requests; limits are 10 active batches per endpoint, 5,000 requests per batch, and 50,000 queued requests per endpoint (up to 1,000,000 daily for enterprise).
• Console Batch tab on each endpoint shows all batches with name, status, and progress counts, plus a detail view with per-request rows, timestamps, and error messages sorted failures-first.
• Webhook and Console Inbox notifications fire once when a batch reaches a terminal state (`FAILED` or `CANCELLED`), including batch ID, endpoint name, status, and completed/failed/total counts.
• Batch jobs are billed at the same rate as standard serverless requests; flex worker discounts apply for enterprise customers.</description>
    </item>
    <item>
      <title>RunPod New ReleaseREST API v2</title>
      <link>https://docs.runpod.io/api-reference-v2/overview</link>
      <guid isPermaLink="true">https://docs.runpod.io/api-reference-v2/overview</guid>
      <pubDate>Sat, 01 Aug 2026 00:00:00 GMT</pubDate>
      <description>RunPod REST API v2 is generally available, adding catalog endpoints, pod log streaming, and Serverless observability at a new base URL.
• New base URL `https://api.runpod.io/v2` for all REST API v2 requests, with reorganized resource paths and standardized request/response shapes.
• New `GET https://api.runpod.io/v2/openapi.json` endpoint returns the complete OpenAPI specification for client generation, request validation, and tooling integration.
• New catalog endpoints let you browse available GPU types, CPU types, and data centers programmatically.
• New pod log streaming capability available via REST API v2.
• New Serverless observability features available via REST API v2.
• New `/runpod:migrate` command (via the Runpod skills plugin in a coding agent) automatically migrates v1 or GraphQL integrations to v2.
• New ECR Integration (BETA) lets you pull private container images from AWS ECR into Pods and Serverless endpoints without migrating registries or managing credentials.
Breaking changes:
• REST API v1 will be retired on November 15, 2026 — existing v1 integrations must be migrated to REST API v2 before that date.
• The GraphQL API will be retired in early 2027 — new integrations should use REST API v2.</description>
    </item>
  </channel>
</rss>
