Grok 4.7

xAI's model, with closed weights. Forcebench has run it in 1 configuration on the API board. API is models reached through a hosted service; Local, models served on Forcebench’s own hardware.

On the API board

Models reached through a hosted service. Grok 4.7 is ranked by its one configuration: the fifth-highest score of 26 models, not clearly different from 9 other models. Scores are within 3 attempts (c@3) with 95% intervals; each configuration is compared with the highest-scoring one by whether their 95% intervals overlap. Every configuration on the board → Cost and speed →

92%
within 3 attempts (c@3), 95% CI 89–95 · high · fifth-highest score of 26 models, not clearly different from 9 other models
13k
output tokens per task · median 7.4k, p90 35k
111 s
median per task, every attempt counted, including network and queueing · 90th percentile 536 s
0%
no answer within the 32,768-token budget
$0.11
per task at the list price of 10 October 2026, every attempt counted
$0.12
per solved task: the total cost over the tasks solved · cost and speed
Every configuration of Grok 4.7 on the API board
ConfigurationRank all configsWithin 3 attempts c@3 · 95% CITokens mean · median · p90No answerLatency median per task, every attempt countedCost per taskCost per solved task
OpenRouter · highhighest score7
92%95% CI 89–95
13k7.4k · 35k0%111 s$0.11$0.12
Suites, at its highest-scoring configuration
high · OpenRouter: within 3 attempts (c@3) on each suite with 95% intervals, against the median of the API board's models, each at its highest-scoring configuration.
  • 95% interval
  • API board median
100%, 95% interval 84–100%
89%, 95% interval 67–97%
88%, 95% interval 66–97%
100%, 95% interval 84–100%
65%, 95% interval 41–83%
94%, 95% interval 74–99%
100%, 95% interval 82–100%
95%, 95% interval 75–99%
100%, 95% interval 82–100%
94%, 95% interval 74–99%
83%, 95% interval 61–94%
93%, 95% interval 70–99%
83%, 95% interval 61–94%
100%, 95% interval 84–100%
94%, 95% interval 74–99%
    Show the numbers
    Per-suite scores of Grok 4.7's highest-scoring configuration on the API board, with the board's median
    Suitec@3 95% CIAPI medianTasks
    Apex
    100%95% CI 84–100
    90%20
    Salesforce APIs
    89%95% CI 67–97
    72%18
    CI/CD
    88%95% CI 66–97
    88%17
    Salesforce CLI
    100%95% CI 84–100
    90%20
    Salesforce docs
    65%95% CI 41–83
    29%17
    fflib Enterprise Patterns
    94%95% CI 74–99
    61%18
    Flow
    100%95% CI 82–100
    69%18
    Governor limits & pushback
    95%95% CI 75–99
    89%19
    Lightning Web Components
    100%95% CI 82–100
    100%18
    Nonprofit Success Pack
    94%95% CI 74–99
    81%18
    Packaging
    83%95% CI 61–94
    69%18
    Permissions & access
    93%95% CI 70–99
    87%15
    Scratch org definitions
    83%95% CI 61–94
    50%18
    SOQL
    100%95% CI 84–100
    100%20
    Trigger Actions Framework
    94%95% CI 74–99
    86%18

    In the studies

    Want this for your team?

    Azul Labs runs Forcebench privately for two kinds of Salesforce team.

    Choosing a model to run yourself?

    A private benchmark of your shortlist

    Open-weight models at the quantisations and reasoning efforts you could run on infrastructure you control, tested on your kind of Salesforce work, with a written recommendation.

    • Private tasks written from your work only ever run on local models; they are never sent to an API.
    • Re-testing after any change of model, quantisation or engine is available.
    • Typical turnaround is 2–3 weeks; large models take about a day of machine time per configuration.

    Building or buying a Salesforce AI tool?

    A private evaluation of your tool

    Your tool on held-out tasks it has never seen, against API baselines (models reached through a hosted service) and Local ones (served on Forcebench’s own hardware), with a written report on where it holds up and where it fails.

    • It can start as a smaller pilot, about 30 held-out tasks with your tool against two baselines, before a full evaluation.
    • Repeat evaluations after your releases are available.
    • Typical turnaround is 2–3 weeks.

    Fixed fee, quoted up front. The quote depends on the number of tasks and the number of models, tools or configurations tested.

    Or email leo@azl.au · azl.au