DoublewordDoubleword
Get started

Intro to Doubleword Inference

Doubleword provides three styles of inference, each optimized for different workloads. Pricing scales with how fast you need each response, meaning async and batch inference offer significant cost savings over realtime pricing — the more latency flexibility you have, the lower the rate.

All three styles use OpenAI or Anthropic-compatible APIs. Not every model is available in every tier — visit the model catalog to see tier availability and the price breakdown per model.

RealtimeAsyncBatch
How it worksShared, rate-limited request-response endpointOpen Responses API with service_tier: "flex" or Autobatcher1Upload JSONL file, or use Autobatcher1
LatencyImmediateMinutes, ~1 min to first tokenHours (24h SLA)
CostStandard pricingReduced pricingLowest pricing
API changeNone, drop-in OpenAI or Anthropic replacementSet service_tier: "flex", or swap SDK import for AutobatcherPrepare a JSONL file, or swap SDK import for Autobatcher
Best forModel testing, development, prototyping, prompt iterationAgentic workflows, background pipelines, production workloadsDataset processing, evaluations, bulk generation

Realtime Inference

Realtime inference provides an immediate request-response experience using the standard OpenAI-compatible API. The self-serve endpoint is designed for development and testing, making it easy to evaluate models, iterate on prompts and prototype your application.

Self-serve Realtime runs on shared, rate-limited capacity. For production realtime workloads, talk to us about a dedicated deployment. We’ll review your workload and optimise the infrastructure around your requirements to deliver the best combination of throughput, latency, caching and price.

If your workload doesn’t require an immediate response, Async and Batch offer significantly lower pricing

Use the Chat Completions API or the Open Responses API with service_tier: "priority". Supports background: true to submit and poll for the result.

Start testing with Realtime→

Talk to us about production Realtime →


Async Inference

Async inference strikes the balance between realtime and batch — faster turnaround than batch, with higher throughput than realtime — all at reduced cost. Submitted work is guaranteed to start processing within a minute, which makes it ideal for background agents that keep making progress without paying realtime rates. Two approaches:

  • Inference APIs — Set service_tier: "flex" on the Responses or Chat Completions APIs for native async support with background polling

    Swap the OpenAI SDK for Autobatcher to run existing code async
  • Autobatcher — The Autobatcher's AsyncOpenAI client automatically runs existing Chat Completions code asynchronously with a single import change

Best suited for:

  • Multi-step agentic workflows where each call doesn't need an instant response
  • Background content generation and classification pipelines
  • Any application code that can tolerate short async delays
  • Teams migrating from OpenAI who want immediate cost savings with zero refactoring

Get started with Async Inference →


Batch Inference

Batch inference is designed for large-scale data processing workloads that run outside of your application code. You upload requests as JSONL files and retrieve results when processing is complete.

With a 24-hour SLA, batch inference offers the deepest cost savings — ideal for workloads where turnaround time is measured in hours, not seconds.

You can prepare requests as JSONL files directly, or use the Autobatcher's BatchOpenAI client to get batch pricing from existing Chat Completions code without writing JSONL files yourself.

Best suited for:

  • Large dataset processing and transformation
  • Model evaluations and benchmarking
  • Bulk content generation and classification
  • Research workflows and data enrichment

Get started with Batch Inference →

Footnotes

  1. Autobatcher is a client library that exposes the same interface as the OpenAI SDK — swap the SDK for autobatcher to run your existing code as async or batch. See the async and batch pages for details. 2