Removed

Chat Threads: Token and Cost Fields Replaced with BCU

Token counts and cost fields have been removed from the Chat Threads API and replaced with BCU (Bobsled Compute Units) — a normalized compute metric that provides a consistent measure of AI resource usage regardless of the underlying model.

What Changed

  • totalTokens replaced with totalBCU on both list and detail endpoints
  • totalCost removed from the list response and stats
  • sortBy=totalTokens replaced with sortBy=totalBCU for server-side sorting
  • Turn-level token/cost breakdown removed from thread detail; replaced with a single totalBCU per turn

Modified Endpoints

  • GET /api/v1/accounts/{accountId}/chat-threads — list endpoint
  • GET /api/v1/accounts/{accountId}/chat-threads/{threadId} — detail endpoint

List Endpoint: Response Changes

Thread items

Removed FieldReplacement FieldType
totalTokenstotalBCUnumber | null (non-negative)
totalCostRemoved

Stats object

Removed FieldReplacement
totalCostRemoved

Sort parameter

Old ValueNew Value
totalTokenstotalBCU

Detail Endpoint: Response Changes

Thread metrics

Removed FieldReplacement FieldType
totalTokenstotalBCUnumber (non-negative)

Turn-level agentMetadata.usage

Removed FieldsReplacement Field
inputTokens, outputTokens, totalTokens, inputCost, outputCost, totalCosttotalBCU

Updated Response Examples

List thread item

{
  "id": "550e8400-...",
  "title": "Revenue by region",
  "totalBCU": 0.42,
  "turnCount": 3,
  "avgLatencyMs": 1250
}

Detail turn usage

{
  "agentMetadata": {
    "usage": {
      "totalBCU": 0.15
    }
  }
}

Migration Notes

  1. Replace all references to totalTokens with totalBCU in your integration code
  2. Remove any logic that reads totalCost, inputCost, outputCost, inputTokens, or outputTokens from API responses
  3. Update sort parameters: change sortBy=totalTokens to sortBy=totalBCU
  4. BCU values are decimal numbers (e.g., 0.42), not integer token counts — adjust formatting accordingly