For the complete documentation index, see llms.txt. This page is also available as Markdown.

Get a Model Evaluation

Fetch a single model evaluation by its ID. For completed evaluations the response includes a summary object with headline metrics; running or failed evaluations return the lean shape only. Which headline metric is populated depends on the task type - mAP for detection-shaped tasks, mIoU for semantic segmentation.

https://api.roboflow.com/:workspace/model-evals/:evalId
curl "https://api.roboflow.com/my-workspace/model-evals/huUF720inUcymARwqAGK?api_key=$ROBOFLOW_API_KEY"

Response (done evaluation)

{
    "evalId": "huUF720inUcymARwqAGK",
    "status": "done",
    "project": "chess-pieces-fmhpz",
    "versionId": "4",
    "modelId": null,
    "createdAt": "2026-04-27T20:04:10.904Z",
    "summary": {
        "mAP": 0.9239650566041828,
        "mIoU": null,
        "precision": 0.85,
        "recall": 0.85
    }
}

Response (running or failed)

The same fields without the summary block.

Notes

  • mAP is mean Average Precision at IoU 0.5 (map50). It is null for non-detection evaluation tasks (e.g. classification, semantic segmentation).

  • mIoU is the foreground macro mean Intersection-over-Union. It is populated only for semantic segmentation evaluations and null otherwise.

  • precision and recall are reported at the F1-optimal confidence threshold for the test split.

  • evalId is the same identifier embedded in every panel response - the modelEvals.get payload is structurally a superset of any panel payload, so a summary-augmented modelEvals.get and a getMapResults response can be rendered through the same client code path.

  • project is the project's URL slug - the same identifier the REST API uses in URL paths. To deep-link to the evaluation UI: https://app.roboflow.com/{workspace}/{project}/evaluation/{versionId}. project is null if the project has been deleted.

Last updated

Was this helpful?