Model comparisons
Apex or Beam 1.0, tier by tier: matched prices, request fields, limits and the content policy measured on each.
Apex from Callstack supports React Native and React application development. This chat API accepts text / images, provides a 262,144-token input budget and accepts max_tokens up to 131,072. Stream Apex’s text as it arrives, or let a function-call result supply the evidence for the next step in React Native development with Apex.
View model details →View sample outputs →Beam 1.0 from Reflection supports coding and long-running tool workflows. This chat API accepts text, provides a 1,048,576-token input budget and accepts max_tokens up to 943,718. Stream Beam 1.0’s text as it arrives, or let a function-call result supply the evidence for the next step in long coding sessions with Beam 1.0.
View model details →View sample outputs →Compare
Start with the input you have, the result you want and your budget. These are the differences that affect that choice.
Compare the published examples, then try the same input on both models with matching settings.
The Spicy Index and Freedom Score for both models, from the same daily calculation as the leaderboards.
| Measure | Apex | Beam 1.0 |
|---|---|---|
| Spicy Index | 77.7 | 68.9 |
| Freedom Score | Not yet tested | Not yet tested |
| Evidence | — | — |
| Range if the rest pass | — | — |
| Price | $1.13 per 1M mixed tokens (3 input : 1 output) | $1.50 per 1M mixed tokens (3 input : 1 output) |
| Reviews | Read the Apex review | Read the Beam 1.0 review |
Preliminary · freedom evidence pending
See both on the leaderboard →Current price
A start price answers a different question than the one you have. These are the tiers both models publish, matched setting for setting, in US dollars per billed unit with no conversion step in between.
Swipe horizontally to compare all fields.
| Tier | Apex | Beam 1.0 | Difference |
|---|---|---|---|
| Input | $0.5 / 1 million tokens | $1 / 1 million tokens | Apex −50% |
| Cached input | $0.2 / 1 million tokens | $0.1 / 1 million tokens | Beam 1.0 −50% |
| Output | $3 / 1 million tokens | $3 / 1 million tokens | Identical |
Arithmetic on the published rates at each model's own default setting, not a quote. The console prices your actual settings before a request is accepted.
About this comparison
Every row here is read from the JSON Schema the endpoint validates against, so it matches what the API will really accept rather than a feature list written by hand.
Swipe horizontally to compare all fields.
| Controls and limits | Apex | Beam 1.0 |
|---|---|---|
| Supported tasks | chat | chat |
| Input context | 262,144 tokens | 1,048,576 tokens |
| Maximum output | 131,072 tokens | 943,718 tokens |
| Tool calling | Yes | Yes |
| Execution | Synchronous, with streaming | Synchronous, with streaming |
| Request timeout | 10 minutes | 10 minutes |
| Availability | Live | Live |
Can I swap the model ID without changing the request body?
The task lifecycle is shared; the body is not. Each endpoint publishes its own JSON Schema and the API validates against that, so this is the list to reconcile before a switch.
How to choose
Beam 1.0 can return more in one reply: up to 943,718 tokens against the other model's ceiling.
Beam 1.0 takes the longer prompt: up to 1,048,576 input tokens in a single request.
Compare
The model identifiers are callstack/apex/chat and reflection/beam-1.0/chat, and both go in the same field of the same request.
Both return the response on the chat request. With streaming enabled, read the stream until it finishes; there is no media task to poll.
Both use the same submit-and-track flow, but their required inputs may differ. Check each model page before switching.
One key, one balance, one set of spend caps. Both bill to the same account in US dollars, and the per-key daily, monthly and lifetime limits apply to whichever one you call.
Questions developers ask
Prices and capabilities shown here come from the current public model catalogue. Check each model page for its latest inputs and examples. Prices may change; check the estimate shown for your actual settings before submitting.
Apex allows 10 minutes per task and Beam 1.0 allows 10. Those are ceilings rather than typical times — most requests finish far sooner — but they are what your own client timeout has to survive.
Prices and capabilities shown here come from the current public model catalogue. Check each model page for its latest inputs and examples.