Skip to main content
POST
Confirm a proposed create (create the assistant)
Second step of the propose → confirm flow. See Propose an agent edit for the full walkthrough. Each confirmationId from proposeAssistantCreate is single-use: it is consumed as soon as the confirm’s checks pass, right before the agent is created — even if the creation itself then fails — so a retry needs a fresh propose call. If the confirm errored or timed out, list the agents first: the creation may have completed, and re-proposing blindly would duplicate the draft.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

tenant
string
required

Tenant whose agents you are managing. Discover the tenants your credentials cover with listMyClaudiaProjects. A tenant your credentials do not cover is indistinguishable from one that does not exist.

Body

application/json

Just the confirmationId returned by proposeAssistantCreate.

The confirmationId returned by propose-create — the only field this endpoint reads.

confirmationId
string
required

Confirmation token returned by propose-create; the only field this endpoint reads. The server creates the assistant from the proposal it stored for this token. Omitting it answers 400.

Response

The agent as created — a draft, in the same passthrough shape getAssistant returns. A free-form object: read the keys rather than assuming a shape.

Free-form object: the agent's stored configuration, in whatever shape the live config schema for its deployment accepts. Read the keys you need; do not assume a fixed set.