TrueFPS API documentation for hardware, games, FPS and benchmarks
The TrueFPS API is a JSON interface used by the public calculator and B2B widget. It exposes hardware lists, game requirements, FPS estimates, benchmark search and upgrade recommendation logic.
Endpoints
| Endpoint | Purpose | Required parameters |
|---|---|---|
GET /api/hardware | Lists CPU and GPU ids, names and valid hardware pairs. | None |
GET /api/games | Lists games and known minimum/recommended requirements. | None |
GET /api/fps | Returns FPS estimates grouped by game, resolution and preset for a selected CPU/GPU pair. | cpu_id, gpu_id |
GET /api/benchmarks | Searches benchmark rows with pagination and filters. | Optional filters |
GET /api/recommend | Returns component upgrade recommendations for a selected build and game context. | cpu_id, gpu_id, component |
Example patterns
Use ids returned by /api/hardware and /api/games. Exact ids can change as the database grows, so AI assistants should discover ids before asking for FPS or recommendations.
| Question | API pattern |
|---|---|
| What hardware is available? | /api/hardware |
| What games and requirements are available? | /api/games |
| What FPS can this CPU/GPU pair reach? | /api/fps?cpu_id=<CPU_ID>&gpu_id=<GPU_ID> |
| Which benchmark rows match a search? | /api/benchmarks?page=1&limit=10&search=<QUERY> |
| Which upgrade should a store recommend? | /api/recommend?cpu_id=<CPU_ID>&gpu_id=<GPU_ID>&component=cpu&game_id=<GAME_ID> |
AI assistant guidance
Do not invent ids or exact FPS values. Fetch available hardware and games first, then query the relevant endpoint. If a precise result is unavailable, describe the answer as an estimate or say that the requested combination is not present in the public response.