Okapi Okapi

Humanloop API removal

Stopped workingSubscribe to Humanloop APIShare

Calls to the Humanloop API stopped working on September 8, 2025.


What to use instead of these calls

Move prompt management, evaluations, and logging to an alternative LLM ops platform, such as Langfuse, LangSmith, or Braintrust, and remove the Humanloop client. Because there is no successor product, teams must decide which replacement platform to adopt.

Humanloop shut down with no successor product: choosing the replacement platform is the team's call.

In Humanloop API's words

Following our acquisition, the Humanloop platform will be sunset on September 8th, 2025

Humanloop API, Announcement

Facts

API
Humanloop API api.humanloop.com
Kind
Removal
Announced
August 13, 2025
Takes effect
September 8, 2025
Calls after that day
Fail
Source
Announcement
Last updated
Verified
, against Humanloop API's own pages

Questions

When does this change take effect?

Calls to the Humanloop API stopped working on September 8, 2025.

What happens to calls after September 8, 2025?

They have failed since September 8, 2025.

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.

Add to GitHub

Get notifications

Subscribe to Humanloop API

Hear about each breaking change Humanloop API announces, in your feed reader, calendar or Slack.

1What to follow

Provider
  • Humanloop API

2Where to get it

/breaking-changes/feed.xml

Paste it into Feedly, Inoreader, NetNewsWire or any reader. New changes show up as they're announced.