Data and AI releases

152 this month · 172 companies

Inference New Serverless mode: Ultra-fast (Preview) Ultra-fast is a new high-speed Serverless mode, now in...

PreviewNot yet verified

Inference New Serverless mode: Ultra-fast (Preview) Ultra-fast is a new high-speed Serverless mode, now in Preview, for highly latency-sensitive applications. Ultra-fast variants aim for 6-8x generation speed, and up to 10x for agentic coding tasks. Like Fast, it is not a different model, so output quality is the same.

AI agentsPricingPerformance

Read on docs.fireworks.ai

Also shipped Nov 3, 2026Fireworks AI in November 2026 →

Gemini Enterprise: Salesforce federated data store

Connecting a Salesforce data source with Gemini Enterprise using data federation is generally available (GA). You can use the Gemini Enterprise app assistant to search across your Salesforce accounts, contacts, opportunities, cases, leads, and custom objects, get answers grounded in that content, and create, update, and delete records without needing to...

GA
Source ↗

More from Fireworks AI platformEvery Fireworks AI platform release →

Errors identify their source

Fireworks AI updated its error reporting to provide more granular source identification for failures, including new error codes for parsing and transport issues.

Update
Source ↗

Failure traces are saved locally

Failed model trajectories now generate private JSONL traces in the system temporary directory. These traces include request data, token IDs, and exception chains to help developers identify whether failures originated from the model, tokenizer, or renderer.

Update
Source ↗

Errors identify their source

Before 1.2.27, the sidecar returned HTTP 502 for two failures that weren't server-side: tito_model_malformed_output (unparseable model output) and tito_upstream_error (any sampling exception, including client timeouts and dropped connections). They are replaced by: tito_sdk_parse_error (422): the output couldn't be parsed into an assistant or tool message.

Update
Source ↗

Unparseable trajectories are discarded

A parse failure makes the whole trajectory untrainable, including earlier successful turns. The cookbook RL loop drops it without retrying or stopping the run, and other rollouts continue. Parse failures don't count toward the infrastructure circuit breaker, which now classifies transient failures more accurately and reports failure counts by reason.

Update
Source ↗

Failure traces are saved locally

Each failed trajectory leaves a private JSONL trace (request, prepared token IDs, raw completion, exception chain) in fireworks-tito-traces under the system temp directory, capped at 256 MiB. Traces from clean trajectories are deleted, and failures rejected by cookbook adapters use the same location and limits.

Update
Source ↗