o1-mini (US)

Azure OpenAI chat

o1-mini (US) is an Azure OpenAI chat model.Input is priced at $1.21/M tokens and output at $4.84/M tokens. Route o1-mini (US) via Future AGI's Agent Command Center for unified observability, caching, and 15 routing strategies including cost-optimized fallback.

Pricing source: litellm Last verified: Oct 22, 2026 View source ↗
Cost calculator

Estimate o1-mini (US) spend

Pick a workload, fine-tune the sliders, and see the monthly bill.

~3K in / ~400 out · 5K req/day
3,000
0200,000
400
016,000
5,000
01,000,000
cached @ $0.6050/M
Per request
$0.005566
in $0.003630 · out $0.001936
Per day
$27.83
5,000 requests
Per month
$847
152,188 requests

Estimate uses $1.21/M input · $4.84/M output. Provider pricing changes. Production costs vary with retries, streaming overhead, and tool-call rounds.
Want this for free? Cache + route via Agent Command Center — first 100K requests and 100K cache hits free every month.

Pricing

Per-token rates, expressed in USD per 1M tokens. Verified Oct 22, 2026.

Input $1.21/M
Output $4.84/M
Blended (3:1 in:out) $2.12/M
Cross-model comparable price
Cached input $0.605/M
Batch input $0.605/M
Batch output $2.42/M

Context & limits

Context window
—
Max input
—
Max output
—
Modalities
text

Capabilities

  • Function calling — not advertised
  • Parallel tool calls — not advertised
  • Vision input — not advertised
  • Audio input — not advertised
  • Audio output — not advertised
  • PDF input — not advertised
  • Streaming ✓ supported
  • Structured output — not advertised
  • Prompt caching — not advertised
  • Reasoning — not advertised

Strengths & caveats — when to pick o1-mini (US)

Data-driven from o1-mini (US)'s percentile within chat peers.

Where it's strong

Watch out for

  • !agentic workflows — no advertised function-calling; use a tool-capable model and route via Agent Command Center for fallback
  • !strict structured output — no JSON-schema enforcement, expect retry loops

Benchmarks pending

We haven't logged public benchmark scores for o1-mini (US) yet. Have one to contribute? Submit a source — citations help us prioritise.

Try it

Call o1-mini (US) via Agent Command Center

One OpenAI-compatible endpoint. Routing, fallback, semantic caching, guardrails, and cost tracking come along for the ride. First 100K requests + 100K cache hits free every month.

SDK
Native Future AGI client (agentcc / @agentcc/client). Per-call metadata — provider, cost, latency, cache hit, request id — is returned on x-agentcc-* response headers, so any HTTP client can read it.
# o1-mini (US) via the Agent Command Center Python SDK
# pip install agentcc
import os
from agentcc import AgentCC

client = AgentCC(
    api_key=os.environ["AGENTCC_API_KEY"],   # from app.futureagi.com → Settings → API Keys
    base_url="https://gateway.futureagi.com/v1",
)

resp = client.chat.completions.create(
    model="azure-openai/us-o1-mini",
    messages=[{"role": "user", "content": "Hello, o1-mini (US)!"}],
)

print(resp.choices[0].message.content)
print(f"Tokens: {resp.usage.total_tokens}")

# Per-call gateway metadata is returned on x-agentcc-* response headers.
# When you need it programmatically, use .with_raw_response to get them:
raw = client.chat.completions.with_raw_response.create(
    model="azure-openai/us-o1-mini",
    messages=[{"role": "user", "content": "Same call, but I want the headers."}],
)
print("Provider:", raw.headers.get("x-agentcc-provider"))
print("Latency:", raw.headers.get("x-agentcc-latency-ms"), "ms")
print("Cost:   ", raw.headers.get("x-agentcc-cost"), "USD")
print("Cache:  ", raw.headers.get("x-agentcc-cache"))
Set AGENTCC_API_KEY with a key fromapp.futureagi.com.Gateway docs ↗

Explore similar models

o1-mini (US) doesn't have a public Arena ELO score yet, so we group by provider only — quality-tier comparisons need a benchmark. Side-by-side links appear where a comparison page exists; otherwise, open the model profile.

FAQ

How much does o1-mini (US) cost?

Input is priced at $1.21 per 1M tokens and output at $4.84 per 1M tokens (Azure OpenAI, last verified Oct 22, 2026).

What is the context window of o1-mini (US)?

Context window for o1-mini (US) is not currently public.

Does o1-mini (US) support function calling?

o1-mini (US) does not currently advertise function-calling support. For agentic workloads, prefer a tool-calling-capable model and route via Agent Command Center for fallback.

Is o1-mini (US) good for production?

o1-mini (US) is best evaluated against your own production traces. Pipe traffic through Agent Command Center to compare it head-to-head against alternatives in shadow mode.

How can I route to o1-mini (US) with fallback?

Use Agent Command Center: a single OpenAI-compatible endpoint that supports cost-optimized routing, latency-aware retries, model fallback, and shadow traffic. Configure once, swap models without app changes.

Useful links for o1-mini (US)

Official sources, independent benchmarks, and pricing aggregators — no random search-engine guesses.