SShortSingh.
Back to feed

GPT-Live-1.1 pricing: how active and standby minutes are billed

0
·3 views

OpenAI bills GPT-Live-1.1 voice sessions by time rather than tokens, charging $0.05 per active minute and $0.02 per standby minute, calculated per second without rounding up. Backend model and tool calls are billed separately at their usual rates. Active time covers speaking, silence before the idle timeout expires, and waiting for backend processing, while standby applies only to WebRTC sessions when inference is paused. Each WebRTC session also incurs a 15-second setup charge that is refunded once the session runs. Developers can control costs by setting a speech wake policy and an idle timeout between 5 and 60 seconds, since omitting the timeout keeps inference active and prevents standby pricing from applying.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

hexbin-heatmap: aggregating points into H3 hexagons and geohash cells, in the browser and CLI

Plotting tens of thousands of points on a map makes dense areas collapse into a solid blob, hiding how many points each location holds. The usual remedy is to aggregate points into grid cells and color those cells instead, though choosing a grid, scaling colors across wide value ranges, and handling cells that cross the 180° meridian add complexity. The open-source hexbin-heatmap project tackles these issues by binning CSV or GeoJSON points into H3 hexagons or geohash cells and rendering them as a choropleth in MapLibre with a resolution slider. The same aggregation logic is also available as a command-line tool that outputs GeoJSON or CSV, with each cell carrying count, sum, and mean values. The web app runs entirely in the browser so files are never uploaded, and the project includes setup instructions for local development, testing, and building.

0
ProgrammingDEV Community ·

nord-sahara-wgs84: a step-by-step Python tool for converting Algerian Nord Sahara 1959 coordinates to WGS 84

Many Algerian maps, survey plans and well reports record coordinates in the Nord Sahara 1959 datum, which is based on the Clarke 1880 ellipsoid, while GPS devices and web maps use WGS 84. Plotting Nord Sahara points on a WGS 84 map without conversion puts them in noticeably wrong locations. The author built nord-sahara-wgs84, a dependency-free Python library and command-line tool that carries out the conversion step by step and checks each figure against PROJ. It covers datum transformations in both directions, UTM projections for zones 29N to 32N on both datums, and all ten published Helmert transformations from the EPSG database, which Nord Sahara 1959 lacks grid files for. The tool is intended as an educational project for making the underlying mathematics readable, and it requires Python 3.13 or newer.

0
ProgrammingDEV Community ·

Ruby2Shell: Critical Ruby flaw enables unauthenticated RCE in Rails APIs

A one-byte heap overflow in Ruby's string case conversion, dubbed Ruby2Shell, has been tracked as CVE-2026-132825 and GHSA-34m4-m9fh-gqp5. Researchers say it is reachable without authentication in a plain Rails app, and affects Ruby 2.4.0 through 3.3.13, 3.4.0 through 3.4.12, and 4.0.0 through 4.0.9. The bug stems from legacy single-byte encodings where the German sharp s expands to two bytes on uppercase, and the fix is upgrading Ruby to 3.3.14, 3.4.13, or 4.0.10 rather than updating gems. Ruby versions 3.2 and earlier receive no patch, and Veria Labs plans to publish a proof-of-concept exploit on November 25, 2026 unless vendors release fixes first. Users are advised to check the Ruby version running in production environments, not just local machines.

0
ProgrammingDEV Community ·

Ruby2Shell: Kritische Rails-Sicherheitslücke betrifft bestimmte Ruby-Versionen

Eine als Ruby2Shell bezeichnete Schwachstelle (CVE-2026-132825) ermöglicht laut Forschern eine Remote Code Execution ohne Authentifizierung in Standard-Rails-Anwendungen. Der Fehler ist ein Ein-Byte-Heap-Overflow in Rubys Großschreibung von Strings in Single-Byte-Kodierungen, ausgelöst durch das deutsche scharfe s. Betroffen sind Ruby 2.4.0 bis 3.3.13, 3.4.0 bis 3.4.12 sowie 4.0.0 bis 4.0.9; die Lösung ist ein Ruby-Upgrade auf 3.3.14, 3.4.13 oder 4.0.10, da ein Gem-Update nicht ausreicht. Ruby hat die Lücke am 18. November 2026 zusammen mit sechs weiteren Schwachstellen veröffentlicht. Die Forscher von Veria Labs wollen ihren Exploit am 25. November 2026 oder später veröffentlichen, falls bis dahin noch keine Fixes ausgeliefert sind.