How one modpack is likely to run on a machine like yours: an average frame-rate range, 1 % low, memory and load time, with how many runs and senders it stands on and whether it was measured on similar PCs or estimated from others
Too little data is said as such, never as zero.
GET
/api/v1/perf/estimate - Sign-in
- No scope
- Scope
- None
- MCP tool
perf.estimate
Parameters
| Field | Type and meaning |
|---|---|
cpu query | string |
gpu query | string |
gpuPci query | string |
height query | integer |
portal query | string |
projectId query | string |
ramMb query | integer |
width query | integer |
Response 200
| Field | Type and meaning |
|---|---|
fpsHigh always | number |
fpsLow always | number |
hwClass always | string |
level always | string |
limits always | string |
live always | object |
live.fps always | number |
live.lowFps always | number |
live.runs always | integer |
live.senders always | integer |
loadS always | number |
lowFps always | number |
portal always | string |
projectId always | string |
ramGb always | integer |
runs always | integer |
senders always | integer |
Errors
| Status | Type and meaning |
|---|---|
400 | The request was not understood. |
401 | Sign in and try again. |
404 | There is nothing here, or nothing you may see. |
429 | Too many requests. |
500 | Something on our side went wrong. |
Every error comes back as { code, message, requestId }. Errors