Skip to main content

Response Envelope

All model-listing endpoints (/api/v1/models, /api/v1/models/top, /api/v1/models/{name}) return this envelope:
object
required
Node identity information
object
required
Hardware specifications (see System Object below)
integer
required
Total number of models matching filters (before limit applied)
integer
required
Number of models in the response (after limit applied)
object
required
Echo of active query parameters for audit trails
array
required
Array of model fit objects (see Model Object below)

System Object

Hardware specifications detected on the node.
number
required
Total system RAM in gigabytes (rounded to 2 decimals)
number
required
Currently available system RAM in gigabytes
integer
required
Number of logical CPU cores
string
required
CPU model name (e.g., "Intel(R) Core(TM) Ultra 7 165U")
boolean
required
Whether any GPU was detected
number | null
required
Total VRAM across all GPUs in gigabytes (null if no GPU)
string | null
required
Primary GPU name (null if no GPU)
integer
required
Number of GPUs detected
boolean
required
Whether system uses unified memory (Apple Silicon). When true, VRAM = system RAM.
string
required
Detected inference backend:
  • "CUDA" - NVIDIA GPU
  • "ROCm" - AMD GPU
  • "Metal" - Apple Silicon GPU
  • "CPU (x86)" - x86_64 CPU fallback
  • "CPU (ARM)" - ARM CPU fallback
array
required
Array of individual GPU objects

Example


Model Object

Complete fit analysis for a single model on the current node.

Model Identity

string
required
Full model identifier (e.g., "meta-llama/Llama-3.3-70B-Instruct")
string
required
Model provider/creator (e.g., "Meta", "Qwen", "Mistral AI")
string
required
Human-readable parameter count (e.g., "7B", "70B", "8x7B" for MoE)
number
required
Numeric parameter count in billions (rounded to 2 decimals)
integer
required
Maximum context window in tokens
string
required
Release date in YYYY-MM-DD format
boolean
required
Whether model uses Mixture of Experts architecture

Use Case Classification

string
required
Primary use case specialization:
  • "General" - General-purpose
  • "Coding" - Code generation
  • "Reasoning" - Complex reasoning
  • "Chat" - Conversational
  • "Multimodal" - Vision + language
  • "Embedding" - Text embeddings
string
required
Use case label (same as use_case, for display purposes)

Fit Analysis

string
required
Model fit classification:
  • "perfect" - Fits entirely in VRAM with optimal quantization
  • "good" - Fits comfortably with reasonable performance
  • "marginal" - Barely fits, may require aggressive quantization
  • "too_tight" - Insufficient memory, unrunnable
string
required
Human-readable fit level (e.g., "Perfect", "Good")
string
required
Execution strategy:
  • "gpu" - Full GPU inference (weights in VRAM)
  • "moe_offload" - MoE with expert offloading
  • "cpu_offload" - GPU with layer offloading to RAM
  • "cpu_only" - CPU-only inference (weights in system RAM)
string
required
Human-readable run mode (e.g., "GPU", "CPU Offload")

Scoring

number
required
Overall fit score (0-100, rounded to 1 decimal). Composite of quality, speed, fit, and context scores.
object
required
Breakdown of score components

Performance Estimates

number
required
Estimated tokens per second throughput (rounded to 1 decimal)
string
required
Recommended inference runtime:
  • "mlx" - Apple MLX (Apple Silicon only)
  • "llamacpp" - llama.cpp (CUDA, ROCm, Metal, CPU)
string
required
Human-readable runtime (e.g., "MLX", "llama.cpp")
string
required
Recommended quantization level (e.g., "Q5_K_M", "Q4_K_M", "Q8_0")

Memory Analysis

number
required
Memory required to run this model in gigabytes (rounded to 2 decimals)
number
required
Memory available on this node in gigabytes (VRAM for GPU, RAM for CPU)
number
required
Memory utilization percentage (rounded to 1 decimal):

Additional Metadata

array
required
Array of warning/info strings (e.g., ["Requires layer offloading"]). Empty array if no notes.
array
required
Array of GGUF source URLs (empty for most models, populated when available)

Example


Fit Levels Explained


Run Modes Explained

Note: On unified memory systems (Apple Silicon), cpu_offload is skipped because VRAM and system RAM share the same pool.

Quantization Levels

Recommended quantization (best_quant field): The API automatically selects the best quantization level that fits available memory while maximizing quality.

Score Components

The overall score field is a weighted composite:
Component breakdown:
  • quality: Model capability based on parameter count and architecture
  • speed: Inference throughput (tokens per second)
  • fit: How well the model fits in available memory (higher = more headroom)
  • context: Available context window size
All components and the final score range from 0-100.

Forward Compatibility

Future API versions may add new fields. Clients should:
  1. Parse only required fields your application depends on
  2. Ignore unknown fields to support forward compatibility
  3. Validate critical fields exist before accessing
  4. Handle null values gracefully for optional fields
Example robust parsing: