Ultralytics
POST /v1/predict/{id} removal
Stopped workingSubscribe to UltralyticsShare
On July 31, 2026, Ultralytics shut down its HUB service. Calls to POST /v1/predict/* fail since that date. The change took effect following the managed HUB-to-Platform migration completed during Q2 2026.
Calls it hits
POST /v1/predict/*
What to use instead of these calls
Use the Ultralytics Platform REST API at platform.ultralytics.com/api with a Platform API key instead. Legacy HUB APIs and keys no longer work.
In Ultralytics's words
Ultralytics HUB shut down on July 31, 2026, after the managed HUB-to-Platform migration completed successfully during Q2 2026.
Facts
- API
- Ultralytics
api.ultralytics.com - Kind
- Removal
- Takes effect
- July 31, 2026
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Ultralytics's own pages
Questions
When does this change take effect?
Calls to POST /v1/predict/* on Ultralytics stopped working on July 31, 2026.
What happens to calls after July 31, 2026?
They have failed since July 31, 2026.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.