Changelog

The compute_units parameter has been renamed to reasoning_loops to better reflect what the parameter controls. This is a breaking change for request payloads.

1
{
2
  "query": "What is the current price of Bitcoin?",
3
  "compute_units": 3
4
}

1
{
2
  "query": "What is the current price of Bitcoin?",
3
  "reasoning_loops": 3
4
}

Five new parameters give you finer control over research behavior:

You can now associate research requests with file collections using the collection_ids parameter. The research pipeline will search across all files within the specified collections.

1
{
2
  "query": "Summarize the key findings from my research papers",
3
  "collection_ids": ["a1b2c3d4-5678-90ab-cdef-1234567890ab"],
4
  "reasoning_loops": 3
5
}

Two new fields provide better visibility into job execution:

The score field has been removed from result items. Source relevance is now determined internally and reflected in result ordering.

1. Replace compute_units with reasoning_loops in all requests
2. Update response parsing to use reasoning_loops_consumed instead of compute_units_consumed
3. Remove any logic that depends on the score field in results

The first public version of the Caesar Research API.