Skip to main content

2026-08-14

Added: Agent list filtering

GET /agents now accepts two optional filters: The filters can be combined and work with the existing limit and cursor pagination parameters. See List Agents for examples and validation behavior.

2026-08-03

Added: Shared Stores API

The Shared Stores API now supports organization-scoped store and entry CRUD, idempotent single-entry updates, and bulk upserts with JSON metadata. Organizations can have up to 10 shared stores, with up to 10,000 entries in each store. See Shared Stores for the endpoint reference.

2026-06-28

Added: output source citations

Agent run outputs now include a sources[] array when a render uses licensed or external media. Getty b-roll citations include the usage window, query, provider asset ID when resolved, internal render asset ID, placement/layout, and rights metadata. Affected surfaces:

2026-05-21

Added: avatar profile API and generation tile docs

The Avatar Profiles API now exposes the public avatar workflow: Avatar profile responses use a flat object shape:
Avatars can be used in AI Avatar tiles immediately after creation. If processing is still running, the agent run waits for the avatar to become ready; failed avatars return an error through status_message. New generation tile documentation is also available for: The Run Agent docs now include node IDs and setup guidance for AI Avatar, Video Generation, Audio Generation, and Image Generation workflows.

2026-04-04

Added: errors field on agent runs and webhooks

Agent run responses and webhook payloads now include an errors field that surfaces error messages from failed tasks, grouped by the template node that produced them. Run-level (GET /agent_run/{run_id} and RUN_FINISHED webhook):
Each entry links errors to the original_node_id (template node) so you can map failures back to specific nodes in your agent. Node-level (GET /agent_run/{run_id}/nodes and RUN_PROGRESS webhook updated_nodes[]):
Per-node errors is a flat string array since the node context is already provided by the parent object. Affected endpoints: Previously, error details from processing tasks were only available internally. The status_message field on runs and nodes continues to work as before and is unaffected by this change.