Just saw the notification flash by in my feed about a "major, forward-looking API evolution" from Braintrust. The announcement copy is, predictably, full of the kind of corporate synergy speak that makes me immediately suspicious. They're talking about "streamlining developer experiences" and "unlocking new paradigms," but I can't find a single concrete breaking change, deprecated endpoint, or migration timeline in their public posts.
If this is anything like the last "evolution" from a major cloud vendor, it means they're going to version-lock the current API, introduce a completely new authentication model that requires a 15-step IAM dance, and silently change the pagination format on half the responses. My immediate concerns, which someone here must have dug into already, are:
* Is the core `object` query/mutation structure changing, or is this just a new GraphQL endpoint wrapped around the old REST API with a version suffix?
* What's the deprecation policy for the current API I'm using in production? The blog post says "long-term support" which historically means "you have 90 days to panic."
* Most importantly, are they finally addressing the insane cardinality issues with the trace spans? The current label system blows up our metrics ingestion costs, and no amount of their "efficiency gains" marketing covers that.
I need to see the actual diff, not the press release. Has anyone managed to get their hands on the real technical specification or a preliminary SDK? My hunch is this is a cost-optimization move on their backend disguised as a feature release, and the bill will get passed to us through observability side-channels.
-- Cam
Trust but verify.
"Long-term support" means your costs double when you're forced onto the new tier. They'll sunset the old API right after billing cycles switch to per-request pricing with a 5x multiplier.
The real cardinality fix is a new `advancedDataFiltering` add-on for $0.02 per filtered record. Seen it before.
show the math
Yeah, I hit refresh on their docs for a solid 20 minutes hoping for a changelog, nothing yet. My guess on the "streamlining" is they're finally moving everything to a single GraphQL endpoint, but you're right, it'll probably just be a proxy layer over the old REST API for now.
The "long-term support" window is what worries me. Last time a vendor pulled this on me, the "LTS" version stopped getting critical security patches after six months unless you upgraded to the new pricing plan. I've got alerts set up for any 4xx spikes in my API monitors - that's usually the first sign of a silent pagination change going live.
Oh, and cardinality? Don't get me started. If they fixed that for real, they'd have led with it. My money's on it being a new, more expensive query parameter.
Dashboards or it didn't happen.
The "long-term support" line is the only real info they've given. It's the vendor code for "your current API calls are now a liability".
Found the actual spec in a GitHub commit buried three repos deep. The cardinality fix is a new rate limit header. Costs you credits to query it.
You've got about a year before the 4xx spikes start. They'll blame your client library first.
Prove it.