Auto Agent Builder

Generate Agent Configurations From a Task

Generate a roster of agent configurations for a task. A single builder agent designs the team and returns ready-to-post AgentSpec entries — the generated agents are not executed by this endpoint.

post/v1/auto-agent-builder/completions

Headers

x-api-keystring required

Request body

taskstring required

The task the generated team should be able to handle. This is the only required field.

namestring nullable

The name of this auto agent builder run.

descriptionstring nullable

The description of this auto agent builder run.

model_namestring nullable

The model backing the builder agent itself — not the models given to the generated agents; the builder chooses those per agent. Defaults to the framework's builder default.

max_agentsinteger nullable

Upper bound on roster size. This is a ceiling, not a target — the builder prefers the smallest roster that covers the task.

num_agentsinteger nullable

Exact number of agents to generate. When set, this overrides max_agents and the builder's prefer-fewer guidance.

system_promptstring nullable

Custom instructions for the builder agent. Defaults to the framework's builder system prompt.

agent_kwargsobject nullable

Extra keyword arguments carried on every generated agent, e.g. max_loops or streaming_on. Keys that collide with the fields the builder generates (agent_name, description, system_prompt, model_name) are ignored.

Response

Successful Response

job_idstring required

The job ID of the auto agent builder run.

namestring required

The name of the auto agent builder run.

descriptionstring required

The description of the auto agent builder run.

statusstring required

The status of the auto agent builder run.

timestampstring required

The timestamp of the auto agent builder run.

Changes

Changed in 6 of the 54 revisions of this API.2110

    • added the new None enum value to the /// response property for the response status

      response-property-enum-value-added

  • 2f1c2f28613922See the full diff
    • the response property / became optional for the status

      response-property-became-optional

    • removed the required property / from the response with the status

      response-required-property-removed

    • the response's property default value 0.01 was added for the status

      response-property-default-value-added

    • added the required property / to the response with the status

      response-required-property-added

    This revision also has 3 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

    • added the optional property // to the response with the status

      response-optional-property-added

    • added subschema #3 to the // response property anyOf list for the response status

      response-property-any-of-added

    • added subschema #1 to the // response property anyOf list for the response status

      response-property-any-of-added

    • added subschema #2 to the // response property anyOf list for the response status

      response-property-any-of-added

    • removed from the // response property anyOf list for the response status

      response-property-any-of-removed

    This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

    • the response's property default value medium was removed for the status

      response-property-default-value-removed

    • added the new optional request property

      new-optional-request-property

    • endpoint added

      endpoint-added

    This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog