SDK Method Name Changes
In an effort to keep our SDK method names consistent with our conventions, we have renamed the following methods:
Before and After
New Projects Endpoint
A new Projects
endpoint has been added to the API, allowing you to manage projects and their associated templates.
The new endpoints can be found here: Projects
New Batch message creation API
A series of new Batch
endpoints has been introduced to support batch message creation, allowing you to perform multiple LLM requests in a single API call. These APIs leverage provider batch APIs under the hood, which can be more cost-effective than making multiple API calls.
New endpoints can be found here: Batch Messages
New List Agent Groups API added
The List Agent Groups
API has been added to the Agents endpoint, allowing you to retrieve all multi-agent groups associated with a specific agent.
New reasoning_effort
field added to LLMConfig
The reasoning_effort
field has been added to the LLMConfig
object to control the amount of reasoning the model should perform, to support OpenAI’s o1 and o3 reasoning models.
New sender_id
parameter added to Message model
The Message
object now includes a sender_id
field, which is the ID of the sender of the message, which can be either an identity ID or an agent ID. The sender_id
is expected to be passed in at message creation time.
New Upsert Properties API for Identities
The Upsert Properties
API has been added to the Identities endpoint, allowing you to update or create properties for an identity.
New Parent Tool Rule
A new tool rule has been introduced for configuring a parent tool rule, which only allows a target tool to be called after a parent tool has been run.
Runs API can now be filtered by Agent ID
The Runs API now supports filtering by agent_id
to retrieve all runs and all active runs associated with a specific agent.
Add new otid
field to Message API
The Message
object returned by our Messages endpoints now includes an offline threading id field, a unique identifier set at creation time, which can be used by the client to deduplicate messages.
Before:
New strip_messages
field in Import Agent API
The Import Agent
API now supports a new strip_messages
field to remove messages from the agent’s conversation history when importing a serialized agent file.