Auto (router)

Fireworks AI chat

Auto (router) is a Fireworks AI chat model. Capabilities include function calling, reasoning. Route Auto (router) via Future AGI's Agent Command Center for unified observability, caching, and 15 routing strategies including cost-optimized fallback.

Pricing source: unknown Last verified: Oct 22, 2026 View source ↗
Pricing not yet public

We don't have verified per-token pricing for Auto (router) yet. If you have a source from Fireworks AI's documentation, help us add it — your submission gets reviewed within 48 hours.

Pricing

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

Input —
Output —

Context & limits

Context window
—
Max input
—
Max output
—
Modalities
text

Capabilities

  • Function calling ✓ supported
  • 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 ✓ supported
  • Prompt caching — not advertised
  • Reasoning ✓ supported

Strengths & caveats — when to pick Auto (router)

Data-driven from Auto (router)'s percentile within chat peers.

Where it's strong

  • +multi-step reasoning and analysis tasks
  • +agentic workflows that depend on reliable tool calls

Watch out for

  • No major caveats flagged from public spec.

Benchmarks pending

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

Try it

Call Auto (router) 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.
# Auto (router) 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="fireworks-ai/accounts-fireworks-routers-auto",
    messages=[{"role": "user", "content": "Hello, Auto (router)!"}],
)

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="fireworks-ai/accounts-fireworks-routers-auto",
    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

Auto (router) 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 Auto (router) cost?

Public per-token pricing for Auto (router) is not yet published. Submit a source on this page to help us add it.

What is the context window of Auto (router)?

Context window for Auto (router) is not currently public.

Does Auto (router) support function calling?

Yes — Auto (router) supports function (tool) calling.

Is Auto (router) good for production?

Auto (router) is well-suited for multi-step reasoning and analysis tasks and agentic workflows that depend on reliable tool calls.

How can I route to Auto (router) 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 Auto (router)

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