Phi 3.5 MOE Instruct
Azure AI Foundry chatPhi 3.5 MOE Instruct is an Azure AI Foundry chat model.It supports a 128,000-token context windowwith up to 4,096 output tokens.Input is priced at $0.160/M tokens and output at $0.640/M tokens. Route Phi 3.5 MOE Instruct via Future AGI's Agent Command Center for unified observability, caching, and 15 routing strategies including cost-optimized fallback.
Estimate Phi 3.5 MOE Instruct spend
Pick a workload, fine-tune the sliders, and see the monthly bill.
Estimate uses $0.1600/M input · $0.6400/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 May 12, 2026.
| Input | $0.160/M | |
| Output | $0.640/M |
Limits
- Context window
- 128,000 tokens
- Max input
- 128,000 tokens
- Max output
- 4,096 tokens
- 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
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 Phi 3.5 MOE Instruct yet. Have one to contribute? Submit a source — citations help us prioritise.
Call Phi 3.5 MOE Instruct 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.
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.# Phi 3.5 MOE Instruct 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-ai-foundry/phi-3-5-moe-instruct",
messages=[{"role": "user", "content": "Hello, Phi 3.5 MOE Instruct!"}],
)
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-ai-foundry/phi-3-5-moe-instruct",
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"))AGENTCC_API_KEY with a key fromapp.futureagi.com.Gateway docs ↗Compare with similar models
Phi 3.5 MOE Instruct doesn't have a public Arena ELO score yet, so we group by provider only — quality-tier comparisons need a benchmark.
- Claude Opus 4.7Azure AI Foundry · $5.00/M in · $25.00/M out · 200,000 ctx
- Claude Opus 4.6Azure AI Foundry · $5.00/M in · $25.00/M out · 200,000 ctx
- Claude Sonnet 4.6Azure AI Foundry · $3.00/M in · $15.00/M out · 1,000,000 ctx
- Claude Opus 4.5Azure AI Foundry · $5.00/M in · $25.00/M out · 200,000 ctx
FAQ
How much does Phi 3.5 MOE Instruct cost?
Input is priced at $0.160 per 1M tokens and output at $0.640 per 1M tokens (Azure AI Foundry, last verified May 12, 2026).
What is the context window of Phi 3.5 MOE Instruct?
Phi 3.5 MOE Instruct supports a 128,000-token context window with up to 4,096 output tokens.
Does Phi 3.5 MOE Instruct support function calling?
Phi 3.5 MOE Instruct 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 Phi 3.5 MOE Instruct good for production?
Phi 3.5 MOE Instruct 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 Phi 3.5 MOE Instruct 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 Phi 3.5 MOE Instruct
Official sources, independent benchmarks, and pricing aggregators — no random search-engine guesses.
Third-party evals — verify the marketing.
Cross-check our number against the rest of the ecosystem.