Reka Core
Snowflake Cortex chatReka Core is a Snowflake Cortex chat model.It supports a 32,000-token context windowwith up to 8,192 output tokens. Route Reka Core via Future AGI's Agent Command Center for unified observability, caching, and 15 routing strategies including cost-optimized fallback.
We don't have verified per-token pricing for Reka Core yet. If you have a source from Snowflake Cortex's documentation, help us add it — your submission gets reviewed within 48 hours.
Pricing
Per-token rates, expressed in USD per 1M tokens. Verified May 12, 2026.
| Input | — | |
| Output | — |
Limits
- Context window
- 32,000 tokens
- Max input
- 32,000 tokens
- Max output
- 8,192 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
- !limited context — 32,000-token window is in the bottom quartile; not ideal for long documents or large RAG
- !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 Reka Core yet. Have one to contribute? Submit a source — citations help us prioritise.
Call Reka Core 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.# Reka Core 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="snowflake-cortex/reka-core",
messages=[{"role": "user", "content": "Hello, Reka Core!"}],
)
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="snowflake-cortex/reka-core",
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 ↗FAQ
How much does Reka Core cost?
Public per-token pricing for Reka Core is not yet published. Submit a source on this page to help us add it.
What is the context window of Reka Core?
Reka Core supports a 32,000-token context window with up to 8,192 output tokens.
Does Reka Core support function calling?
Reka Core 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 Reka Core good for production?
Reka Core 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 Reka Core 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 Reka Core
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.